Print

Print


On Mon, 23 May 2005, Brian Tingle wrote:

> Hi,
>
> I'm working on some XSLT for MODS, and I have some questions that maybe
> someone on the list might have some feedback on.
>
> ...
> <mods:originInfo>
>       <mods:place>
>        <mods:placeTerm type="text">[Chicago, Ill.] : National
> Association for the Education and Advancement of Cambodian, Laotian and
> Vietnamese Americans (NAFEA), 1995</mods:placeTerm>
>       </mods:place>
>       <mods:dateCreated>1995</mods:dateCreated>
>       <mods:dateCreated encoding="w3cdtf"
> point="start">1995</mods:dateCreated>
>      </mods:originInfo>
> ...

Should be:

<mods:originInfo>
   <mods:place>
      <mods:placeTerm type="text">[Chicago, Ill.]
      </mods:placeTerm>
   </mods:place>
   <mods:publisher>: National Association for the Education and Advancement
    of Cambodian, Laotian and Vietnamese Americans (NAFEA)
   </mods:publisher>
   <mods:dateIssued>1995 </mods:dateIssued>
   <mods:dateIssued encoding="w3cdtf" point="start">1995</mods:dateIssued>
   </mods:originInfo>
The repetition of the date with and without the encoding is optional-- it
would be fine to just do it once with the encoding.
Publication dates are generally considered dateIssued. Could also be the
same as date created, but not necessarily. dateCreated is date of creation
of intellectual content.

I don't know why you'd want to put all this stuff into placeTerm; we would
expect to parse out the pieces. One could use a stylesheet to take the
pieces and creates an imprint (inserting ISBD punctuation if you wnated
to).

> Q1: Does putting the publisher in the placeTerm make sense?  Why
> wouldn't someone use the mods:publisher element here?  Is putting the
> date in the placeTerm valid?  If the date is in the placeTerm; should
> there even be a dateCreated?
>
> Q2: For date display, could a reasonable logic go like this?: 1) display
> unqualified date if it exists 2) if no unqualified date; only then
> display the qualified date.

I suppose you mean as an imprint statement. Sure, that makes sense.

> ...
> <mods:name type="corporate">
>       <mods:namePart>The News and Observer</mods:namePart>
>       <mods:role>
>        <mods:roleTerm type="text"
> authority="marc">Publisher</mods:roleTerm>
>       </mods:role>
>      </mods:name>
>      <mods:typeOfResource>still image</mods:typeOfResource>
>      <mods:genre>Periodicals</mods:genre>
>      <mods:originInfo>
>       <mods:dateCreated>November 2, 1997</mods:dateCreated>
>       <mods:dateCreated encoding="w3cdtf"
> point="start">1997-11-02</mods:dateCreated>
>      </mods:originInfo>
> ...
>
> Q3: In what cases should someone use name/namePart[roleTerm='Publisher']
> rather than originInfo/publisher ?  6 of one, half a dozen of the other?

It is to cover the case where you consider the publisher a contributor in
some way. If it serves the purpose of just publishing it, I'd just use
mods:originInfo:publisher. It's the case where, like in MARC, you decide
the publisher deserves an access point for some special contribution made
to the resource.

Rebecca
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^^  Rebecca S. Guenther                                   ^^
^^  Senior Networking and Standards Specialist            ^^
^^  Network Development and MARC Standards Office         ^^
^^  1st and Independence Ave. SE                          ^^
^^  Library of Congress                                   ^^
^^  Washington, DC 20540-4402                             ^^
^^  (202) 707-5092 (voice)    (202) 707-0115 (FAX)        ^^
^^  [log in to unmask]                                          ^^
^^                                                        ^^
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^


 > thanks for any insight,
>
> -- Brian
>