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:

Monospaced Font

LISTSERV Archives

LISTSERV Archives

MODS Home

MODS Home

MODS  April 2003

MODS April 2003

Subject:

Re: MODS user guidelines

From:

Suzanne Pilsk <[log in to unmask]>

Reply-To:

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

Date:

Wed, 30 Apr 2003 09:42:24 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (129 lines)

One thing that I think would be a great help would be to have some more full
examples that are not converted from MARC - but created in MODS and has some
of these "librarian" things omitted.

The guidelines and examples still seem to come from the perspective of a
converted MARC record instead of an initially created MODS record.

I am fiddling with trying to break down a record into fields so that a
citation could be built out of the data. My goal is to have the data pulled
apart logically so that it can be put together by a style sheet or rules
with out compromising the standard used for the citation.

Has anyone else done this? Anybody have anything to share?

Thanks,

Suzanne

Suzanne C. Pilsk
Cataloging Services
Smithsonian Institution Libraries
PO Box 37012
Natural History Building, Room 30- MRC 0154
Washington, DC 20013-7012
[log in to unmask]
202-357-3161


>>> [log in to unmask] 04/30/03 09:24AM >>>
We do need to be careful about confusing the MODS schema, the crosswalks,
the guidelines, etc. It is a common misconception that MARC has been
equated with AACR2, while it is intended to be used with any cataloging
code. We want MODS to be able to accommodate records using AACR2 or any
other cataloging code as well as simpler less controlled records using no
particular cataloging rules. One reason for the guidelines is for those
who do not use a set of rules so that there are still some content rules
for populating the elements. Accommodating all these needs is indeed a
challeng.

In the case of the GMD ([sound recording], etc.), it is the case that the
crosswalk says to put 245$h along with title. As I recall we debated this
early on. This discussion has convinced me that the better approach would
be to put 245$h in <physicalDescription><form> which has an attribute
authority. We could use "gmd" as the authority in these cases, which would
allow us to map from MODS to MARC and be able to put the GMD back in the
title. As you probably have noticed, we took statement of responsibility
(245$c) out of title and put it in a note (labelled as such). This is a
similar situation, where the data doesn't really belong with title.

Since it's a crosswalk change, we can make it without much of an
impact. We will just have to change it in the document on our Web site and
in our stylesheet that does the conversion. A schema change requires of
course revising the schema, which we don't want to do too oftern. We do
plan to do some changes to the schema shortly.

As for indicating cataloging rules, we have thought of that and thought it
was overkill to add. But if others think it important we could consider
putting it in recordInfo in this next set of changes. We already have a
list we use in MARC at:
http://www.loc.gov/marc/relators/reladesc.html#rela040b
I suppose we would say that if the element isn't filled in, no rules are
used or specified.

Rebecca

On Tue, 29 Apr 2003, Karen Coyle wrote:

> At 04:00 PM 4/29/2003 -0700, Roy Tennant wrote:
> >Are we visiting the sins of MARC on MODS? That is, are we once again
> >building a structure with which we can mimic the layout of a card from
> >our card catalog, without thinking critically about what metadata we
> >actually need and how to best encode it?
>
> Are we confusing LC's cross-walk and examples with the capabilities of
> MODS? There's nothing in MODS itself that seems to require the GMD. And
of
> course it would never exist in data that doesn't come from a MARC21
record.
>
> Maybe we can make more progress if we parse out this problem into its
> components:
> 1- the MODS structure
> 2- the MARC-to-MODS crosswalk
> 3- [other metadata]-to-MODS crosswalks
>
> Bruce is interested in carrying citation information in MODS, so he
> shouldn't have to be concerned about where AACR2 (library cataloging)
> elements would appear since he won't have them -- unless his citations
come
> from a library database, but I have the feeling that's not the usual
source
> for his data. Others of us are indeed taking MARC records and turning
them
> into MODS, and so we might want to address the crosswalk defined by LC
or
> develop our own. If, however, Bruce does get data that originated in a
> library catalog, he is going to see AACR2 cataloging because that's
what's
> in those records, just like he may see different citations formats from
> different publications. We can get rid of the GMD, but heading choices
will
> be according to AACR2.
>
> I also think we need to separately address the structure of MODS and the
> rules for its content. As you know, this has been the problem area for
> Dublin Core, which defines a rather relaxed structure but does not have
> cataloging rules that define the content of its fields. MARC is not just
a
> structure, at least not the way most of us refer to it -- MARC21 implies
> the use of AACR2 to determine exactly what goes into a title or author
> field. What seems to be happening is that some people are assuming the
MODS
> also is informed by AACR2, and others have no interest in AACR2 at all.
So
> we need get clear about this -- will there be a way to know what rules
were
> used to create the MODS record? Do we know now if the record originated
as
> a MARC21 record? Is there a way to say that the record was derived from
a
> PubMed record structure, or an MLA-formatted bibliography.?
>
> I don't think we should go too far down this road, but I fear that if we
> don't de-couple the record format and the bibliographic rules we'll
> continue to have confusion of purpose.
>
> kc
>

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