Metacat

We have used a few different DOI registration approaches on the KNB:

• bulk load of all historical content (metadata and data) when we became a DataONE MN - uses the "d1/object/<pid>" endpoint for resolution
• publish requests during our UI testing stage - uses "/m/#view/<pid>"
• new publish requests now that we are deploying Metacat UI at the web root.

Generalizing this to other Metacat deployments with EZID accounts, it is reasonable to assume that their registrations drift as they migrate serves or change endpoints and it would be great to address our needs on the KNB as well as any other MNs that also manage DOIs via EZID.