Comments on: ResolveRef : looking at the logs

By: perry

perry — Sat, 07 Jun 2008 09:07:53 +0000

Thanks Ed … the fuzzy match on journal titles could really help make ResolveRef a lot more user friendly.

It’s not like ResolveRef is actually getting traffic that it would generate many Crossref API requests at the moment anyway … but I can always dream

By: Ed Pentz

Ed Pentz — Fri, 06 Jun 2008 14:23:50 +0000

Hi,

CrossRef doesn’t throttle requests at all so I would suggest giving the OpenURL interface a try – http://www.crossref.org/requestaccount/

There are some limitations to the metadata (we don’t always get all others from some publishers, sometimes there are character encoding issues) but we do a fuzzy match on journal titles so they don’t have to be exact.

Ed Pentz, Executive Director, CrossRef

By: perry

perry — Fri, 06 Jun 2008 00:42:45 +0000

Thanks Rich. I have considered using CrossRef as a backup (or even exclusively), but from comments to your post I got the impression that CrossRef may throttle requests too much to rely on that service exclusively (even if ResolveRef is ‘non-commercial’).

Many searches fail because the journal title needs to be exactly the one PubMed uses. The new suggest feature should help with this. In your case, “Modelling” is actually spelled “Modeling” (single ‘L’) in the PubMed title . Don’t worry, I’m one of those who speak the Queen’s English and spell “Modelling” the correct way too.

By: Rich Apodaca

Rich Apodaca — Thu, 05 Jun 2008 14:24:12 +0000

Great idea. Adding CrossRef as a backup could be useful. For example, my search for:

Journal of Chemical Information and Modelling 2007 47, 1727

gave no result on ResolveRef.

I’ve thought many times about building a service like this using CrossRef exclusively.