OpenAtlas

h1. Welterbe Salzkammergut Meeting 2024-03-27

Location: Online

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

h2. Participants

* *OpenAtlas*: Alexander Watzinger, Bernhard Koschiček-Krombholz

* *Welterbe Salzkammergut*: Bernd Paulowitz, Lara Alice Tudor

h2. About

This meeting was about question regarding entering data. A PDF from Lara with well prepared questions (in German) including screenshots is attached.

h2. Topics

* Question 4: Different order of types at detail view and input mask

  %{color:green}We (the OpenAtlas team) haven't noticed that before, thanked for the input and created an issue for this (#2246)%

* Question 5: Can sub type hierarchies be added elsewhere?

  %{color:green}Not like this. But after discussing the details we solved it with using:%

** *Place* %{color:green}for the estate%

** *Feature* %{color:green}for buildings%

** *Artifact* %{color:green}for everything else, e.g. a wall, a bench, ...%

  %{color:green}This allows for creating different vocabularies for each of these classes, which of coursed can shared between them were needed.%

* Question 6: Is it possible to use aliases for artifact?

  %{color:green}Aliases are only available for places and actors, where they are often needed. To also track an object ID (like it turned out in this case) we suggested to keep the name as a name and use an external reference system for the object ID.

  This way there is no need for an alias and the object ID is tracked in more CIDOC CRM conform way.%

* Question 7: Can the selection of elements of a type hierarchies be limited to the the last level?

  %{color:green}It's not possible to make only parts of a hierarchy selectable.

  One approach to solve this would be to make a separate custom type for every category, that should not be selectable itself.%

* Question 8: What determines the order of displayed attributes for an entity?

  %{color:green}The display of elements has a fixed order to offer consistency of the user interface. A more detailed answer was given in #2240%

* Question 9: How to prevent adding duplicate names?

  %{color:green}It can't be prevented to add duplicate names at e.g. places, actors, ... mainly because duplicate names just can happen in real life.

  But OpenAtlas offers tools at admin/data (see "manual":https://manual.openatlas.eu/admin/data_integrity_checks.html) to check for duplicate and similar names.%

* Question 10: Can the maximum zoom level of maps be changed?

  %{color:green}There are some sensible limits set by default.

  But because the requirements of projects using OpenAtlas can be quite different, it can be configured at admin/maps, see "manual":https://manual.openatlas.eu/admin/map.html%

* Question 11: How to limit rights of users for data entry?

  %{color:green}OpenAtlas provides a user system with groups with different permissions, "see manual":https://manual.openatlas.eu/admin/user.html%