OpenAtlas + APIS Meeting 2025-02-11, 11:30, room 2C¶

Location: ACDH-CH, Bäckerstraße 13
Updated information during the meeting is in color and/or marked with an ✅. Every participant is welcome to add and adapt.

Participants¶

• OpenAtlas: Alexander Watzinger, Bernhard Koschiček-Krombholz, Nina Richards
• APIS: Matthias Schlögl, Saranya Balasubramanian

Topics¶

• Public protocol ok? ✅
• To start OpenAtlas would do the same with APIS as with other reference systems:
  • Define a resolver URL
  • Search with autocomplete
  • Show entity info of the other system

• How GeoNames and Wikidata is integrated in OpenAtlas and the OpenAtlas API was presented to the APIS team
• APIS limits the availability of entities that show up in the Wikidata search - so only persons are shown when entering an actor as big difference; they also import data into APIS (enrich view) which OpenAtlas does not
• OpenAtlas would like to create something similar for one of the ENCHANT case studies and will use a No Mans Land instance, see their swagger
• The extra information in APIS could be used in OpenAtlas in the same way as for Geonames and Wikidata
• APIS has a filtered search or a field search available - a completely open search across different classes is not provided though
• APIS API is not opened for entities yet but persons are accessible already

• How does APIS generate Swagger files
  Auto generating for all base classes - if one model uses 5 or 6 base classes, it's displayed under every header; Django spectacular inspects the Django API routes and classes for getting query parameters

How to proceed¶

• Bernhard will look into using the No men's land API and will give feedback
• As soon as OpenAtlas gets missing basic information from project partners we will inform APIS so that they can try to work with/access our API too
  -> the OpenAtlas team would then be curious about feedback too
• Next step would be to look into how generic this cross-systems can be used between other projects from OpenAtlas and APIS