This past year has been a captivating journey of immersion within the Crossref community, a mix of online interactions and meaningful in-person experiences. From the engaging Sustainability Research and Innovation Conference in Port Elizabeth, South Africa, to the impactful webinars conducted globally, this has been more than just a professional endeavour; it has been a personal exploration of collaboration, insights, and a shared commitment to pushing the boundaries of scholarly communication.
One of the challenges that we face in Labs and Research at Crossref is that, as we prototype various tools, we need the community to be able to test them. Often, this involves asking for deposit to a different endpoint or changing the way that a platform works to incorporate a prototype.
The problem is that our community is hugely varied in its technical capacity and level of ability when it comes to modifying their platform.
When each line of code is written it is surrounded by a sea of context: who in the community this is for, what problem we’re trying to solve, what technical assumptions we’re making, what we already tried but didn’t work, how much coffee we’ve had today. All of these have an effect on the software we write.
By the time the next person looks at that code, some of that context will have evaporated.
It turns out that one of the things that is really difficult at Crossref is checking whether a set of Crossref credentials has permission to act on a specific DOI prefix. This is the result of many legacy systems storing various mappings in various different software components, from our Content System through to our CRM. To this end, I wrote a basic application, credcheck, that will allow you to test a Crossref credential against an API.
You can now easily search for publications and add them to your ORCID profile in the new beta of Crossref Metadata Search (CRMDS). The user interface is pretty self-explanatory, but if you want to read about it before trying it, here is a summary of how it works.
When you go to to CRMDS, you will see that there is now a small ORCID sign-in button on the top right-hand side of the screen.
click on thumbnail to see larger image
Clicking on this button allows you to connect CRMDS to your ORCID profile and authorises CRMDS to add publications to your profile. First, if you are not already logged into ORCID, CRMDS will ask ORCID to log you in:
click on thumbnail to see larger image
Once you have logged in, ORCID will ask you if you want to allow CRMDS to be able to view and update your ORCID profile:
click on thumbnail to see larger image
After you authorise CRMDS to access your profile, you will be returned to the CRMDS screen and the top right corner of the CRMDS page will indicate that you have connected to your ORCID profile (note, you can always de-authorise CRMDS from accessing your ORCID profile in your ORCID settings):
click on thumbnail to see larger image
Once you are logged in, you can enter search terms that are likely to return records of your publications:
click on thumbnail to see larger image
Each search result will show an icon telling you whether that particular item is visible in your ORCID profile. If the item is not in your ORCID profile, you see an icon like this:
And if the item is already in your ORCID profile, you will see an icon like this:
In the following search results you can see that 1 item is already in Josiah Carberry’s profile, and 2 items are not:
Clicking on the “Add to Profile” button will confirm that you want to add the specified publication to your ORCID profile:
click on thumbnail to see larger image
After clicking on “Yes” to add the publication to your profile, the search results will refresh to reflect that the item has been added.
You can then just continue searching for and adding any publications that are not in your ORCID profile.
Note that, occasionally, you may see an orange icon that says that an item is “Not Visible”
This only occurs when you have previously added an item to your profile using CRMDS and then either:
Set the ORCID privacy for that particular work item to “Private” in your ORCID profile.
Deleted the work from your ORCID profile.
Unfortunately, CRMDS has no way to determine which of these two events occurred However, If you click on the “Not Visible” icon, you will be prompted with two ways to resolve this issue. Either you can:
Reset the privacy settings on the specified work to “Public” or “Limited”
Confirm to CRMDS that you have deleted the item from your profile.
click on thumbnail to see larger image
If the issue was your privacy settings, then once you have changed the privacy settings to public/limited you can simply click on the “Refresh” button and CRMDS will reflect the correct status of the work.
The best way to avoid this kind of confusion is to go to your ORCID settings and set the default privacy level for “works” to either “limited” or “public.”
Crossref Metadata Search is still a “Crossref Labs” project and, as such, we are very interested to hear feedback on this new ORCID functionality for CRMDS. Please send comments, etc. to: