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.
Subject classifications have been available via the REST API for many years but have not been complete or reliable from the start and will soon be deprecated.
The subject metadata element was born out of a Labs experiment intended to enrich the metadata returned via Crossref Metadata Search with All Subject Journal Classification codes from Scopus. This feature was developed when the REST API was still fairly new, and we now recognize that the initial implementation worked its way into the service prematurely.
Crossref and DOAJ share the aim to encourage the dissemination and use of scholarly research using online technologies and to work with and through regional and international networks, partners, and user communities for the achievement of their aims to build local institutional capacity and sustainability. Both organisations agreed to work together in 2021 in a variety of ways, but primarily to ‘encourage the dissemination and use of scholarly research using online technologies, and regional and international networks, partners and communities, helping to build local institutional capacity and sustainability around the world.
The Metadata Manager tool is in beta and contains many bugs. It’s being deprecated at the end of 2021. We recommend using the web deposit tool as an alternative, or the OJS plugin if your content is hosted on the OJS platform from PKP.
The Review selection provides a condensed view of all the metadata you’ve provided in the form, so you can check it before submitting the record for deposit. Click Continue at the top of the form, and select Review. You can also Review All submissions on the To deposit screen before submitting the deposit.
Submitting a deposit
When you have finished adding article metadata and would like to deposit, click Continue from the article form, and select Add to deposit.
You can also do this from the Record List - select the article(s) you would like to deposit by checking the box to the left of the article title. You will then see the Action menu, and you can select Add to deposit. You can also move to, duplicate, and remove selected records using these buttons in the Action menu. If you select Remove for a record that has not been deposited, it will be erased from Metadata Manager. Records previously deposited will not be deleted from our system, only removed from the Metadata Manager workspace. If you created an article outside of a volume or issue, you can associate it with a volume or issue using Move to.
To submit your item(s) for deposit, click To deposit at the top of the screen. Please submit a maximum of 20 articles at a time. This will reduce the chance of an error with Metadata Manager.
Here, you can collect and review all your journal-specific records using Review all. The system will display any errors with a red flag by the respective record(s). You must correct these errors before you can deposit. If there are no errors, the Deposit button will be activated. Click Deposit and the system will immediately process your deposit request.
Page owner: Sara Bowman | Last updated 2022-July-22