Having joined the Crossref team merely a week previously, the mid-year community update on June 14th was a fantastic opportunity to learn about the Research Nexus vision. We explored its building blocks and practical implementation steps within our reach, and within our imagination of the future.
Read on (or watch the recording) for a whistlestop tour of everything – from what on Earth is Research Nexus, through to how it’s taking shape at Crossref, to how you are involved, and finally – to what concerns the community surrounding the vision and how we’re going to address that.
TL;DR A year ago, we announced that we were putting the “R” back in R&D. That was when Rachael Lammey joined the R&D team as the Head of Strategic Initiatives.
And now, with Rachael assuming the role of Product Director, I’m delighted to announce that Dominika Tkaczyk has agreed to take over Rachael’s role as the Head of Strategic Initiatives. Of course, you might already know her.
We will also immediately start recruiting for a new Principal R&D Developer to work with Esha and Dominika on the R&D team.
As a distributed, global, and community-led organisation, sharing information and listening to our members both online and in person has always been integral to what we do.
For many years Crossref has held both in-person and online meetings and events, which involved a fair amount of travel by our staff, board, and community. This changed drastically in March 2020, when we had to stop traveling and stop having in-person meetings and events.
The Crossref Nominating Committee is inviting expressions of interest to join the Board of Directors of Crossref for the term starting in March 2023. The committee will gather responses from those interested and create the slate of candidates that our membership will vote on in an election in September.
Expressions of interest will be due Friday, June 24th, 2022.
About the our board elections The board is elected through the “one member, one vote” policy wherein every member organization of Crossref has a single vote to elect representatives to the Crossref board.
Fully implementing Crossmark is a relatively technical process. You’ll need to include Crossmark-specific metadata for each DOI that you register. And you’ll need to add the DOI in a html meta-tag in each article landing page where Crossmark is implemented, as well as include a script in the source code for each page that calls the Crossmark dialog box.
Step one: Designate a Crossmark policy page and assign it a DOI
You’ll need a way to explain Crossmark to your readers. To do this, you’ll need a page on your website explaining that you are participating in the Crossmark service and have committed to maintaining version of record copies of content that display the Crossmark button. This page should be registered and have a DOI to enable persistent linking. It should explain your policies on corrections, retractions, withdrawals and other updates, and may contain definitions and explanations of any additional custom metadata fields that are being used. The page could also include links to other relevant policies such as author submission guidelines, and peer review guidelines. You may already have a suitable page on your website, but don’t forget to register it with us so it has a DOI.
Step two: Deposit the minimum Crossmark metadata for all your content
It’s important to apply the Crossmark button to all of your current content, not just content that has updates. The problem with partial implementation of Crossmark is that when an item of content is published, you won’t know if it might need to be updated at some point in the future. Therefore, a researcher may download a PDF article today without a Crossmark button, but if the article is subsequently updated and the Crossmark button is added, the researcher has no way of knowing if their locally-saved article is still current, as it had no Crossmark button at the point when they downloaded it. If you’re using the Crossmark service, we’d expect you to display the Crossmark button on all your content, whether or not it has an update.
The minimum metadata required for the Crossmark button to display is:
The DOI of the content the Crossmark is being applied to
The DOI for your Crossmark Policy Page
Deposit Crossmark metadata by direct deposit of XML
If you usually register your content with us by uploading XML files into the admin tool or sending us XML by HTTPS POST, then you can include Crossmark metadata in your initial deposit. You can also add Crossmark metadata to existing DOIs using a resource-only-XML deposit. Some members find our XML samples helpful for full and resource-only deposits.
Deposit Crossmark metadata the web deposit form (or if you’re still using the deprecated Metadata Manager)
Simply add your Crossmark metadata into the relevant fields.
In Metadata Manager, you need to add the Crossmark Policy Page up at journal level. Go to the journal-level record for your publication, add your Crossmark policy page DOI, and click Save.
Deposit Crossmark metadata using the Crossref plugin for OJS
This is not currently available, but should be coming soon.
Step three: Add metadata that reflects any updates to specific items
If there is an update to a content item, you need to add extra Crossmark metadata to indicate this. Updates should only be deposited for editorially significant changes - those that are likely to affect the interpretation or crediting of the work, and not for minor changes such as spelling corrections or formatting changes.
There are 12 defined types of accepted update within Crossmark:
If an update does not fall into one of these categories, it should instead be placed in the more information section of the pop-up box by being deposited as an assertion. Please note - @order is an optional attribute. If @order is absent, it will return results in the order in which you list them in your deposit, but this is not guaranteed. If you want to be sure of the order, then you can use @order. Learn more about the Crossmark deposit elements (including what is optional) in the schema.
When deposited content corrects or updates earlier content, the DOI(s) of the corrected content must be supplied in the Crossmark metadata. See the Crossref unixref documentation section on updates for examples of how this is recorded in the Crossmark metadata.
When a correction is made in situ (that is, it replaces the earlier version completely), then the DOI of the corrected content will be the same as the DOI for the original Crossref deposit. In situ updates are not considered best practice as they obscure the scholarly record.
Step four: Apply the Crossmark button to your HTML pages
Add the button
There are a number of variations of the Crossmark button available so that you can choose one that fits well on your site. You can change the Crossmark button that is used simply by changing the src attribute of the img element to point to one of the following:
Alternatively, this you can view source on this page to see the correct code snippets for each style of button.
The button can be resized according to your design needs by changing the image width in the image tag but do follow the Crossmark button guidelines.
Don’t forget to record the DOI in the HTML metadata
The Crossmark button needs to have a DOI to reference in order to pull in the relevant information. This needs to be embedded in the head of the HTML metadata for all content to which Crossmark buttons are being applied as follows:
It may appear redundant to apply Crossmark elements both in their own Crossmark namespace as well in the pdfx namespace, but the latter is necessary to ensure the Crossmark elements appear in the PDF dictionary, a specific requirement for some search engines. Any metadata found in the pdfx namespace will be copied over to the document info dictionary. Simply make sure that Crossmark metadata is in the pdfx namespace in the XMP provided to the tool.
The link structure for Crossmark links from PDFs looks like this:
domain tells the Crossmark system what kind of static content the link is coming from, and will change for different static formats (such as epub)
date_stamp tells the Crossmark system the date on which a last Major Version of the PDF was generated. In most cases, this will be the date the article was published. However, when a member makes significant corrections to a PDF in-situ (no notice issued, and no new version of the work with a new DOI) then the date_stamp should reflect when the PDF was regenerated with the corrections. The system will then use the date_stamp in order to tell whether the reader needs to be alerted to updates or not. The date_stamp argument should be recorded in the form YYYY-MM-DD (learn more about ISO 8601).
Further options: adding more information to the Crossmark button
The Crossmark box has a section for you to show any additional non-bibliographic information about the content. You decide what to include here (you are not required to add anything). In this section, Crossmark participants often include publication history dates, details of the peer review process used, and links to supporting information.
Use Metadata Manager to add custom metadata, or use the assertion element in your XML.
Several metadata elements will automatically display in the Crossmark box if you are registering them:
Author names and their ORCID iDs (learn more about contributors)
If you are already registering this additional metadata at the time you implement Crossmark, there is nothing more you need to do. If you start to register these metadata elements after you have set up Crossmark, they will automatically be put into the Crossmark box.
Page owner: Isaac Farley | Last updated 2021-October-18