LISTSERV mailing list manager LISTSERV 16.5

Help for CODE4LIB Archives


CODE4LIB Archives

CODE4LIB Archives


CODE4LIB@LISTS.CLIR.ORG


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Monospaced Font

LISTSERV Archives

LISTSERV Archives

CODE4LIB Home

CODE4LIB Home

CODE4LIB  February 2008

CODE4LIB February 2008

Subject:

Re: Multiple ISBNs in COInS?

From:

Jonathan Rochkind <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Tue, 19 Feb 2008 11:09:54 -0500

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (174 lines)

Be careful though, please don't send an rft_id ISSN identifier for an
_article level_ metadata package. OCLC does this. It's wrong, as the
ISSN does not serve as an identifeir for the _article_ cited, but rather
for the journal it's in. Until I figured out what was going on, this
caused some bugs in Umlaut.

It _would_ be nice to send multiple ISSNs even for an article-level
citation. Let's say the generator of the OpenURL happens to know that
there are several variant ISSNs for the publication, that identify
differnet manifestations, but any of which are valid for the given
article citation. It would be helpful for the generator to send them all
along, in case the link resolver knows about some but not all of them,
to increase the chances that the link resolver will properly 'recognize'
the citation.

But, it unfortunately can't be done. It's not the end of the world to
realize that OpenURL isn't perfect (what is? By trying you learn from
your experience to do better next time), but I'm unconvinced that this
is actually desirable in any way instead of an oversight. One thing I
think I feel like we've learned from many of our community's recent
metadata initiatives is the importance of creating standards in such a
way that they can be further developed and/or extended in a backwards
compatible way. Ie, an OpenURL 1.1 or something, that was backwards
comptable so it could be sent to resolvers that knew no more than 1.0
without problems. This has to do with both the design of the
structure/syntax of the metadata, as well as the design of the
_processes_ of maintenance, to make this kind of extension and
development not too cumbersome socially.

Jonathan

Karen Coyle wrote:
> Ah, you're referring to rft_id, and I was looking at the ISBN element in
> the KEV Book format. So using rft_id would work.
>
> The reason for multiple ISBNs is that many MARC records have ISBNs for
> the hard copy and the paperback. Without going through some gyrations
> you don't know which is which, although for purposes like ILL either is
> valid. There are also multi-volume works that each get an ISBN.
>
> Like other FRBR "levels" manifestation has a fairly wide range of
> ambiguity. A book simultaneously published in two countries... is that
> one manifestation or two? What if they each get a separate ISBN? A
> hardback and trade paperback that come out at the same time, where the
> only difference is the cover... and the ISBN?
>
> Although I often use the shortcut of "ISBN = manifestation" the fact of
> it is that ISBNs are publisher inventory and sales numbers and are used
> in ways that are convenient for publishers. They also get mis-assigned
> frequently, as some tests being run on bib data at the Open Library are
> showing.
>
> kc
>
> Ross Singer wrote:
>> Actually, this:
>> http://alcme.oclc.org/openurl/servlet/OAIHandler/extension?verb=GetMetadata&metadataPrefix=mtx&identifier=info:ofi/fmt:kev:mtx:ctx
>>
>>
>> indicates that multiple rft_ids *are* valid, and, in fact, would have
>> to be, since you could very easily have a DOI and a PMID and, say, a
>> SICI.
>>
>> I have no idea what any resolver would do with this bundle of ISBNs,
>> of course. It also seems somewhat contrary to the intention of the
>> Book metadata format, since I think it's (in my murky view of FRBR-y
>> terms) trying to define a manifestation rather than the expression
>> level that Bill is trying to use it for. I could be weaving in my own
>> interpretations and biases there.
>>
>> An alternative would be use by-reference context objects and then make
>> the context objects available as XML. You could have multiple context
>> object available in one XML document this way. A combination of
>> COinS/unAPI could make something like this possible.
>>
>> -Ross.
>>
>> On Feb 18, 2008 6:53 PM, Karen Coyle <[log in to unmask]> wrote:
>>> Actually, the max occurrence of ALL of the KEV keys is 1 except for
>>> "au"
>>> (which is unlimited). I remember discussions in which we acknowledged
>>> that one key NE one value, eg you could input multiple values if your
>>> recipients were in agreements (a poor excuse, I know). Thus:
>>> "isbn:3333;isbn:8888". My only memory for why max=1 for all of these is
>>> that it has to do with the fact that there is no structure or
>>> dependency
>>> in KEV, so an OpenURL with keys
>>> &rft.au=nnn&rft.title=ttt&rft.au=pppp&rft.title=rrrr
>>> isn't interpretable in terms of what authors go with what titles. Why
>>> the exception for au but for no other fields? My memory fails me here.
>>> Undoubtedly it made sense at the time.
>>>
>>> kc
>>>
>>>
>>> Jay Luker wrote:
>>>> Hi William,
>>>>
>>>> According to the book KEV format (defined here:
>>>> ttp://tinyurl.com/2psmkq) the max occurrence of the isbn key is 1. I'm
>>>> assuming that by extension that means that the rft.<m-key> (i.e.,
>>>> rft.isbn) form is also limited to one occurrence. So specifying
>>>> multiple ISBNs that way is a no go.
>>>>
>>>> You can however specify multiple referent identifiers. From the KEV
>>>> Context Object format matrix (http://tinyurl.com/2r5hsc): "Multiple
>>>> instances of rft_id do not indicate multiple Referents, but rather
>>>> multiple ways to identify a single Referent"
>>>>
>>>> So I *think* what you could do is this:
>>>>
>>>> "rft_id=urn:isbn:<isbn1>&rft_id=urn:isbn:<isbn2>&..."
>>>>
>>>> Also, I'd be remiss not to point you to a more authoritative list for
>>>> OpenURL questions: http://listserv.oclc.org/scripts/wa.exe?A0=OPENURL.
>>>> Although I'm sure there's plenty of overlap in interest/knowledge in
>>>> the subject between the lists.
>>>>
>>>> --
>>>> Jay Luker [log in to unmask]
>>>> Software Engineer, Ex Libris Inc.
>>>> (617) 332-8800, x604 http://www.exlibrisgroup.com
>>>>
>>>> On Feb 17, 2008 3:14 AM, William Denton <[log in to unmask]> wrote:
>>>>> I'm hep to the COInS scene now and am using it in some lists of
>>>>> books I'm
>>>>> generating. For some of the books I know multiple ISBNs. Can I
>>>>> include
>>>>> them all in one COInS span somehow? Doing one individually makes my
>>>>> OpenURL Referrer extension clutter up the page with a lot of links.
>>>>>
>>>>> I looked at the specification but it didn't seem to cover this.
>>>>> generator.ocoins.info only seems to want one one ISBN. Putting
>>>>> multiple
>>>>> rft.isbn variables just makes the last one overpower the earlier
>>>>> ones.
>>>>>
>>>>> Any tips appreciated!
>>>>>
>>>>> Bill
>>>>> --
>>>>> William Denton, Toronto : www.miskatonic.org www.frbr.org
>>>>> www.openfrbr.org
>>>>>
>>>>
>>> --
>>> -----------------------------------
>>> Karen Coyle / Digital Library Consultant
>>> [log in to unmask] http://www.kcoyle.net
>>> ph.: 510-540-7596 skype: kcoylenet
>>> fx.: 510-848-3913
>>> mo.: 510-435-8234
>>> ------------------------------------
>>>
>>
>>
>
> --
> -----------------------------------
> Karen Coyle / Digital Library Consultant
> [log in to unmask] http://www.kcoyle.net
> ph.: 510-540-7596 skype: kcoylenet
> fx.: 510-848-3913
> mo.: 510-435-8234
> ------------------------------------
>

--
Jonathan Rochkind
Digital Services Software Engineer
The Sheridan Libraries
Johns Hopkins University
410.516.8886
rochkind (at) jhu.edu

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003

ATOM RSS1 RSS2



LISTS.CLIR.ORG

CataList Email List Search Powered by the LISTSERV Email List Manager