Update the URI pattern creation of a number of class instances

[rtroncy]

See https://github.com/silknow/converter/blob/master/URI-patterns.md. I believe that the following changes should be done:

• [x] crmdig:D1_Digital_Object: currently, the URI pattern looks like http://data.silknow.org/graph/[graph-short-name]/[ID]. Instead, the URI pattern should simply be: http://data.silknow.org/object/[UUID]
• [x] ecrm:E73_Information_Object: currently, the URI pattern looks like https://data.silknow.org/informationobject/[UUID]. Instead, the URI pattern should simply be: http://data.silknow.org/object/[UUID]. Between, what is this instance supposed to be? I do have the same question for what does ecrm:E89_Propositional_Object represent? (looking at http://data.silknow.org/object/a8c5aa2b-9426-32e9-a632-496243adde61 and nearby does not tell me)
• [x] ecrm:E9_Move: we do not seem to have anymore any instances of this class. Is it normal?
• [x] ecrm:E11_Modification: currently, the URI pattern looks like http://data.silknow.org/modification/[UUID]. Instead, the URI pattern should simply be: http://data.silknow.org/event/[UUID]. It seems that only GARIN and Imatex are providing instances of this class. The type seems to always be "restoration". In the case of Imatex, it would be good to extract the temporal information of the restauration event.
• [x] ecrm:E14_Condition_Assessment: none of the links I have clicked are dereferencable, why? What is the purpose of those instances?
• [x] ecrm:E31_Document: why do we create instances of this class in the first place? This seems relevant only for UNIPA?

[tschleider]

Changes pushed, but not yet reconverted / uploaded:

• D1: Changed the URI pattern. Seed for UUID is filename + JSON-ID
• E73: Changed the URI pattern. Seed is as usual. It is used in the mapping for "Bibliography" and "Exhibition" mappings.
• E9: This class was systematically replaced by a new class that is still not available to us. I asked Marie to temporarily change it back to E9. In the meantime I removed the mapping, I will set it up again asap.
• E11: URI pattern changed. @pasqLisena : Unless it takes you, too much time, do you have a Regex pattern in mind for Strings like this (year not always at the end, sometimes in the middle etc.): "RESTAURACIÓ*" : "Cerdà Durà, Elisabet - 2010 - / Fundació Abegg Stiftung. 1992 -" (3008-en.json)?
• E14: I'm on it, they will be dereferencable tomorrow.
• E31: It used to be in the mapping, but has been replaced now. Next time I reconvert and upload the KG they will be gone.

[rtroncy]

Don't forget to update https://github.com/silknow/converter/blob/master/URI-patterns.md accordingly.

[tschleider]

Changed the URI pattern doc.

[pasqLisena]

E11: URI pattern changed. @pasqLisena : Unless it takes you, too much time, do you have a Regex pattern in mind for Strings like this (year not always at the end, sometimes in the middle etc.): "RESTAURACIÓ*" : "Cerdà Durà, Elisabet - 2010 - / Fundació Abegg Stiftung. 1992 -" (3008-en.json)?

All is possible, but what is the date here? How this will be represented? These for me are 2 different restoration events:

• by Elisabet Cerdà Durà in 2010
• by Fundació Abegg Stiftung in 1992

Do you have a longer list of example to understand if we can always split at that /?

[tschleider]

• E14 is dereferencable now, but this highlights that it's implemented incorrectly. The actual "condition" is not in the KG right now. I'm on it.

@pasqLisena : Thanks for having a look. Here the full query for all E11s (It's not that many).

[pasqLisena]

Like this is more visible.

So, from what I see, - / is a newline character. When there is the information about "author" and date, it is always following this pattern (line type A):

(.+)(?: -|,|.) (\d{4})(?: \((.+)\))?

Where group 1 is the author, 2 is the year, 3 is the (optional) comment.

Whatever is not following this pattern (line type B) it is a comment on what has been done during the restoration (and should simply be attached to the event as a note).

When there are more lines type A, we should create one E11 for each of them. In these cases, in the string there isn't any line type B (so we do not need to link the comment to the right event).

@tschleider can I let you implement it?

[tschleider]

All changes implemented, will deploy them to stage tomorrow.

[tschleider]

Deployed to stage

[tschleider]

Examples:

• D1
• E73
• E11
• E14