Developer Meeting 2026-01-28, 13:00¶

Location: ACDH, Bäckerstraße 13, room 3D
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 (moderator)
• Alina Coskun
• Bernhard Koschiček-Krombholz
• Nina Richards
• Massimiliano Carloni
• Olivia Reichl
• Stefan Eichert

Administrative¶

• Welcome Alina ✅
• Feedback round ✅
• Schedule next developer meeting -> 2026-04-13, 13:00, moderator Bernhard
• Events ✅

Topics¶

OpenAtlas Discovery¶

After the 1.0.0 release we could present it more on https://openatlas.eu

• Announcement 1.0.0 release at news (also in Redmine) ✅
• Add to software section (#1992) ✅
• Other ideas -> Either add to start page or, depending on size, add an own site with a link to it at start page

Renaming OpenAtlas classes¶

OpenAtlas changed and evolved a lot in recent years and so did our understanding of class usage. Some suggestions of re-naming OpenAtlas classes to reflect this:

• appellation -> alias ✅
• source translation -> text ✅
• administrative unit -> which consists now of custom place hierarchies (instead fixed administrative unit and historical place) -> Will stay the same
• Group artifact -> to make clear it includes human remains and artifacts -> item (DE: Gegenstand)

Dates¶

• Dates before 4713 BC (#1004): Claire asked about it. Post at PostgreSQL mailing list again?
  -> Decision to not try PostgreSQL mailing list again but to look into customization of PostgreSQL functions
• Change end data functionality (#2156): Clarify that it isn't blocked but could be a lot of work (backend, API, former presentation sites, ...) ✅

Other issues¶

• THANADOS performance: when will be update/server move? -> Time of server move currently unknown but an OpenAtlas update can happen before.
• Vocabs Bone Vocabulary (#2591): status? -> Looking good, vocabulary release seems to be possible in February
• Sub documents for sources (#1970): add to roadmap? -> Decision to use Stefan's approach (see #1970) but has to be documented in manual
• Case study system type (#2705): keep the name? -> Yes