Fake/Placeholder Crossmark metadata deposited by Metadata Manager for <crossmark_policy>
User 'smoves' updated the metadata for 10.24113/ijohmn.v6i1.160 using Metadata Manager, to include a Crossmark update.
They entered the update in the article record in Metadata Manager and redeposited the article.
The Crossmark XML produced by Metadata Manager is as follows.
<crossmark>
<crossmark_policy>undefined/something</crossmark_policy>
<crossmark_domains>
<crossmark_domain>
<domain>psychoceramics.labs.crossref.org</domain>
</crossmark_domain>
</crossmark_domains>
<updates>
<update type="new_edition" date="2020-02-04">10.24113/ijohmn.v6i1.160</update>
</updates>
</crossmark>
"undefined/something" for crossmark_policy and "psychoceramics.labs.crossref.org" for crossmark_domain were not provided by the user and should not have been included in the deposit.
The Crossmark Policy Page DOI can be provided in MM at the journal level, in the journal title record (along with the title, ISSNs, and journal-level DOI) - but not on creating the journal level DOI, only on subsequently editing that DOI record.
Add new:
Edit:
This isn't particularly intuitive - the policy page isn't shown as a field in the journal record when users search for an existing title.
When a user fails to supply a Crossmark Policy Page DOI at the journal level in MM, but enters Crossmark metadata for the article DOI, the XML is deposited with "undefined/something" as a placeholder for the policy page DOI. This is an invalid format as the field should be a DOI. Pattern: 10\.[0-9]{4,9}/.{1,200}
- This then means the update policy is not included in the JSON output, and that prevents their Crossmark widgets from working correctly.
Because the Crossmark Policy Page DOI is a required metadata element when including Crossmark metadata, I'd suggest that if a user fails to supply a Crossmark Policy Page DOI at the journal level in MM, and then deposits an article with Crossmark Metadata, the XML should insert a default DOI that points to a Crossref policy page (until we find a better round-trip solution for having members understand and add policy URLs).
Background
Definition of ready
-
Product owner: @kmeddings / @SaraBowman -
Tech lead: @myalter -
Service:: label applied -
Definition of done updated -
Weight applied
Definition of done
-
Available via a staging URL -
Code reviewed -
Unit tests identified, implemented, and passing -
Public documentation reviewed and updated -
Knowledge base reviewed and updated -
Acceptance criteria met -
A page is created on the Crossref website as a "dummy" policy page, and is registered as a dataset to obtain a DOI -
Metadata Manager inserts this DOI into the Policy Page element whenever a user registers an article with Crossmark metadata but has not registered a policy page DOI at the journal level.
-