To start using ARKs you need:
Please fill out the NAAN request form if you are interested in generating and using ARKs for your resources. While a NAAN is often associated with a single organization, if you work in a large or complex organization (e.g., a university campus), different units within it may have different needs in assigning ARKs, such as frequency, total number, and varieties of objects to identify. Independent units might need their own NAANs or “shoulders” (see ARK namespaces).
As you prepare to use ARKs for the first time, consider both the current and future potential use cases for ARKs in your organization. This may influence, for example,
Read more about:
Also consider implementing some of the features that related ARK systems use, such as suffix passthrough, which can be useful if your resources contain many sub-resources with a large number of files per resource. Also consider some of the features that related ARK systems use, such as the suffix passthrough feature (currently implemented only for ARKs stored in N2T.net). This can be useful if your resources contain many sub-resources with a large number of files per resource.
Because ARKs are free, open identifiers, there are many choices for implementing them. Some free, specialized services offer ARK assignments, such as for text deposits at the Internet Archive and for metadata vocabulary terms at YAMZ.net. At the moment, we don’t know of any general-purpose ARK service providers available to the public. ARK assignments are offered as a side-effect of working with many institutional repositories and vendors (e.g., in archiving and education).
There are also software plug-ins and microservices you can integrate with your own repository or system. The Resources area of this site provides links to available tools and to technical documentation if you choose to build your own local ARK support system. One example is the Noid system for minting, managing, and resolving identifiers.
Issues to consider:
Read more about: