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.
Metadata Manager (beta) offers a way to deposit and update metadata for journal articles for both single and multiple deposits.
You’ll now see your Metadata Manager workspace. This is where all deposits occur, both new deposits and updates to content you’ve already registered with Crossref. To return to this view at any time, click Home at the top of the screen.
Your workspace holds your list of publications, and it will be blank when you first log in. As you add the publications you want to manage to Metadata Manager, they’ll start collecting on this screen.
You can add new publications and edit existing publications you have previously submitted to our system from your workspace. You can also click into each publication and add or edit articles against them.
The home button - Return to the overview of all your publications by clicking Home.
Deposit history - See your previous deposits made via Metadata Manager (excludes deposits via other deposit methods such as HTTPS POST, or the web deposit form).
To deposit - Shows items for which you’ve entered information, but have not yet deposited with us. The number next to To deposit shows how many records are awaiting deposit.
Your username - Shows the credential you’ve used to log in. Click the down arrow to access account functions, log out, and view a tutorial of Metadata Manager.
Search publication - This search bar allows you to find and add publications to your workspace. You can search by title name or title-level DOI.
New publication - This section allows you to create a new journal and add it to your workspace.
Page owner: Sara Bowman | Last updated 2022-July-22