h1. INDIGO Meeting 2021-12-07

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

h2. Participants

* *OpenAtlas*: Alexander Watzinger, Bernhard Koschiček-Krombholz, Christoph Hoffmann, Nina Richards 
* *LBI ArchPro*: Geert Verhoeven, Jona Schlegel
* *ARCHE*: Massimiliano Carloni, Martina Trognitz
* *Spraycity*: Stefan Wogrin
* *TU Wien*: Benjamin Wild

The meeting is about showing how to enter data into OpenAtlas, demonstrating new features and discussing further adaptions and workflows.

h2. Administrative

* Public protocol
* Outreach, e.g. tweets about new OpenAtlas releases with Nina %{color:green} Twitter updates will be posted in Mattermost awareness by Nina to inform all members%
* Watcher at issues, Geert is added by default e.g. #1573

h2. New feature for INDIGO

* Show production of artifacts (#1500)

* %{color:green} Questions:% 
** %{color:green} would it be possible to add actors directly to the artifact without using an event in between -> events are needed for CIDOC CRM but it would be possible to make it easier in the UI%
** %{color:green} American or British English? Depends on the project's preferences%

h2. VOCABS

* Entering data, discuss workflow
** ACDH-CH services available: 
*** https://vocabs.acdh.oeaw.ac.at/en/ (readonly)
*** https://vocabseditor.acdh.oeaw.ac.at/ (editor, status unclear)
*** https://vocbench.acdh-dev.oeaw.ac.at/ (potentially productive, status unclear)
* How to sync later %{color:green} -> Best approach would be to prevent editing in two systems at the same time as much as possible. E.g. when starting adding vocabularies in OpenAtlas stop editing them in former spreadsheets%

* %{color:green} Status quo: right now INDIGO is in the concept phase regarding the vocabulary/thesaurus, after this initial phase a parallel approach would be useful; as of today the project is using spreadsheets as a base for the thesaurus, it is planned to later add it into OpenAtlas as types as well as into Vocabs  (at later phase/towards the end of the project)%
** %{color:green}the SKOS editor/vocabs editing tools but spreadsheets are used in the initial phase of the project to provide a better overview for different team members; there is the possibility to move data to the SKOS editor/Vocab editing tools in the upcoming weeks to test the concept - Problem to keep in mind with spreadsheets: invalidated information caused problems in other projects before%
* %{color:green}Vocabs provides: SKOS invocation types and possibilities to including different languages (German/English), SKOS source to add a bibliography, link to other concepts than external references, which is not possible in OpenAtlas (yet)%
* %{color:green}Problem: how to deal with changes in the thesaurus/vocabulary and how to synchronize different systems% 
* %{color:green} Most important argument for using other methods than OpenAtlas to make vocabulary: Multi-language is not supported by OpenAtlas, but crucial for INDIGO%

* %{color:green}Proposed workflow for thesaurus from OpenAtlas side:% 
** %{color:green}Thesaurus should stay flexible throughout the project%
** %{color:green}Work in OpenAtlas, as it allows flexibility and changes -> put data from spreadsheets into OpenAtlas type trees%
** %{color:green}Export data later to Vocabs and/or other systems%
** %{color:green}Synchronizing systems during the project won't be necessary then%
** %{color:green} use already existing vocabularies for commonly used attributes as colors, licences etc.%
 
** Image taken time, gets imported, add to model?
* %{color:green} Possibility to read metadata connected to single pixels/picture annotation -> one picture can have different metadata in different areas/pixel; Metadata is added to photos by software - to be discussed, in connection with ARCHE's role in the project; goal: add picture's metadata to the database when the pictures are uploaded to the system (not at the end of the project) and to fill some of the fields in OpenAtlas with the metadata provided;%
** %{color:green} Possibility: RDF%

h2. Issues

* Add references to types (#1586) needed or are reference systems sufficient? %{color:green}will be announced/implemented when necessary% 
* 3d geometries, view only, need sample data (#1573) %{color:green}still in concept phase and will be exchanged when final decisions are made%
* Dates with hours and minutes (#1574) %{color:green} hour and minute are needed for the creation of a Graffito is needed, not just for the time the picture was taken%