Meeting 2024-12-19 » History » Version 5
Alexander Watzinger, 2024-12-20 13:56
| 1 | 1 | Alexander Watzinger | h1. Welterbe Salzkammergut Meeting 2024-12-19, 14:00 |
|---|---|---|---|
| 2 | |||
| 3 | 3 | Alexander Watzinger | Location: ACDH-CH, Bäckerstraße 13, room 2D (the big one next to the kitchen in 2nd floor) |
| 4 | 1 | Alexander Watzinger | Updated information in the course of the meeting is %{color:green}in color% and/or marked with an ✅. Every participant is welcome to add and adapt. |
| 5 | |||
| 6 | h2. Participants |
||
| 7 | |||
| 8 | 4 | Alexander Watzinger | * *OpenAtlas*: Alexander Watzinger, Nina Richards, Olivia Reichl |
| 9 | 1 | Alexander Watzinger | * *Welterbe Salzkammergut*: Bernd Paulowitz, Lara Alice Tudor, Renate Bornberg |
| 10 | |||
| 11 | 5 | Alexander Watzinger | h2. %{color:green}Topics discussed in the meeting% |
| 12 | 1 | Alexander Watzinger | |
| 13 | 5 | Alexander Watzinger | We discussed a lot in the meeting. Once the cooperation starts we can look at these topics in more detail. |
| 14 | |||
| 15 | h3. Multiple supers for place subs |
||
| 16 | |||
| 17 | Because some features may encompass multiple places (areas) the question is how to deal with that. |
||
| 18 | One possibility would be to allow e.g. multiple places as super for one feature. For more information see #2436 |
||
| 19 | |||
| 20 | h3. Specialized views for data entry |
||
| 21 | |||
| 22 | Because of the challenge that short-time involved persons enter data we might develop specialized views for data entry. |
||
| 23 | The aim would of course also be to make this in a most generic way so that it can be used for different scenarios and projects too. |
||
| 24 | |||
| 25 | *Splitting data entry forms* |
||
| 26 | Because a lot of types with different priorities and maybe even interconnected dependencies are needed one solution would be to split theses forms to enter data step by step. |
||
| 27 | |||
| 28 | *Auto generate names* |
||
| 29 | A challenge when short-time involved persons enter data in this project seemed to be the naming of entities. |
||
| 30 | One solution would be that names are generated automatically, e.g. base type name and id |
||
| 31 | |||
| 32 | *Importing places with geolocations* |
||
| 33 | Geolocated places can be imported. We will have to look in detail at provided data once available if the build in import suffice or we need some extra scripts/functionality. |
||
| 34 | |||
| 35 | *Using imported places for data entry* |
||
| 36 | Once we have clarified the import of places we can look into using provided information for data entry. |
||
| 37 | |||
| 38 | h3. Goobi viewer |
||
| 39 | |||
| 40 | Because we talked about data exchange with via the "Goobi viewer":https://goobi.io/goobi-viewer. This should be possible, details about it: |
||
| 41 | * Complex software for controlling and presenting digitization projects |
||
| 42 | * Open Source (GPL2), available on "GitHub":https://github.com/intranda/goobi-viewer-core |
||
| 43 | * Supports IIIF, written in Java, provides interfaces, e.g. Swagger |
||
| 44 | * For metadata curation the ACDH-CH provides an instance of the software Goobi Workflow (and Viewer) jointly with BAS:IS, so there seem to be some experiences with it at our institute |