To start using ARKs you need:

• A Name Assigning Authority Number (NAAN) to indicate your organization.
• Decide what ARK features you need
• Choose your local ARK resolver system, usually your website modified just enough to respond correctly to URLs containing “ark:"

Get a Name Assigning Authority Number (NAAN)

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).

Decide what ARK features you need

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,

• whether you choose to implement a shoulder for the first set of resources you assign ARKs to;
• what metadata conventions or standard you will use;
• whether you want to reveal part/whole relationships by using component qualifiers;
• which services you want to provide to your resources by using variant qualifiers;
• what policy you will follow in fulfilling your persistence commitment, for example, what kinds of change users can expect.

Read more about:

• General identifier concepts and conventions (prefix, base, suffix, shoulder, check digit, opacity)
• ARK namespaces and sub-namespaces (NAANs and shoulders)
• ARK shoulders: Do’s and Don’ts
• ARK features (including Shoulders & Metadata)
• Parts of an ARK and following questions (including qualifiers)

Consider some of the features that other ARK systems use, such as suffix passthrough feature (implemented by the Frick Collection tool). This can be useful if your resources contain many sub-resources with a large number of files per resource.

Choose your local ARK resolver ystem

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 tool is the Noid system for minting, managing, and resolving identifiers.

Issues to consider:

• Is there a service provider that I’m eligible to use? (Note that while ARKs are free, service providers will like charge a fee for the service)
• If selecting a repository system, does that system support ARKs?
• Does my organization have a commitment to providing developer support and access to servers for running a Noid system?
• Is there a Noid system available in the programming language(s) we work with?

Read more about:

• Running minters and resolvers
• ARK Implementation best practices (including Metadata & Policy statements)
• Service providers