Metacat

You are proposing a redirect from a Metacat docid to a DataONE Identifier -- these are not always the same value and often there is a DOI shoulder added to the Metacat docid.
In many cases (e.g., those DOIs we minted when the KNB first came online as a DataONE MN) we can successfully prepend "doi:10.5063/AA" to the Metacat docid and redirect to the #view URI. In some cases where the package has been updated after we generated the batch DOIs, this will result in an error (the docid == identifier with no DOI prefix). There is no way for us to know (in the Apache configuration where I assume these rewrite rules will exist) which is correct redirect strategy to take. There should probably be a nice error page giving suggestions about how to search to locate the package they are trying to find.

We could update the Metacat KNB skin with a informational message about the new KNB redesign with a link to the new KNB Metadata view for that package.

For the perl registry, I ended up needing another Metacat servlet method to get the docid when given a pid:
https://knb.ecoinformatics.org/knb/metacat?action=getdocid&pid=doi:10.5063/AA/nuding.7.9
We could do a similar look up of the PID given a docid, just not sure when or how to call this kind of lookup, especially if we are trying to do it outside of Metacat.

If we kept this stuff in Metacat, then /knb/metacat/<docid>/<qformat> could easily redirect to the /#view/<DOI> version of it or the #view/docid version of it as appropriate for the given docid.
Similarly, /knb/metacat?action=read&docid=<docid>&qformat=<qformat> could redirect as well. Would not want to redirect when qformat=xml, of course.