Allow the Crossmark fields in Metadata Manager for all users, not just those who have Crossmark enabled as a service in Sugar
WHAT
Metadata Manager should make the Crossmark metadata available to all users, regardless of whether or not the Crossmark service appears in their Sugar record.
WHY
Crossmark fees are now waived and we are allowing/encouraging all members to deposit Crossmark metadata.
However, Metadata Manager only displays the relevant fields to enter Crossmark metadata for users who have officially signed up to participate in Crossmark with our Membership team for whom the Crossmark service appears in their Sugar CRM record.
This is toil for the support team, who must enable Crossmark in Sugar for every member who inquires (and members can't enable this on their own). For example, one of our sponsoring orgs with 1000+ sponsored members ran a webinar to show how to add crossmark metadata, which has generated a lot of requests to enable crossmark (great!! But.. toilsome).
Additional info....
The REST API doesn't surface license and funding data deposited outside of Crossmark. For example, guidance on flagging covid 19 research free to read https://www.crossref.org/documentation/flagging_free_to_read/
For example, if you login to MM with username 'abou' no Crossmark fields appear. There is no Crossmark Policy Page DOI field in the Journal title data, and no Crossmark metadata menu to expand in the article-level metadata form.
To contrast, user 'smoves' has signed up for the Crossmark service and it appears in their Sugar record. When you login to MM with that username, the relevant Crossmark fields appear at the journal- and article-levels.
Related issue issues#602 (closed)
Definition of ready
-
Product owner: @SaraBowman -
Tech lead: @myalter -
Service:: label applied -
Definition of done updated -
Acceptance testing plan: tested on MM staging -
Weight applied
Definition of done
-
Code reviewed -
Available via a staging URL -
Knowledge base reviewed and updated -
Public documentation reviewed and updated -
Consider any impacts to current or future architecture/infrastructure, and update specifications and documentation as needed -
Acceptance criteria met -
Any member can edit/deposit crossmark metadata in Metadata Manager -
File a follow up issue to remove crossmark status from the membership or publisher object and the getPublisher prefix APIs and the sugar information and the member info data structure and sugar and internal documentation
-