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. Isaac joined Crossref in April 2018.

English version –– Información en español In this post, Arley Soto shares some experiences about his work as a Crossref ambassador in Latin America. When I joined as a volunteer Crossref ambassador in 2018, I never imagined that in less than two years, I would have the opportunity to travel to three

I’m happy to announce that Lucy Ofiesh has joined Crossref as our new Director of Finance and Operations. Lucy has experience supporting the sustainability and governance of not-for-profit organizations having held roles such as Executive Vice President of the Brooklyn Children’s Museum and for the last few years as Chief Operating Officer at Center for Open Science, a Crossref member.

The first version of our metadata input schema (a DTD, to be specific) was created in 1999 to capture basic bibliographic information and facilitate matching DOIs to citations. Over the past 20 years the bibliographic metadata we collect has deepened, and we’ve expanded our schema to include funding information, license, updates, relations, and other metadata.

Crossref strives for balance. Different people have always wanted different things from us and, since our founding, we have brought together diverse organizations to have discussions—sometimes contentious—to agree on how to help make scholarly communications better. Being inclusive can mean slow progress, but we’ve been able to advance by being flexible, fair, and forward-thinking.

Bibliographic references in scientific papers are the end result of a process typically composed of: finding the right document to cite, obtaining its metadata, and formatting the metadata using a specific citation style. This end result, however, does not preserve the information about the citation style used to generate it. Can the citation style be somehow guessed from the reference string only?

TL;DR On Wednesday, October 2nd, 2019 we discovered that we had accidentally pushed the main Crossref system as part of a docker image into a developer’s account on Docker Hub. The binaries and configuration files that made up the docker image included embedded passwords and API tokens that could have been used to compromise our systems and infrastructure.

We’ve all been subject to floods of conference invitations, it can be difficult to sort the relevant from the not-relevant or (even worse) sketchy conferences competing for our attention. In 2017, DataCite and Crossref started a working group to investigate creating identifiers for conferences and projects.

2019 has been busy for the Community Outreach Team; our small sub-team travels far and wide, talking to members around the world to learn how we can better support the work they do. We run one-day LIVE local events alongside multi-language webinars, with the addition of a new Community Forum, to better support and communicate with our global membership.

2019 Board Election The annual board election is a very important event for Crossref and its members. The board of directors, comprising 16 member organizations, governs Crossref, sets its strategic direction and makes sure that we fulfill our mission. Our members elect the board - its “one member one vote” - and we like to see as many members as possible voting.

This month we have officially released a new version of our input metadata schema. As well as walking through the latest additions, I’ll also describe here how we’re starting to develop a new streamlined and open approach to schema development, using GitLab and some of the ideas under discussion going forward.