Approaching Byzantium meeting 2024-12-12, 12:00¶

Location: Online
Updated information in the course of the meeting is in color and/or marked with an ✅. Every participant is welcome to add and adapt.

Participants¶

• OpenAtlas: Alexander Watzinger, Olivia Reichl
• Approaching Byzantium: Nicholas Melvani

Topics¶

The meeting will be mostly about the presentation site for Approaching Byzantium: https://approaching-byzantium.openatlas.eu/.

• Update about changes
• Discuss how entries for Places are displayed (questions, comments, and requests from Nicholas)
• Search functions and filters (questions from Nicholas)
• Questions about the layout
• Minor clarifications about the database: connecting artifacts with owners; removing subs from artifacts

Update with information from the meeting¶

We received a lot of valuable input and feedback from Nicholas. I (Alex), tried to document it and creating issues after the meeting.
Like always, every participant is free to add/adapt and, especially created issues concerning the presentation site, are up to our frontend team to prioritize and assign them as seem fit.

• Displaying movement: like previously discussed, this issue will be prioritized (#2253)
• Expandable detail view (#2423)
• Remove types from being displayed (#2424)
• Remove placeholder for unavailable images (#2425)
• Multiple collapsible info boxes in side bar (#2426)
• Show additional file information (#2295)
• Improved search options (#2427)
• Showing type related entities: not sure where we looked at it in our meeting but it seems to work, e.g. see (disregarding the known layout bug) male
• Broken home link (#2428)
• Nicholas kindly offered to add us to the team site. We are feeling honored and will send a suggestion.
• One display bug, the issue will be created by Nicholas (and linked here later).
• List related texts below listed source (#2429)

• Question about owner of artifact: it is broadly used for owner and last location but what if they differ? -> was added as topic for next developer meeting
• Presentation site in backend is linked to MAMEMS: we will need a solution how to deal with multiple presentation sites sharing the same backend (#2430)