With EZID not accepting new users, we need an easy low-cost/free method of generating Persistent Identifiers. The latest module updates make it possible to generate and store unique & opaque ARKs locally. Users only need to request a NAAN using the Ark Alliance's NAAN request form and plug it into our module.
After inputting the NAAN (and optional shoulder value) and generating and assigning ARKs using one of the methods below, the ARK should immediately resolve to a stable, generic, site-agnostic landing page for its corresponding Omeka resource, complete with metadata and any media using the syntax http://n2t.net/[ARK]. Example: http://n2t.net/ark:/99999/mk0081pk45
There's more in-depth info on Persistent Identifiers and particular testing tasks to follow in the original testing issue.
You're free to test generating/resolving the EZID ARK or DataCite DOI identifiers as well, though I can't guarantee the testing credentials will still work. Info on generating and accessing local ARK identifiers is below.
You can do most of the testing tasks on your local machine, but for actually resolving the n2t.net URL to the Omeka item, you'll need to access my own Omeka S test instance on the dev server--the reason being, the test NAAN and Shoulder below have been specifically created to link to that domain. The URL for this instance is http://dev.omeka.org/mmckinley/omeka-s/admin but I'll create a user for you using your avianna@omeka.org address so you should receive a new user email anyway (let me know if you don't get it).
Local Ark Configuration:
NAAN: 99999
Shoulder: mk0
In production use, this is an optional field if users want to subdivide ARK-ed items under their general institutional NAAN. If you don't put anything in here, the module should create and assign a random shoulder value for consistencies sake. BUT for the purpose of this testing, 99999 is the generic ARK testing NAAN, so we need the full ark:/99999/mk0[...] bit to properly resolve to my Omeka s dev site.
Please let me know if you have any questions or if I've missed anything. Thanks!
With EZID not accepting new users, we need an easy low-cost/free method of generating Persistent Identifiers. The latest module updates make it possible to generate and store unique & opaque ARKs locally. Users only need to request a NAAN using the Ark Alliance's NAAN request form and plug it into our module.
After inputting the NAAN (and optional shoulder value) and generating and assigning ARKs using one of the methods below, the ARK should immediately resolve to a stable, generic, site-agnostic landing page for its corresponding Omeka resource, complete with metadata and any media using the syntax http://n2t.net/[ARK]. Example: http://n2t.net/ark:/99999/mk0081pk45
There's more in-depth info on Persistent Identifiers and particular testing tasks to follow in the original testing issue.
You're free to test generating/resolving the EZID ARK or DataCite DOI identifiers as well, though I can't guarantee the testing credentials will still work. Info on generating and accessing local ARK identifiers is below.
You can do most of the testing tasks on your local machine, but for actually resolving the n2t.net URL to the Omeka item, you'll need to access my own Omeka S test instance on the dev server--the reason being, the test NAAN and Shoulder below have been specifically created to link to that domain. The URL for this instance is http://dev.omeka.org/mmckinley/omeka-s/admin but I'll create a user for you using your avianna@omeka.org address so you should receive a new user email anyway (let me know if you don't get it).
Local Ark Configuration:
NAAN: 99999
Shoulder: mk0
In production use, this is an optional field if users want to subdivide ARK-ed items under their general institutional NAAN. If you don't put anything in here, the module should create and assign a random shoulder value for consistencies sake. BUT for the purpose of this testing, 99999 is the generic ARK testing NAAN, so we need the full ark:/99999/mk0[...] bit to properly resolve to my Omeka s dev site.
Please let me know if you have any questions or if I've missed anything. Thanks!