TL;DR: We have a Community Forum (yay!), you can come and join it here: community.crossref.org.
Community is fundamental to us at Crossref, we wouldn’t be where we are or achieve the great things we do without the involvement of you, our diverse and engaged members and users. Crossref was founded as a collaboration of publishers with the shared goal of making links between research outputs easier, building a foundational infrastructure making research easier to find, cite, link, assess, and re-use.
Event Data uncovers links between Crossref-registered DOIs and diverse places where they are mentioned across the internet. Whereas a citation links one research article to another, events are a way to create links to locations such as news articles, data sets, Wikipedia entries, and social media mentions. We’ve collected events for several years and make them openly available via an API for anyone to access, as well as creating open logs of how we found each event.
2020 wasn’t all bad. In April of last year, we released our first public data file. Though Crossref metadata is always openly available––and our board recently cemented this by voting to adopt the Principles of Open Scholarly Infrastructure (POSI)––we’ve decided to release an updated file. This will provide a more efficient way to get such a large volume of records. The file (JSON records, 102.6GB) is now available, with thanks once again to Academic Torrents.
Our colleague and friend, Kirsty Meddings, passed away peacefully on 10th December at home with her family, after a sudden and aggressive cancer. She was a huge part of Crossref, our culture, and our lives for the last twelve years.
Kirsty Meddings is a name that almost everyone in scholarly publishing knows; she was part of a generation of Oxford women in publishing technology who have progressed through the industry, adapted to its changes, spotted new opportunities, and supported each other throughout.
This section is for Similarity Check account administrators only. It explains how administrators need to set up the iThenticate account for their organizations before starting to add other users. It walks administrators through the parts of iThenticate that only account administrators can see, so if you aren’t an account administrator, you can ignore this section and skip to using your iThenticate account.
Not sure if you’re an account administrator? When you receive your email with your login details for iThenticate, log in and check if you can see the Manage Users tab. You can only see this tab if you’re an account administrator.
If you can’t see this tab, you’re not an account administrator, and you can skip ahead to using your iThenticate account for information on how to actually use the service to check your manuscripts.
Similarity Check administrator checklist - questions to answer before you begin
As a Similarity Check service user, your organization gets reduced-rate access to the iThenticate tool from Turnitin. You and your team are able to upload your manuscript submissions and receive a Similarity Report which shows areas of overlap between the manuscript and other published works.
As an administrator, you create and manage the users on your account, and you decide how your organization uses the iThenticate tool. You’ll find the system easier to use if you set it up correctly to start with. Do consider the following questions carefully and set up your account accordingly before inviting any users to your account:
Exclusions allow you to set iThenticate to ignore particular phrases, document sections, common words, and URLs, so that they are not flagged in your account’s Similarity Reports.
We recommend starting without any exclusions to avoid excluding anything important. Once your users are experienced enough to identify words and phrases that appear frequently but are not potentially problematic matches (and can therefore be ignored) in a Similarity Report, you can start carefully making use of this feature.
It’s important to set clear guidelines for your users so they understand the settings you have already applied, and can make skilful use of the options they can choose for themselves at report level.
4. Which iThenticate repositories will you want to check your manuscripts against?
iThenticate has a number of content repositories, grouped by the type of content they contain, including: Crossref, Crossref posted content, Internet, Publications, Your Indexed Documents.
You can choose which of iThenticate’s repositories you’re checking your manuscripts against. We recommend including them all to start with.
The person (whether an administrator or a user) who sets up a folder selects the repositories to check against for that folder. When the folder is shared, other users cannot adjust the repositories selected.
5. How will you budget for your document checking fees?
There’s a charge for each document checked, and you’ll receive an invoice in January each year for the documents you’ve checked in the previous year. If you’re a member of Crossref through a Sponsor, your Sponsoring Organization will receive this invoice.
As well as setting a Similarity Check document fees budget for your account each year, it’s useful to monitor document checking and see if you’re on track. You can monitor your usage in the reports section of the iThenticate platform. Ask yourself:
How many documents do you plan to check?
How often do you want to monitor usage? Set yourself a reminder to check your usage reports periodically.
How do you want to segment your report? You can report separately by groups of users, so think about what types of groups would make sense for your circumstances.
Learn more about how usage reports can help you monitor the number of documents checked on your account.
It’s a good idea to come back to these questions periodically, consider how your use of the tool is evolving, and make changes accordingly.