Joe Wass – 2016 November 04
As the linking hub for scholarly content, it’s our job to tame URLs and put in their place something better. Why? Most URLs suffer from link rot and can be created, deleted or changed at any time. And that’s a problem if you’re trying to cite them.
Rachael Lammey – 2016 November 02
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:
Doing so will help fully integrate preprint publications into the formal scholarly record.
Jennifer Lin – 2016 August 25
Anna Tolwinska – 2016 April 25
Ginny Hendricks – 2015 November 11
The rebranding of Crossref was top priority when I joined in May in a new role called “Director of Member & Community Outreach”. Since then I’ve been working to understand the array of services, attributes, and audiences we have developed; to answer the questions “What do we do, for whom, and why?”
As Crossref prepares to celebrate turning fifteen at our annual meeting next week, I am thrilled to present our new brand identity with key messages and logo. And along with “thrilled” you may also detect “nervous excitement”.
Geoffrey Bilder – 2015 June 11
Anybody who knows me or reads this blog is probably aware that I don’t exactly hold back when discussing problems with the DOI system. But just occasionally I find myself actually defending the thing…About once a year somebody suggests that we could replace existing persistent citation identifiers (e.g. DOIs) with some new technology that would fix some of the weaknesses of the current systems. Usually said person is unhappy that current systems like
Geoffrey Bilder – 2015 March 17
On January 20th, 2015 the main DOI HTTP proxy at doi.org experienced a partial, rolling global outage. The system was never completely down, but for at least part of the subsequent 48 hours, up to 50% of DOI resolution traffic was effectively broken. This was true for almost all DOI registration agencies, including Crossref, DataCite and mEDRA.
At the time we kept people updated on what we knew via Twitter, mailing lists and our technical blog at CrossTech. We also promised that, once we’d done a thorough investigation, we’d report back. Well, we haven’t finished investigating all implications of the outage. There are both substantial technical and governance issues to investigate. But last week we provided a preliminary report to the Crossref board on the basic technical issues, and we thought we’d share that publicly now.
Geoffrey Bilder – 2015 January 21
So today (January 20th, 2015) the DOI HTTP resolver at dx.doi.org started to fail intermittently around the world. The doi.org domain is managed by CNRI on behalf of the International DOI Foundation. This means that the problem affected all DOI registration agencies including Crossref, DataCite, mEDRA etc. This also means that more popularly known end-user services like FigShare and Zenodo were affected. The problem has been fixed, but the fix will take some time to propagate throughout the DNS system. You can monitor the progress here:
Now for the embarrassing stuff…
Geoffrey Bilder – 2013 September 20
2017 September 18
2017 September 14
2017 September 11
2017 September 11