Blog

Rachael Lammey

Based in Bristol, UK, Rachael leads Crossref’s approach to community-focused product development, consulting with members, users, and other open scholarly infrastructure organisations to help focus the organisation’s priorities and deliver on our ambitious roadmap. Rachael worked her way up through editorial groups at a scholarly publisher before joining Crossref as a Product Manager in 2012. In that role she introduced ORCID Auto-update and oversaw improvements to Crossmark and Similarity Check. In the Community team she initiated our important partnership with the Public Knowledge Project, grew adoption of preprints, grants, and data citation, and a brief strint in R&D saw her engage new technical and community iniiatives such as crowd-sourcing retrations and updates. Rachael took over as Director of Product in May 2022.

Read more about Rachael Lammey on their team page.

Using the Crossref REST API. Part 3 (with SHARE)

As a follow-up to our blog posts on the Crossref REST API we talked to SHARE about the work they’re doing, and how they’re employing the Crossref metadata as a piece of the puzzle.  Cynthia Hudson-Vitale from SHARE explains in more detail…

Preprints are go at Crossref!

Rachael Lammey

Rachael Lammey – 2016 November 02

In PersistencePreprints

We’re excited to say that we’ve finished the work on our infrastructure to allow members to register preprints. Want to know why we’re doing this? Jennifer Lin explains the rationale in detail in an earlier post, but in short we want to help make sure that:

  • links to these publications persist over time
  • they are connected to the full history of the shared research results
  • the citation record is clear and up-to-date

Doing so will help fully integrate preprint publications into the formal scholarly record.

Using the Crossref Metadata API. Part 2 (with PaperHive)

We first met the team from PaperHive at SSP in June, pointed them in the direction of the Crossref Metadata API and let things progress from there. That’s the nice thing about having an API - because it’s a common and easy way for developers to access and use metadata, it makes it possible to use with lots of diverse systems and services.

So how are things going? Alexander Naydenov, PaperHive’s Co-founder gives us an update on how they’re working with the Crossref metadata:

Using the Crossref Metadata API. Part 1 (with Authorea)

Did you know that we have a shiny, not so new, API kicking around? If you missed Geoffrey’s post in 2014 (or don’t want a Cyndi Lauper song stuck in your head all day), the short explanation is that the Crossref Metadata API exposes the information that publishers provide Crossref when they register their content with us. And it’s not just the bibliographic metadata either-funding and licensing information, full-text links (useful for text-mining), ORCID iDs and update information (via Crossmark)-are all available, if included in the publishers’ metadata.

The Wikipedia Library: A Partnership of Wikipedia and Publishers to Enhance Research and Discovery

Back in 2014, Geoffrey Bilder blogged about the kick-off of an initiative between Crossref and Wikimedia to better integrate scholarly literature into the world’s largest knowledge space, Wikipedia. Since then, Crossref has been working to coordinate activities with Wikimedia: Joe Wass has worked with them to create a live stream of content being cited in Wikipedia; and we’re including Wikipedia in Event Data, a new service to launch later this year.

Auto-Update Has Arrived! ORCID Records Move to the Next Level

Crossref goes live in tandem with DataCite to push both publication and dataset information to ORCID profiles automatically. All organisations that deposit ORCID iDs with Crossref and/or DataCite will see this information going further, automatically updating author records.