LISTSERV mailing list manager LISTSERV 16.0

Help for MODS Archives


MODS Archives

MODS Archives


MODS@LISTSERV.LOC.GOV


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

MODS Home

MODS Home

MODS  June 2006

MODS June 2006

Subject:

Re: Crosstown Traffic

From:

Karen Coyle <[log in to unmask]>

Reply-To:

Metadata Object Description Schema List <[log in to unmask]>

Date:

Thu, 8 Jun 2006 07:39:37 -0700

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (250 lines)

The answer to Tony's question, of course, is "it depends on what you 
want to do with the record." I agree with Raymond that a common use of 
this RSS feed might be to add the records to a personal bibliographic 
system. You would probably want to also offer the records in the same 
format as would go to a system like Endnote (or create an Endnote filter 
for this format). I don't know of a library system that would use RSS in 
its cross-database functions that would require a record that is 
structured like a library catalog record.

For any bibliographic use, however, I do think that the name order 
matters. The usual purpose in distinguishing between family names and 
given names is so that citations can be presented in a bibliographical 
order, which generally means by the author's last name. This is such a 
common use of citations that I would think that it's a no-brainer of 
sorts. I would bet that the originating system (the Nature data) has its 
data in last name, forenames order (um... maybe I should check that ;-), 
and that this information is lost when the record is converted to DC. 
It's one of the things that really annoys me about DC, I have to say. 
However, even presenting the authors in the last name, forenames order 
within DC would allow for correct sorting of entries, as Raymond's 
MARC-to-MODS example shows.

Actually, I hadn't ever seen PRISM used before in a bibliographic 
retrieval system. I can see where it works well for article citations, 
something that we haven't handled terribly well in MARC and MODS due to 
the fact that libraries do not generally include individual articles in 
their catalogs. It's a real problem when we try to reconcile records 
from the abstracting and indexing databases and those from library 
catalogs.What will be difficult is getting this part converted nicely to 
MARC -- at least not without some loss:

<prism:publicationName>Nature</prism:publicationName>
<prism:publicationDate>2006-05-31</prism:publicationDate>
<prism:volume>441</prism:volume>
<prism:number>7093</prism:number>
<prism:section>Correspondence</prism:section>
<prism:startingPage>574</prism:startingPage>
<prism:endingPage>574</prism:endingPage>

Basically, you need to create a 773 field in MARC (Host item entry). It would end up looking like:

$a Nature
$d 2006-05-31
$q 441:7093:Correspondence<574 

Yuk! (If "Correspondence" is a section within the journal issue, and not 
a separate issue, it would not be included here.)

MODS has recently added a data element called "part" which I think can 
be used to give the enumeration in better detail. I don't know if anyone 
has used it and would be interested to hear how it has worked out.
kc

Tony Hammond wrote:
> Hi Raymond:
>
> Many thanks for your feedback. Fully understand where you're coming from.
> Was just looking to see how we can establish a better cross-fertilization of
> two different termsets (PRISM in the library world, and MODS in the
> publisher world). Maybe one day. (The granularity thing of course is
> interesting - but that may be a separate question.)
>
> Cheers,
>
> Tony
>
>
> On 1/6/06 02:02, "Raymond Yee" <[log in to unmask]> wrote:1/6/06 02:02
>
>   
>> Hi Tony,
>>
>> Just to look at one angle of this problem.  Let's say that I want to get
>> a record that will be easily formatted for a scholarly bibliography.  To
>> that end, I want to distinguish between the given and family names of
>> authors.  The MODS specification provides for that distinction.  See
>> http://www.loc.gov/standards/mods/v3/modsjournal.xml for an example to see
>>
>> <name type="personal">
>> <namePart type="given">Neil</namePart>
>> <namePart type="family">Brenner</namePart>
>>
>> <role>
>> <roleTerm type="text">author</roleTerm>
>> </role>
>> </name>
>>
>>
>> Now, not all MODS records will nicely split out given vs family names.
>> For example, the following LOC record
>> http://z3950.loc.gov:7090/voyager?operation=searchRetrieve&version=1.1&query=t
>> itle=%22Chaucer%20Life-%20Records%22&maximumRecords=10&recordSchema=mods3
>> shows:
>>
>>   <name type="personal">
>>     <namePart>Crow, Martin Michael</namePart>
>>
>>     <namePart type="date">1901-</namePart>
>>     <role>
>>       <roleTerm authority="marcrelator" type="text">creator</roleTerm>
>>     </role>
>>     <role>
>>       <roleTerm type="text">ed.</roleTerm>
>>     </role>
>>
>>   </name>
>>
>> Now, the fact that the name is written as "Crow, Martin Michael" does
>> help over writing it simply as Martin Michael Crow.
>>
>> When I look at 
>> http://www.nature.com/nature/current_issue/rss/index.html  (accessed
>> today at around 6pm Pacific), I see
>>
>> <item rdf:about="http://dx.doi.org/10.1038/441574c">
>> <title>Can the Internet save us from epidemics?</title>
>> <link>http://dx.doi.org/10.1038/441574c</link>
>> <description>SirKathleen Morrison, in News &amp; Views (&#8220;Failure and how
>> to avoid it&#8221; Nature440, 752&#8211;754; 2006), notes that societies have
>> often prevented collapse by adopting new technological strategies. In today's
>> world, where one of the most-talked about prospects for </description>
>> <dc:title>Can the Internet save us from epidemics?</dc:title>
>> <dc:creator>David M. Eagleman</dc:creator>
>>
>> <dc:identifier>doi:10.1038/441574c</dc:identifier>
>> <dc:source>Nature 441,  574
>> (2006)
>> </dc:source>
>> <dc:date>2006-05-31</dc:date>
>> <prism:publicationName>Nature</prism:publicationName>
>> <prism:publicationDate>2006-05-31</prism:publicationDate>
>> <prism:volume>441</prism:volume>
>> <prism:number>7093</prism:number>
>> <prism:section>Correspondence</prism:section>
>> <prism:startingPage>574</prism:startingPage>
>>
>> <prism:endingPage>574</prism:endingPage>
>>
>>
>> </item>
>>
>> My question:  if you were to present this record in MODS, would you be
>> parsing out  David M. Eagleman to be family name = Eagleman and given
>> name to be "David M.".  That is, are we going to get metadata of finer
>> granularity through MODS or ONIX than what you are currently putting
>> out?  If so, then I'd definitely be interested.  If not, I would
>> probably have code to parse out whatever you have (Since there is no
>> universal agreement on the metadata specs and since I have had to deal
>> with enough systems, whether you show me DC, or PRISM or MODS doesn't
>> really matter -- unless you get metadata of finer granularity in one
>> other the others.)
>>
>> There are other issues to consider -- but let me just throw in this one
>> observation for now.
>>
>> -Raymond
>>
>> Tony Hammond wrote:
>>     
>>> Hi All:
>>>
>>> In common with many other scholarly publishers Nature Publishing Group makes
>>> citation level metadata available through its RSS feeds using the DC [1] and
>>> PRISM [2] vocabularies, see
>>>
>>>     http://www.nature.com/rss
>>>
>>> It is also experimenting an SRU wrapper service into its search indexes
>>> again exposing result records in DC and PRISM, see
>>>
>>>     http://nurture.nature.com/search
>>>
>>> Question: Would it be useful (or even helpful) to also expose this metadata
>>> in MODS? As a complement to DC/PRISM? (And what about ONIX?) What is the
>>> sweet spot for libraries/publishers? (We can't really do this without some
>>> feedback from you guys. We may not have that level of imagination. Believe.
>>> :~)
>>>
>>> What do libraries want? What do end-users want? What can publishers do to
>>> improve the overall situation? To make our metadata feeds more widely
>>> useful?
>>>
>>> Our general perception is that an open disclosure of our metadata records
>>> will facilitate a third party service ecology which can only be of benefit
>>> to all.
>>>
>>> Looking for answers. Pretty, please.
>>>
>>> Cheers,
>>>
>>> Tony
>>>
>>> --
>>> Tony Hammond
>>>
>>> New Technology, Nature Publishing Group
>>> 4 Crinan St., London N1 9XW, UK
>>>
>>> tel:+44-20-7843-4659
>>> mailto:[log in to unmask]
>>> --
>>>
>>> [1] http://dublincore.org/
>>>
>>> [2] http://prismstandard.org/
>>>
>>> "The Publishing Requirements for Industry Standard Metadata (PRISM)
>>> specification defines an XML metadata vocabulary for syndicating,
>>> aggregating, post-processing and multi-purposing magazine, news, catalog,
>>> book, and mainstream journal content. PRISM provides a framework for the
>>> interchange and preservation of content and metadata, a collection of
>>> elements to describe that content, and a set of controlled vocabularies
>>> listing the values for those elements."
>>>
>>> *****************************************************************************
>>> ***   
>>> DISCLAIMER: This e-mail is confidential and should not be used by anyone who
>>> is
>>> not the original intended recipient. If you have received this e-mail in
>>> error
>>> please inform the sender and delete it from your mailbox or any other storage
>>> mechanism. Neither Macmillan Publishers Limited nor any of its agents accept
>>> liability for any statements made which are clearly the sender's own and not
>>> expressly made on behalf of Macmillan Publishers Limited or one of its
>>> agents.
>>> Please note that neither Macmillan Publishers Limited nor any of its agents
>>> accept any responsibility for viruses that may be contained in this e-mail or
>>> its attachments and it is your responsibility to scan the e-mail and
>>> attachments (if any). No contracts may be concluded on behalf of Macmillan
>>> Publishers Limited or its agents by means of e-mail communication. Macmillan
>>> Publishers Limited Registered in England and Wales with registered number
>>> 785998 
>>> Registered Office Brunel Road, Houndmills, Basingstoke RG21 6XS
>>> *****************************************************************************
>>> ***
>>>   
>>>       
>
>
>   

-- 
-----------------------------------
Karen Coyle / Digital Library Consultant
[log in to unmask] http://www.kcoyle.net
ph.: 510-540-7596
fx.: 510-848-3913
mo.: 510-435-8234
------------------------------------

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

February 2020
January 2020
December 2019
October 2019
September 2019
August 2019
June 2019
May 2019
March 2019
February 2019
January 2019
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 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
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
February 2008
January 2008
December 2007
November 2007
October 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
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
October 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager