Developer Meeting 2024-09-03, 15:00¶

Location: ACDH-CH, Bäckerstraße 13, 3D (the big one next to the kitchen in 3nd floor)
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¶

• Alexander Watzinger
• Bernhard Koschiček-Krombholz
• Massimiliano Carloni
• Nina Richards
• Olivia Reichl (moderator)
• Stefan Eichert

Administrative¶

• Feedback round ✅
• Schedule next developer meeting, who moderates? -> 9. October (Bernhard moderates), 4. Dezember (Alex moderates)
• #2311 T-shirts -> Nina kindly offered to keep track of it

Plan new features¶

We won't have time to discuss these in depth. It will be more about status updates and scheduling kickoff meetings.

• #2332 Persistent presentation site URLs
  • We absolutely need persistent links for frontends which can be used for e.g. publications or as reference system links by other applications
  • These links should still work even after making sites static
  • As discussed we will use /entity/<id> as permalinks and will label/show it at the detail view accordingly
• #2079 Text annotation
  • Take a look at the draft
  • Maybe Christoph can provide support for the frontend part?
  • -> When Christoph returns we schedule a meeting for the frontend part, Alex and Bernhard will take care of the backend part.
• #2319 OpenAtlas and APIS interface
  • Make a first version draft
  • Plan kickoff meeting with APIS developers
  • -> Bernhard will organize a kickoff meeting together with the APIS team
• #2300 Load form tables dynamically
  • Important to solve performance issues with bigger data sets
  • -> Bernhard will take a look at it, Olivia will support with the JavaScript table part
• #2170: Tags on project site
  • Olivia + Nina?
  • -> Olivia and Nina will take of the tags for the project page and will make other minor adaptions while at it

Topics¶

• Result of first usability research interview ✅
• #2323 Improved start page
  -> Has no high priority but everyone is invited to make suggestions
• #2156 Change end data functionality: worth the effort?
  -> No additional reasons (except that it would feel more correct) that would justify the effort were provided. Instead a new idea was proposed which should be tracked in an new issue.
• #1925: Multi language support for data entering - model solution for description needed
  -> The newest proposed CIDOC CRM solution was deemed to be too insufficient for description translations by Stefan
• Move: confusing adding of persons/groups to move events (again)
  -> No progress was made with this topic