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. dfdfd
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.
On September 1st we completed the final stage of the Crossmark v2.0 release and sent an email to all participating publishers containing instructions for upgrading. The first phase of v2.0 happened when we changed the design and layout of the Crossmark box back in May of this year. That allowed us to better display the growing set of additional metadata that our members are depositing, and saw the introduction of the Linked Clinical Trials feature.
Now all publishers have the opportunity to complete the upgrade by simply replacing the Crossmark button and the piece of code that calls the box. The new button designs are, we think, a much better fit for most websites, and are designed to look more like a button than a flat logo. The new buttons are also available as .eps files for placement in PDFs.
Â
Crossmark box on a mobile phone
Most importantly, switching to 2.0 makes the Crossmark box responsive for better display on mobile devices.
Â
Just two weeks after the code release a number of publishers have already upgraded and are running Crossmark 2.0 on their content. Congrats to the Pan African Medical Journal who were the first member to upgrade just a couple of days after the release. Â Of course we realise that many members will need time to schedule the upgrade, and while we are keen to see as many early adopters as possible, we will support version 1.5 of Crossmark through to the end of March 2017.
If your content is running Crossmark 2.0 we would love to see it. Drop us a line or put a link in the comments below.