Code and tables for making and maintaining datacite records and DOIs from VO resources. This uses the datacite MDS API v2, as documented on https://mds.datacite.org/static/apidoc A browser-based management page for our resources is at https://doi.datacite.org/. You'll need to sign in with the credentials from credentials.txt. This needs to be configured in a file credentials.txt in the resdir. It is parsed using a DaCHS keyValueGrammar and needs the fields user and password (for record upload with datacite), prefix (datacite assigned prefix), and endpoint (https://mds.test.datacite.org or https://mds.datacite.org). We're getting our credentials through the university library. Our contact there was Leonhard Maylein. Note that doitansform used to be svn:external but now is dual-managed here in SVN and in git, https://github.com/ivoa/vor-doi. If you make changes there, commit in both places. Also, res/vor-to-landing.xslt and static/landingpage.css are (basically) mirrored in https://github.com/ivoa/vor-to-landing, and I'd say that's now our upstream. We should merge back changes, but you need to fix two strings in vor-to-landing.xslt you get from there (see the README over there). In case you're getting a 422 from mds.datacite: That means it thinks our document is invalid. To help figuring out what's wrong, the machinery dumps the rejected metadata to $stateDir/last-mdc-failure.xml. # Landing page The dx.doi.org and Datacite redirection will redirect readers to a landing page displaying additional metadata on the dataset. The DOI must not point to dataset directly. ## Customisation By default the landing page carries neutral/generic IVOA (International Virtual Observatory Alliance) branding. This can be customised by modifying: res/vor-to-landing.xslt static/landingpage.css When editing the XSLT, it is necessary to notify DaCHS of changes with: $ touch q.rd After which DaCHS will be reload the relevant files, and changes will be become visible on the next webpage refresh. ## DOI Landing Page Guidelines Various people's (conflicting) suggestions on what makes an ideal landing page can be found at: https://wiki.earthdata.nasa.gov/display/DOIsforEOSDIS/DOI+Landing+Page http://wiki.esipfed.org/index.php/DOI_Landing_Pages # Debugging hints If the upload to datacite breaks because of schema violations, have a look at how the transformed document looks like. To do that, fetch your resource's OAI-PMH XML (e.g., go to WIRR and look for ivoid), and then run curl > tmp.xml vi tmp.xml # remove the xslt processing instruction xsltproc --stringparam doi_for_record "10.test/test" doitransform/vor-to-doi.xslt tmp.xml