OK. Back to integrating the Zenodo API onto Open Context.

Another question for the #beforemoderntimes #DH #openscience #opendata set.

Shall I use EZID to mint ARK identifiers for all 1.5 million URIs managed by OC? @paregorios will Pleiades plan on minting persistent IDs for all Pleiades entities or you happy with DOIs for data dumps, and not bother with persistent IDs for more granular data?

I'm just trying to judge what is a good use of my time, and what's broadly useful.

(cc @steko)

@ekansa @paregorios what does a typical OC URI look like? I think "cool URIs" don't need an additional layer of persistence, unless 1) you've got a separate archival resource, perhaps for long term preservation 2) the additional PID is transparent, e.g. it has a different prefix than the HTTP base URL, but keeps the same suffix identifier.

Makes sense?

@steko @paregorios

Here's a typical URI:
https://opencontext.org/media/48fb6172-647a-40f6-a576-e50d006a4f52

I also have an ARK id for it:
https://n2t.net/ark:/28722/k2q244j7j

The JSON-LD representation (https://opencontext.org/media/48fb6172-647a-40f6-a576-e50d006a4f52.json) says "owl:sameAs" for the ARK id.

I just want to maximize the probability that someone can look up the citation to an OC record over the years.

@steko @paregorios
@aejolene
@sebhth

What do you all think? Will it help, harm, or "meh" to add ARK identifiers to all our URI identified data?

@ekansa

My guess is that if you have the personal/technical/resource bandwidth to do the work (ongoing basis?), then it's probably good resiliency.

@sebhth @aejolene @steko

@paregorios @steko @aejolene @sebhth

The effort is minimal, because I can script it. Getting ARKs from EZID just requires API calls.

So, ok, I'll get on it.

@ekansa @paregorios @aejolene @sebhth so ARKs are free to mint? If so, why is #DOI favoured?