Hi Jonathan,

It *is* confusing, I know, but here's the deal: our old agreement with
libraries is for a query process that accesses the complete crossref
metatdata database, but only on a query-by-query database. The new "web
services" agreement for libraries (yet to be finalized) covers a service
that delivers all or part of the metadata in the form of complete
records, for those publishers who wish to participate. We wanted a new
service that would allow users to re-purpose and display the metadata
under certain conditions, and our membership agreed to this as long as
they could decide to exclude their data from select partnerships if they
so desired.

So the RFP follows the latter model, as a free deal for the winning
proposal. Libraries currently do not pay for an account on the CrossRef,
and the new service will likely have an annual fee associated with it.
We are using the RFP in part to see how libraries might want to
re-purpose the metadata.

Hope that helps,
Amy

Jonathan Rochkind wrote:
> I don't understand. We already have a license to use CrossRef. You are
> saying that we are free to ignore this license so long as we are
> creating something for 'this RFP initiative', because eventually we'll
> get some other license that hasn't yet been written instead?  That
> doesn't quite make sense.
>
> Jonathan
>
> Amy Brand wrote:
>> Nathan,
>>
>> The agreement you are referring to below doesn't apply to services that
>> may emerge from this RFP initiative -- CrossRef hasn't drafted any such
>> agreement yet, but the intention is in fact to allow display of CrossRef
>> metadata in the new services. The reason for the change is that
>> participating publishers can opt out any metadata sharing partnership if
>> they like, on a case by case basis. So far, with the commercial metadata
>> sharing partnerships we have established, very few publishers have opted
>> out, to give you some indication. Please let me know if you have other
>> questions.
>>
>> Thanks,
>> Amy
>>
>> Nathan Vack wrote:
>>> From the license:
>>>
>>> a. The Library may retrieve DOIs and metadata by batch or one at a
>>> time. The Library may use retrieved DOIs and metadata to make
>>> persistent links to full-text works online, to make link resolvers
>>> function better and clean up its own indices, abstracts and record
>>> locators, the Library may cache the DOIs and incorporate DOIs into
>>> their content and library systems. The Library may use the DOIs and
>>> metadata for scholarly, research, educational, personal or non-
>>> commercial purposes.
>>>
>>> b. Any other use of metadata is prohibited. For example, the Library
>>> may not, and may not permit others to, use metadata to create tables
>>> of contents, abstracts or indices. The Library also may not cache
>>> metadata (except temporarily during retrieval and use in a link
>>> resolver; it may, however, cache DOIs). For avoidance of doubt, the
>>> Library may not, and may not permit others to, redistribute, copy,
>>> print, archive, backup, reserve or loan any of the metadata (except
>>> incidentally where DOIs and metadata have been incorporated into the
>>> Library's content and/or systems.)
>>>
>>> Thanks to Eric Larson for actually reading it before we wrote one of
>>> these.
>>>
>>> If you're thinking about writing one of these, remember: you can't
>>> make anything public. Yawn.
>>>
>>> -Nate
>>> UW - Madison
>>>
>>> On Jun 13, 2007, at 4:25 AM, Amy Brand wrote:
>>>
>>>>
>>>>
>>>> RFP
>>>> *REQUEST FOR PROPOSALS: INNOVATIVE USES OF CROSSREF METADATA
>>>>
>>>> *CrossRef is now accepting proposals for the most original and
>>>> promising
>>>> use of CrossRef's article-level metadata as part of a scholarly
>>>> research/authoring tool or related library service. *_Free access _*to
>>>> participating publishers' metadata and DOIs will be granted to the
>>>> researcher or librarian whose proposal is selected.
>>>>
>>>>
>>>> */DEADLINE FOR PROPOSALS:/    _July 15, 2007
>>>>
>>>>
>>>> _**/WHAT TO SUBMIT:
>>>> /
>>>> **1)* *A short but thorough description of the service you would
>>>> like to
>>>> create using the CrossRef metadata,
>>>> including estimated implementation time
>>>>
>>>> **2)* *Links to software/services/protocols/standards that you may
>>>> have
>>>> implemented in the past
>>>>
>>>> **3)* *Your CV
>>>>
>>>>
>>>> **/TO WHOM:
>>>>
>>>> /*Amy Brand, PhD, Director of Business & Product Development
>>>> email: [log in to unmask]
>>>>
>>>>
>>>> By submitting a proposal, you agree to any publicity about the winning
>>>> project that CrossRef may wish to pursue.
>>>>
>>>>
>>>> *_BACKGROUND ON CROSSREF METADATA AND WEB SERVICES
>>>> _
>>>> *CrossRef is an independent membership association, founded and
>>>> directed
>>>> by publishers. CrossRef helps connect users to primary research
>>>> content
>>>> by enabling publishers to work collectively. Our citation-linking
>>>> network today covers over 27 million articles and other content items
>>>> from several hundred scholarly and professional publishers.
>>>>
>>>> CrossRef Web Services, or CWS, offers an easy-to-use suite of tools
>>>> for
>>>> authorized partners to collect metadata on a cross-publisher basis to
>>>> streamline their own crawling, indexing, and linking services. One way
>>>> to access the 27 million+ metadata records now registered in
>>>> CrossRef is
>>>> via our OAI-PMH (Open Archives Initiative Protocol for Metadata
>>>> Harvesting) interface. The CrossRef OAI-PMH repository interface
>>>> serves
>>>> as the central point for the distribution of metadata from
>>>> participating
>>>> publishers, utilizing a robust and widely adopted technology
>>>> targeted at
>>>> consumers of large quantities of metadata. Access to the CrossRef's
>>>> metadata repository is controlled by IP authentication and can be
>>>> tailored to provide specific content from select publishers to each
>>>> authorized recipient.
>>>>
>>>> The metadata in CrossRef's database consists of basic bibliographic
>>>> information for each item, including author(s), title, journal name,
>>>> ISSN, volume, issue, page, and DOI-URL pair. Here are links to some
>>>> sample CWS metadata: <http://www.crossref.org/oai-handler_sample.xml>,
>>>> <http://www.crossref.org/oai-pmh_sample2.xml>.
>>>>
>>>> Our data repository is extensive but highly variable in quality from
>>>> publisher to publisher. We have recently begun to take measures to
>>>> ensure higher quality metadata. Any suggestions you may have regarding
>>>> how best to achieve a higher level of data quality and consistency, as
>>>> part of your proposal or otherwise, would be greatly appreciated.
>>>> Different but similarly basic metadata is collected for other types of
>>>> content. In addition, many publishers now also deposit references as
>>>> part of their metadata.
>>>>
>>>> *CONTACT: *Please email [log in to unmask] with any questions you may
>>>> have about CrossRef Web Services or this RFP.
>>>>
>>>> http://www.crossref.org/03libraries/RFP_CrossRef_metadata.html
>>>>
>>>
>>
>
> --
> Jonathan Rochkind
> Sr. Programmer/Analyst
> The Sheridan Libraries
> Johns Hopkins University
> 410.516.8886
> rochkind (at) jhu.edu
>