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)
No. I guess we're all trying to guess what the future will bring. I'm a little worried about identifier soup, but I want people to be able to formally cite a specific record. It seems then that some sort of persistent ID scheme, backed by institutions beyond our own, is needed?
I like ARKs. Cheap, easy to mint. PeriodO uses them.
Now, thanks to @ekansa, I'm #reading:
“Archival Resource Key (ARK) Identifiers.” N2T.net: Resolver: Names -> Things. Accessed May 2, 2018. http://n2t.net/e/ark_ids.html.
Zotero: https://www.zotero.org/users/465/items/J9IHLSUY
To get up to speed on #ARKs so I can consider better whether we should start using them for resources in @pleiades in addition to the #CoolURIs we already mint ourselves.
Yet another rabbit hole to fall into.
John Kunze with CDL is a key architect of NOIDs, and he has lots to say about identifiers. Like everything else important, there is much to this subject.
@ekansa
OK, so I can see the resiliency advantage in third-party IDs. I guess I'd need to read up on ARKs and other options, if any.
@pleiades @steko