OpenAtlas

h1. OpenAtlas Discovery API Meeting 2024-04-30

Updated information in the course of the meeting is %{color:green}in color%. Every participant is welcome to add and adapt.

The meeting will be about the presentation site and the API used to retrieve the relevant information.

h2. Participants

* *OpenAtlas*: Olivia Reichl, Bernhard Koschiček-Krombholz, Moritz Großfurtner

h2. Topics

* Can the types hierarchy be delivered with each step as JSON Object consisting of ID and Label for better navigation? %{color:green} Will be added✅%

* Get array of possible relation types, as well as corresponding Description/Locale Strings via API?  %{color:green} Array will be added, but we should create our own dictionary that can potentially be overwritten on a project basis. ✅%

* New format just to load overview tables faster? (Bernhard) %{color:green} Already in use for the map and not needed for the tables due to pagination ✅%

* Relation timespans (e.g. for actor relations) don't seem to be sent in the response. It seems, that the timespans sent with the relations are the ones of the linked entity, not of the relation. %{color:green} Will be addressed/fixed ✅%

h2. Topics raised in the meeting

* Discuss how to handle previous & next object e.g. for artifacts belonging to a grave. Should it be fetched client side or can it be added to the response object of an Entity request? 

** If we need to fetch the data via the frontend the sensible path would probably be: Fetching the parent and then finding the previous/next one in it's list of siblings.