OpenAtlas

I got some feedback from my nice collegauges at the ACDH-CH (thanks Vera).

There is a Vocabs instance about licenses. I don't think we will use them all because it also contains a lot of software licenses, but there is one that looks especially interesting:
Copyright Not Evaluated which is also used by ARCHE and could replace the Needs clarification item.

I also asked about CIDOC mapping and was provided with an example from CLS INFRA:

<https://clscor.io/entity/f8ca3e64-1> a crm:E13_Attribute_Assignment ;
        crm:P134_continued <https://clscor.io/entity/6f473447-3> ; <-- that's our corpus description activity
        crm:P140_assigned_attribute_to <https://clscor.io/entity/bf849ab519> ; <-- entity, the license is assigned to
        crm:P141_assigned <https://clscor.io/entity/type/license/cc0-1-0> ; <-- our license vocab (mapped to ARCHE-licenses vocab)
        crm:P177_assigned_property_of_type crm:P2_has_type .

So next questions will be:

• Do we want to use Vocabs license definitions (which) and link to them via external reference (I would like that)
• Do we change/adapt the mapping? Currently it's just a P2 -> E55 (e.g. we could put the license text in the description but how/where to map the URL, ...)

Now that it looks like we are going to create links to Vocabs for already provided licenses in the default installation, I'm thinking about how to add Vocabs to our default external reference systems.

Some clarification for this will be necessary:

• How sustainable will the usage of Vocabs be: how are the long term plans there?
• Do we add one external reference system for all of Vocabs or one for each vocabulary, e.g. ARCHE Licenses
• Can we make use of the Vocabs API like we do e.g. with Wikidata and GeoNames?
• What adaptions would be needed for the existing Vocabs import functionality?

I try to clarify these topics in the next days. In case we decide to integrate Vocabs I will make an own issue for this.

To answer my own questions from before with a lot of feedback from Christoph:

• Vocabs is planned to stay there for a long time
• We will use one external reference system for each vocabulary (like in INDIGO), so for licenses we will add ARCHE Licenses
• There is a Vocabs API via Skosmos which we can use for e.g. search functionality in the OpenAtlas user interface

We still will have to look into adaptions for existing Vocabs and INDIGO import scripts.
Also I decided to not split this issue because license changes and Vocabs integration will have to be done in one upgrade together anyway.

After some discussion with my very helpful colleagues it became clear that we would need all license related features in one go, so also:

• #2128: Option to mark files for public viewing
• #2129: Attributions for files

We still will do them one after another but they will be released together to not make users have to go through and update file licenses multiple times.

After some input from Christoph I'm afraid we have to re-open the discussion about licenses.
He made some good points why using the categories public, restricted, ... don't really make sense.

The essence from our talk was that to show/archive uploaded files it should have:

• a defined license
• a flag if it is meant to be shown/shared public

We will also implement the possibility to add creator and/or rights holder but because it's not possible to (automatically) cross check with the licenses if this is mandatory (e.g. not needed if public domain) it's the responsibility of the person who sets the public flag if this is legitimate. So in short creator/rights holder can be set (and of course shown) but won't be a criteria to show something publicly.

Anyway, I added this to the agenda of the next developers meeting.