Print

Print


The problem with the example is that we used our MARC to MODS stylesheet
to take what was in the MARC field 852 and put it in physicalLocation. The
MODS element does not parse the pieces. The MARC 852 has separate
subfields for location, sublocation, and classification/shelf number. The
stylesheet just puts them all in physicalLocation as a string. So I can
see why this would be confusing. We'll need to think about how we might do
this better in a conversion. However, for MODS input, I agree that your
example is definitely the way to go.

Rebecca

On Fri, 21 May 2004, Ruth Bogan wrote:

> Rebecca,
>
> Thanks for the response. I'm still a bit perplexed by the example in the
> MODS user guidelines for vesion 3.0. It shows an example:
>
>       <location authority="marcorg">
>         <physicalLocation>DLC MicRR Microfilm 82/528
> MicRR</physicalLocation>
>       </location>
>
>
>
> In the Rutgers application, we need to record both the text name of the
> owning agency as well as its MARC org code. I thought it would look
> something like this:
>
> <location>
>    <physicalLocation> New Jersey HIstorical Society</physicalLocation
>    <physicalLocation authority="marcorg">NjHi</physicalLocation>
> </location>
>
> The two examples--the one from the web site and my own--code the authority
> differently.
>
> Ruth
>
> Ruth A. Bogan
> Head, Database and Catalog Portal Management Section
> Rutgers, the State University of New Jersey
> 47 Davidson Road, Busch Campus
> Piscataway, NJ 08854-5603
> Ph.: 732-445-5906
> Fax: 732-445-5888
> Email: [log in to unmask]
>
> ----- Original Message -----
> From: "Rebecca S. Guenther" <[log in to unmask]>
> To: <[log in to unmask]>
> Sent: Wednesday, May 19, 2004 1:34 PM
> Subject: Re: [MODS] Attributes for "location"
>
>
> > Location in MODS 2.0 did not have subelements and did have the authority
> > attribute. Because MODS 3.0 now makes a distinction between an identifier
> > and an electronic location, <location> now has 2
> > subelements: <physicalLocation> (which is equivalent to the MODS 2.0
> > location) and <url>, which was added. So <physicalLocation> takes the
> > attributes that location did in 2.0: authority, displayLabel, lang,
> > xml:lang, script and transliteration.
> >
> > See the outline:
> > http://www.loc.gov/standards/mods/v3/mods-3-0-outline.html
> >
> > Rebecca
> >
> > On Wed, 19 May 2004, Ruth Bogan wrote:
> >
> > > What are the attributes for "location" and its subelement
> > > "physicalLocation" in MODS 3? I think I am confused between versions 2
> > > and 3. But also, I'm looking at the first example in the user
> > > guidelines for v.3. It shows the attribute "authority" at the
> > > "location" level, but the description directly above it shows the
> > > attribute "authority" at the subelement level.
> > >
> > > Thanks for any help through the fog here.
> > >
> > > Ruth
> > >
> > > Ruth A. Bogan
> > > Head, Database and Catalog Portal Management Section
> > > Rutgers, the State University of New Jersey
> > > 47 Davidson Road, Busch Campus
> > > Piscataway, NJ 08854-5603
> > > Ph.: 732-445-5906
> > > Fax: 732-445-5888
> > > Email: [log in to unmask]
> >
>