Project

General

Profile

Actions

Meeting 2022-04-05 » History » Revision 17

« Previous | Revision 17/20 (diff) | Next »
Massimiliano Carloni, 2022-04-05 22:49


OpenAtlas INDIGO Vocabs Meeting 2022-04-05

Updated information in the course of the meeting is in color. Every participant is invited to add and adapt.

Participants

  • Alexander Watzinger
  • Bernhard Koschiček-Krombholz
  • Klaus Illmayer
  • Massimiliano Carloni

This meeting is about importing thesaurus from ACDH-CH Vocabs into OpenAtlas (#1663). We invited our Vocabs expert Klaus to help clear up open questions.

Vocabs frontend

Is there a possibility/tool to enter and manage data directly in Vocabs (a SKOSMOS representation of a thesaurus)?
  • ACDH-CH tool vocabseditor for simple solutions, but currently unmaintained.
  • Vocbench, an external tool but very complex and with some unsolved issues currently.

Massimiliano will take a look at the vocabseditor but most likely we keep the current workflow (INDIGO providing the data and Massimiliano importing it to Vocabs).

Identifier

At the moment in the INDIGO project identifier like 0080 are used, are there better alternatives?
Klaus suggest using camel case notation of the label in the URI when stable, like e.g https://vocabs.dariah.eu/tadirah/en/page/audioAnnotation.

Versioning

Versioning is possible in theory but there are no good practical solution which could be used as examples currently. E.g. former versions could be archived in Arche and on Vocabs only the newest version is available. Problem with this solution would be for ones who still want to use an older version because they would have to update their systems to link to archived instance in Arche.
Additional suggestion from Klaus: don't use version numbers in URLs. Older version should be dumped with changelog and the new entries are linked to the old entries with close match.

Structure

Although collections/groups are good for a nice representation, they could be problematic for data entry/usage because they are not a concept and just containers. E.g. we have hierarchically groups, like Graffito Component but it shouldn't be used for linking in OpenAtlas. Klaus answered an in between question from Alex about broader/broadMatch: broadMatch is used for external references, broader for internal.

How to proceed

We will suggest another meeting with INDIGO to discuss:
  • Identifier
  • Using of groups and collections, e.g. what to do about Graffito Component/Concept Idea

Updated by Massimiliano Carloni 8 months ago · 17 revisions

Also available in: PDF HTML TXT