Persitent identifiers in archived material

[Magnus Sälgö]

In Sweden DIGG (Agency for Digital Government) is starting to look into Persistent Identifiers for the Governments in Sweden GITHUB.

Sweden has today no solution for when persistent identifiers are archived at the Swedish National Archives to resolve them. I see a persistent identifier also need to be "available"(resolvable) from the Archives.

Question: Anything like that implemented that an identifier for a Thing also when the information is archived can be resolved? please share examples and specifications

I would like to see PID grafs from the archives ---> all peristent identifiers mentioned in the archived information can be resolved....

In wikidata that I have used a lot I have implemented the Nobelprize winners --> 
* Nobelprize winner id = 1011 --> json html
   * the same "Thing "can also be accessed using the Nobelprize id from Wikidata using the Nobelprize property P8024 --> https://hub.toolforge.org/P8024:1011?site=wd

See more in Swedish

[Pierre Grenon]

Hi Magus, 

apologies if I misunderstand the question, I'm not sure if it is generic about identifiers or specific to cases in the archival world. 

The concept you are illustrating seems to be very close to the old PURL solution that advocated governance of globally unique identifiers that are then dereferenceable. Usually identifiers are unique within a namespace that is equated with an authority.

--
You received this message because you are subscribed to the Google Groups "Records_in_Contexts_users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to Records_in_Context...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/Records_in_Contexts_users/388bd8d1-e017-4111-abee-59a25a0a208bn%40googlegroups.com.

[Pierre Grenon]

apologies, I hit a thingy too early...

For PURL, see https://en.wikipedia.org/wiki/Persistent_uniform_resource_locator

it has links to modern solutions too, especially an archival specific scheme. With PURL came purl resolver systems, ensuring redirections at the server level with built in notions of content negotiation. In some domains people have created their own PURL servers, for example in the biomedical domain: https://github.com/OBOFoundry/purl.obolibrary.org On top of this there are approaches to publish resolution for namespaces https://identifiers.org/ This is all a big issue of community governance. 

These are outside the archival world yet the problem exists in every domain; every authority designing schemes for this is always going through the hazing of finding a syntax for identifiers, and then making them resolvable as URIs. One extreme solution is to simply create globally unique ids (modulo namespace), a good example is: https://permid.org/1-5035507360 in the finance world. This is extreme -- and arguably good -- because it treats URIs as things for machines, On the other hand of the spectrum, the UK government issued a while back some guidance on building identifiers: https://www.gov.uk/government/publications/designing-uri-sets-for-the-uk-public-sector It's the other hand of the spectrum because a lot of semantics and case analysis is built into the URIs. 

In the archival world, in the UK, there was a really neat project at the National Archives a few years ago. Maybe someone on this list knows the status, there's a small series of blogs that remain most of the discussions are about IDs and you may find them useful: https://catalogueprojects.medium.com/

I had never come across PID grafs -- the idea of a graph of identifiers does seem in essence to be the idea of Linked (Open) Data and in relation to this, one of the basic FAIR principles https://www.go-fair.org/fair-principles/f1-meta-data-assigned-globally-unique-persistent-identifiers/

Again, not totally sure this is what you are asking about or if it helps, apologies if I misread your question. 
Pierre