Blog

Isaac Farley

Isaac joined Crossref in April 2018 having previously been a member. He worked for the Society of Exploration Geophysicists as their Digital Publications Manager. In addition to more than five years of experience in digital publishing, he has previous experience in community building, volunteer engagement, and education. He enjoys writing, music, podcasts, his family, and the outdoors, in no particular order. Isaac works remotely from Tulsa, Oklahoma.

Read more about Isaac Farley on their team page.

Solving your technical support questions in a snap!

My name is Isaac Farley, Crossref Technical Support Manager. We’ve got a collective post here from our technical support team - staff members and contractors - since we all have what I think will be a helpful perspective to the question: ‘What’s that one thing that you wish you could snap your fingers and make clearer and easier for our members?’ Within, you’ll find us referencing our Community Forum, the open support platform where you can get answers from all of us and other Crossref members and users. We invite you to join us there; how about asking your next question of us there? Or, simply let us know how we did with this post. We’d love to hear from you!

Flies in your metadata (ointment)

Quality metadata is foundational to the research nexus and all Crossref services. When inaccuracies creep in, these create problems that get compounded down the line. No wonder that reports of metadata errors from authors, members, and other metadata users are some of the most common messages we receive into the technical support team (we encourage you to continue to report these metadata errors). We make members’ metadata openly available via our APIs, which means people and machines can incorporate it into their research tools and services - thus, we all want it to be accurate.

Hiccups with credentials in the Test Admin Tool

TL;DR We inadvertently deleted data in our authentication sandbox that stored member credentials for our Test Admin Tool - test.crossref.org. We’re restoring credentials using our production data, but this will mean that some members have credentials that are out-of-sync. Please contact support@crossref.org if you have issues accessing test.crossref.org. The details Earlier today the credentials in our authentication sandbox were inadvertently deleted. This was a mistake on our end that has resulted in those credentials no longer being stored for our members using our Test Admin Tool - test.

Lesson learned, the hard way: Let’s not do that again!

TL;DR We missed an error that led to resource resolution URLs of some 500,000+ records to be incorrectly updated. We have reverted the incorrect resolution URLs affected by this problem. And, we’re putting in place checks and changes in our processes to ensure this does not happen again. How we got here Our technical support team was contacted in late June by Wiley about updating resolution URLs for their content. It’s a common request of our technical support team, one meant to make the URL update process more efficient, but this was a particularly large request.

Stepping up our deposit processing game

Some of you who have submitted content to us during the first two months of 2021 may have experienced content registration delays. We noticed; you did, too. The time between us receiving XML from members, to the content being registered with us and the DOI resolving to the correct resolution URL, is usually a matter of minutes. Some submissions take longer - for example, book registrations with large reference lists, or very large files from larger publishers can take up to 24 to 48 hours to process.

Changes to resolution reports

This blog is long overdue. My apologies for the delay. I promised you an update in February as a follow up to the resolution reports blog originally published in December by my colleague Jon Stark and me. Clearly we (I) missed that February projection, but I’m here today to provide said update. We received many great suggestions from our members as a result of the call for comments. For those of you who took time to write: thank you! We took extra time to review and evaluate all of your comments and recommendations. We have reached a decision about the major proposed change - removal of all filters from monthly resolution reports - as well as a couple of suggested improvements from that feedback.

Resolution reports: a look inside and ahead

Isaac Farley, technical support manager, and Jon Stark, software developer, provide a glimpse into the history and current state of our popular monthly resolution reports. They invite you, our members, to help us understand how you use these reports. This will help us determine the best next steps for further improvement of these reports, and particularly what we do and don’t filter out of them.

A simpler text query form

The Simple Text Query form (STQ) allows users to retrieve existing DOIs for journal articles, books, and chapters by cutting and pasting a reference or reference list into a simple query box. For years the service has been heavily used by students, editors, researchers, and publishers eager to match and link references.

We had changes to the service planned for the first half of this year - an upgraded reference matching algorithm, a more modern interface, etc. In the spirit of openness and transparency, part of our project plan was to communicate these pending changes to STQ users well in advance of our 30 April completion date. What would users think? Could they help us improve upon our plans?

Quarterly deposit invoices: avoiding surprises

Whenever we send out our quarterly deposit invoices, we receive queries from members who have registered a lot of backlist content, but have been charged at the current year’s rate. As the invoices for the first quarter of 2019 have recently hit your inboxes, I thought I’d provide a timely reminder about this in case you spot this problem on your invoice.

Before, during, and after - a journey through title transfers

In January, I wrote about how we’ve simplified the journal title transfer process using our new Metadata Manager tool. For those disposing publishers looking for an easy, do-it-yourself option for transferring ownership of your journal, I suggest you review that blog post. But, whether you choose to process the transfer yourself via Metadata Manager or need some help from Paul, Shayn, or myself, there’s more to a transfer than just the click of a transfer button or the submission of an email to support@crossref.org, as I’m sure those of you who have been through a title transfer can attest.