LISTSERV mailing list manager LISTSERV 16.0

Help for MODS Archives


MODS Archives

MODS Archives


[email protected]


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  December 2003

MODS December 2003

Subject:

Re: A compendium of MODS questions

From:

"Rebecca S. Guenther" <[log in to unmask]>

Reply-To:

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

Date:

Fri, 12 Dec 2003 13:18:20 -0500

Content-Type:

TEXT/PLAIN

Parts/Attachments:

Parts/Attachments

TEXT/PLAIN (132 lines)

On Tue, 9 Dec 2003, Marie-Louise Ayres wrote:

> 2.  LC colleagues - any timelines on updated MODS2MARCXML and MARCXML2MODS
> stylesheets becoming available?

We posted the new schema yesterday; expect to have MARCXML2MODS very soon,
and MODS2MARCXML a little later.

> 3.  I've noticed a discrepancy between the MODS2MARC mapping for
> <originInfo><dateCaptured> and the Guidelines.  Mapping reads:
> <dateCaptured> with encoding="iso8601" 033 ind1=0 ind2=0 $a <dateCaptured>
> with point="start" and 033 ind1=2 ind2=0 first $a encoding="iso8601"
> <dateCaptured> with point="end" and 033 ind1=2 ind2=0 second $a
> encoding="iso8601"
> with the ind2=0 - Capture, defined as:
> The recording of sound, the filming of visual images, the making or
> producing of an item, including the creation of an item not involving
> recording or filming.
> However, the MODS guidelines state:
> <dateCaptured>
> "dateCaptured" contains the date on which the resource was digitized or a
> subsequent snapshot was taken. This is particularly useful for Web resources
> because of their changeability. This could be a date that the resource was
> captured or could also be the date of creation.
> I'd just like to check that <dateCaptured> is the most appropriate place to
> store information about recording dates.

The guidelines generally add to the MARC descriptions. So the text
about date captured being a digitization date is of particular
relevance to digital resources, but is in addition to the basic MARC
definitions to clarify its use. I did check with someone dealing with
recorded sound here at LC, and it is appropriate to include recording
dates under dateCaptured, whether MODS or MARC 033. Other dates relevant
may be dateIssued (260$c in MARC), which may or may not be the same as
date captured/date recorded.

> 4.  I'd really like some advice on <relatedItem type="host">, especially as
> I see there are some additions there, and there are some special issues as
> we'll be converting these records to MARCXML (and MARC doesn't handle these
> thiings particularly well!).
> We have some sample records output from ScreenSound Australia's MAVIS
> database, which incorporates the concepts of 'cover' and 'track' level
> records.  I've included the following coding:
> <relatedItem type="host">
>                 <titleInfo>
>                         <title>Josie and Me; Pagan Love Song</title>
>                 </titleInfo>
>                 <physicalDescription>1, Shellac disc (78s, transcription),
> 10" Standard Play</physicalDescription>
>                 <identifier type="local">395552</identifier>
> </relatedItem>
>
> inside a MODS record for one of the components (which includes a URL to the
> online sound recording etc.).  This will all map to various 773 sub-fields,
> but looking at the changes to V3.0, I can see quite a lot of 'part' coding.
> Any advice on how these might be used, and what MARC fields and sub-fields
> they might map to?

If you have physical description of the component (the track), it would go
in <physicalDescription> of that MODS instance and map to 300. It is not
necessary to include in <part> unless it is parsing out pieces of a
citation, or the location within a host which would otherwise not be
included elsewhere. But I'm not sure exactly what data you are proposing
putting in part, so an example would be useful. What you've done above
looks fine to me. It is questionable whether or not you need that
<physicalDescription> under relatedItem because if you had a record for
the host, it would also be included in that record.

> 5.  In V3.0, we now have
>
> <place>
> <placeTerm type="code" or "text" authority="">
>
> Could you advise whether <placeTerm> is required (as namePart is required),
> or whether it is acceptable to simply have <place>Australia</place>

You would need the subelement placeTerm; <place> is now a wrapper element
and a value wouldn't go in it.

> 6.  Now that MODS allows us to include a URL for an online resource in
> <identifier type="uri>  AND
> <location><url>
>
> are others planning to include this information in both places and only
> index one?

If it is strictly a location (which may or may not be persistent)
providing access to the resource, record in <location><url>. What we are
doing at LC is using the URL in location, and if it has been assigned a
handle (which we do for digital resources), including the "raw" handle in
<identifier>. If a URI is identified as a persistent one it can be
recorded in both places.

Clearly we need some guidelines here.

> 7.  My colleagues in the Australian National Bibliographic Database wondered
> whether any other organisations had raised the needs for a MODS equivalent
> to MARC 008 character position 28 to represent government publications?
> Would you use
>
> <genre authority="marc">government publication</genre>
>
> But in this case, there is no way to indicate the jurisdictonal level.  This
> is an issue for us as we are using MODS and our new Harvester system to pass
> metadata bout online government publications through to the NBD.

I had suggested earlier that we include the values from 008/28, but hadn't
decided whether to mix them with the MARC genre list (which means they
will be at a different level of granularity than other terms on that
list) or to make a separate identifiable list. Any other thoughts on that?

Hope this helps.

Rebecca

 > > Thanks
>
> Marie-Louise
>
>
>
> Dr Marie-Louise Ayres
> Project Manager, Music Australia
> National Library of Australia
> Parkes  ACT  2600
> Email: [log in to unmask]
> Phone: +61 2 6262 1536
> Fax:      +61 2 6273 5081
>
> http://www.musicaustralia.org
>

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

December 2023
November 2023
August 2023
July 2023
June 2023
November 2022
October 2022
September 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
May 2021
November 2020
September 2020
August 2020
July 2020
May 2020
April 2020
March 2020
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