In 2020 we released our first public data file, something we’ve turned into an annual affair supporting our commitment to the Principles of Open Scholarly Infrastructure (POSI). We’ve just posted the 2022 file, which can now be downloaded via torrent like in years past.
We aim to publish these in the first quarter of each year, though as you may notice, we’re a little behind our intended schedule. The reason for this delay was that we wanted to make critical new metadata fields available, including resource URLs and titles with markup.
Unfortunately, Bryan Vickery has moved onto pastures new. I would like to thank him for his many contributions at Crossref and we all wish him well.
I’m now pleased to announce that Rachael Lammey will be Crossref’s new Director of Product starting on Monday, May 16th.
Rachael’s skills and experience are perfectly suited for this role. She has been at Crossref since 2012 and has deep knowledge and experience of all things Crossref: our mission; our members; our culture; and our services.
Since we announced last September the launch of a new version of iThenticate, a number of you have upgraded and become familiar with iThenticate v2 and its new and improved features which include:
A faster, more user-friendly and responsive interface A preprint exclusion filter, giving users the ability to identify content on preprint servers more easily A new “red flag” feature that signals the detection of hidden text such as text/quotation marks in white font, or suspicious character replacement A private repository available for browser users, allowing them to compare against their previous submissions to identify duplicate submissions within your organisation A content portal, helping users check how much of their own published content has been successfully indexed, self-diagnose and fix the content that has failed to be indexed in iThenticate.
A re-cap We kicked off our Ambassador Program in 2018 after consultation with our members, who told us they wanted greater support and representation in their local regions, time zones, and languages.
We also recognized that our membership has grown and changed dramatically over recent years and that it is likely to continue to do so. We now have over 16,000 members across 140 countries. As we work to understand what’s to come and ensure that we are meeting the needs of such an expansive community, having trusted local contacts we can work closely with is key to ensuring we are more proactive in engaging with new audiences and supporting existing members.
The web deposit form is suitable for making small numbers of deposits, and you do not need any knowledge of XML to use it. You can use this form to deposit metadata for journals, books, conference proceedings, reports, and dissertations. You can also upload NLM or JATS-formatted XML using this form.
How to use the web deposit form to register your content
Step one: Select your content type
Start at the web deposit form and select the type of content you want to register: journal, book, conference proceedings, report or dissertation. Different fields will appear depending on what you’ve chosen.
Step two: Add the content you want to register
Journals
You can deposit a journal-level DOI only or DOIs for each article within a given issue.
Register DOIs for articles - you can register articles for up to one issue in any deposit. On the first screen, enter information for the relevant journal or issue, then click add articles. After you’ve added information for each article, click on Add another article to register the next article. When you are done, click Finish.
Register a journal-level DOI only - on the first screen, enter the information for the relevant journal or issue and click Submit journal/issue DOI.
Please note: when you register your first item, be really careful about the journal title you enter - this will create a journal title record and any future submissions will have to match this. Your journal title doesn’t have to match the title in the ISSN portal, but if you do want it to match, make sure to check what this is before you register your first item.
Books
You can register both book- and chapter-level information. Add you content and select Submit Book DOI to deposit a title-level DOI, or select Add Chapters to enter metadata for chapters attached to the book being registered. For series and sets, only one volume can be registered at a time.
Conference proceedings
Enter event and conference paper information. Select Add Papers to enter metadata for conference papers.
Reports
Select Submit Report DOI to deposit a single report DOI, or select Add Content Item if the report contains multiple chapters or papers.
Dissertations
Complete the fields and click Submit dissertation.
Step three: Login and submit your content
Login with your Crossref account credentials, and then add the email address that should receive the submission log email. Even if your login username is your email address, you still need to add an email address to receive the submission log email. It can be the same or different from the email you used as your login username. Finally, click Deposit.
Your submission is then added to our submission queue. When we’ve processed your file we’ll send you a log via email (to the address you gave us in step three). You must review this log to make sure your content was registered successfully. Learn more about error and warning messages.
We also send you a copy of the XML that has been generated by the web deposit form. This XML is just for your records - you don’t need to do anything with it. If changes or corrections need to be made to your metadata record, you can edit and submit the XML instead of re-entering your metadata into the form. If you do edit the XML, be sure to increment the value in the <timestamp> field to ensure a successful update.
Web deposit form limitations and how to work around them
There are some metadata elements that you can’t currently register as part of your initial deposit in the web deposit form. However, you can add many of these to an existing deposit later on, using our other tools. Here’s a list of the elements that can’t currently be included in your initial deposit with the web deposit form, and your options for adding them later:
archive locations, and article numbers or IDs can’t be registered using the web deposit form.
Funding and license information, Similarity Check URLs, STM-article sharing framework (stm-asf) license information, and text and data mining URLs can be added to existing DOIs in bulk using a supplemental metadata upload.
References: use Simple Text Query to match and deposit references to existing DOIs.
How to use the web deposit form to upload a JATS or NLM file
You can use the web deposit form to upload an XML file built according to the NLM or JATS document type definition (DTD) publishing tag set. Find out more.
How to use the web deposit form for supplemental metadata upload using a .csv file
Supplemental metadata upload enables members to add metadata elements to existing DOIs in bulk by uploading a .csv file via the web deposit form. You can use it to add funding metadata, license metadata, funding and license metadata together, Similarity Check URLs, or STM-article sharing framework (stm-asf) license metadata.
Click the choose file button next to csv file information and select your .csv file for upload
Enter the email address that should receive the submission log email
Click upload csv data
Some initial validation relating to formatting is performed upon upload. Incomplete or incorrect files will return an error message, and will not be deposited. If the file passes the initial validation, it will be converted to XML, and registered with us. Additional validation is performed upon deposit.
You will receive a submission log when your deposit is complete. Please review the log to be sure your DOIs have been updated successfully.
Please contact us with questions or comments about your .csv upload. If you are reporting problems with a .csv upload, please attach the .csv file to your support request.
Specifications for all .csv files
Files submitted for supplemental metadata upload using a .csv file must comply with these specifications:
Don’t use commas (,) or quotation marks (") within a column value
Dates must be in the format: YYYY-MM-DD
If metadata is not available for an item, leave the cell blank. If an entire column is not populated, you may omit it. Do not enter placeholders such as n/a or -, as this will cause your deposit to fail, or cause incorrect metadata to be attached to a DOI
Files may be up to 45 MB in size. We automatically split the file into batches of 4,000 DOIs for processing. We send you two emails for each batch: a submission log, and a copy of the submitted XML, so uploading a large file may result in many emails.
<funder_name>: name of the funding agency as it appears in the Funder Registry. Learn more about accessing the Funder Registry.
<funder_identifier>: funding agency identifier in the form of a DOI
<award_number>: grant number or other fund identifier
If a DOI has multiple funders, the DOI must be repeated for each funder. We recommend that all available metadata is deposited. If a piece of funding metadata is not available (for example, a grant number) the field should be left blank.
Prepare your .csv file for funding and license metadata
Funding and license metadata may be combined into a single file. The order is important: please include columns in the order listed below (*=required):
DOI: the DOI whose metadata is being updated*
<funder_name>: name of the funding agency* as it appears in the Funder Registry. Learn more about accessing the Funder Registry
<funder_identifier>: funding agency identifier in the form of a DOI*
<award_number>: grant number or other fund identifier*
<license_ref>: license URL
<license_ref applies_to="vor">: license URL for version of record
<vor_lic_start_date>: start date of version of record license
<license_ref applies_to="am">: license URL for accepted manuscript
<am_lic_start_date>: start date of accepted manuscript license
<license_ref applies_to="tdm">: license URL for accepted manuscript
<tdm_lic_start_date>: start date of accepted manuscript license
<resource content_version="vor">: item URL for version of record
<resource content_version="vor" mime_type="?">: item URL for version of record with MIME type
<resource content_version="am">: item URL for author manuscript with MIME type
<resource content_version="am" mime_type="?">: item URL for author manuscript with MIME type
Open your file using spreadsheet software (such as MS Excel). Your file should contain two columns with the headings DOI and <item crawler="iParadigms">, where DOI is the DOI being updated and <item crawler="iParadigms"> is the URL being submitted for Similarity Check indexing. Here is an example:
Replace the example DOIs (10.5555/test1) and URLs (https://www.yoururl.com/pdf1) with your DOIs and URLs.
Be sure to save the file as .csv and not as .xlsx (or any other file type)
Some spreadsheet programs add additional quotation marks to the column headers, such as "DOI" or "<item crawler="iParadigms">". If your upload is not successful, please open your file in a text editor, and make sure the top line of the file is simply: DOI or <item crawler="iParadigms">. Edit if necessary, and resubmit.
Prepare your .csv file for STM-article sharing framework (stm-asf) license metadata
As of 2022, Crossref supports registration of STM-article sharing framework (stm-asf) license metadata. The .csv file may contain these headings (*=required):
DOI: the DOI whose metadata is being updated*
<license_ref applies_to="stm-asf">: stm-asf license URL for version of record
<stm-asf_lic_start_date>: start date of version of record license
<license_ref applies_to="am">: license URL for accepted manuscript
<am_lic_start_date>: start date of accepted manuscript license
<license_ref applies_to="tdm">: license URL for accepted manuscript
<tdm_lic_start_date>: start date of accepted manuscript license
<resource content_version="vor">: item URL for version of record
<resource content_version="vor" mime_type="?">: item URL for version of record with MIME type
<resource content_version="am">: item URL for author manuscript with MIME type
<resource content_version="am" mime_type="?">: item URL for author manuscript with MIME type
<resource>: item URL with no version type and with MIME type
<resource mime_type="?">: item URL with no version type
