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  February 2006

MODS February 2006

Subject:

MODS version 3.2

From:

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

Reply-To:

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

Date:

Fri, 17 Feb 2006 16:59:56 -0500

Content-Type:

TEXT/PLAIN

Parts/Attachments:

Parts/Attachments

TEXT/PLAIN (130 lines)

We would like to make some minor changes to MODS for a version 3.2. This
will be considered an incremental version in that it will not invalidate
existing records. We plan to work on more extensive changes in a version
4.0 in the near future.

Proposed changes for MODS v. 3.2

1. Add an attribute linkInfo to <location><url> to allow for notes
associated with the link (MARC 856$z). (For DLF Registry of Digital
Masters)

We first considered adding an element like <urlNote>, but decided on an
attribute because this note is associated with the URL. You could have a
<physicalLocation> (for the repository that is responsible for the
resource) and <url> (for the URL of the resource) that are bound together
in a <location> container. So just adding a note under <location> wouldn't
tell you whether it belongs with <physicalLocation> or <url>. It is
associated with the link given in <url>, so an attribute seemed
appropriate.

2. Add enumerated values under digitalOrigin to accommodate more of those
in MARC ER 007/11 (Antecendent/source) 
(also for DLF Registry of Digital Masters)

Now the MODS values are:
born digital
reformatted digital (which means reformatted to digital from the original)
We want to add:
digitized microfilm (MARC code b)
digitized other analog (MARC code d)

In the next full version of MODS (4.0) we could change "reformatted
digital" to something more precise (to bring out that it means digitized
from analog). Since this version should not invalidate existing instances,
we would not want to make that change now.

3. Add ID attribute to part element.   This will allow the element to be
referred by an IDREF attribute from within the same document. When MODS is
used in METS documents, we need to be able to reference MODS relatedItem
and part elements using the METS div DMDID attribute (which is an IDREF
type). This makes it possible to associate particular entities represented
by divs in the structMap with particular descriptive information.

4. Restore ID attribute to relatedItem element. (It disappeared
inadvertently from Version 3.1-- was in 3.0).

5. Allow part element to be optionally empty (for when the ID and type
attribute values contain all the information needed about the part).

Example:

<mods:relatedItem ID="DMD_article01" type="constituent">
  <mods:titleInfo>
    <mods:title>Wien, 10. mai.</mods:title>
  </mods:titleInfo>
  <mods:genre>article</mods:genre>
  <mods:part ID="DMD_article01_para01" type="paragraph"/>
  <mods:part ID="DMD_article01_para02" type="paragraph"/>
</mods:relatedItem>

The idea is that it is possible to use the part element plus type
attribute to note the existence of paragraphs (as suggested in the
MODS Outline of Elements and Attributes). Given that the above construct
expresses all I needed to express (i.e. the existence of a sequence of
paragraphs in document order) it renders the text subelement
superfluous. Currently the text child element (or one of the other child
elements- detail, extent, or date- are required. 

<mods:relatedItem ID="DMD_article01" type="constituent">
  <mods:titleInfo>
    <mods:title>Wien, 10. mai.</mods:title>
  </mods:titleInfo>
  <mods:genre>article</mods:genre>
  <mods:part ID="DMD_article01_para01" type="paragraph">
    <mods:text/>
  </mods:part>
  <mods:part ID="DMD_article01_para02" type="paragraph">
    <mods:text/>
  </mods:part>
</mods:relatedItem>

6. Make a few elements global that are referenced in the DCMI Library
Application Profile (these are subelements under other elements):

dateCaptured (under <originInfo)
edition (under <originInfo>
physicalLocation (under <location>)

7. Addition of collection description elements
Most of the elements in the DCMI Collection Description Profile map
already to MODS. We are thinking we should provide for them all, since in
many cases people will be exposing their metadata in OAI as MODS, but
there may be collection description information they want along with their
items that are exposed as MODS. So the following are the elements that
would need to be added:

Accrual periodicity: defined as "The frequency with which items are
added to a collection" MODS has frequency under <originInfo>, although
this is uncontrolled text and is under <originInfo> (and used for MARC 310
information). That is used for the frequency of a publication as opposed
to the frequency of adding something to a collection. But then if what you
are describing is a collection you probably could use this frequency and
add an authority for a controlled list of values.

Accrual method: in MARC holdings this is Method of acquisition (008/07)

Accrual policy: in MARC holdings similar to Receipt or acquisition status
(008/06).

If this will require a lot of discussion I'd rather wait until the next
full version of MODS, since we want to get 3.2 out. If people think we
should pursue it now because they think it's important to have it right
away, I'll suggest some elements.

Comments welcome. We'd like to be able to put out a new schema in a few
weeks.

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]                                          ^^
^^                                                        ^^
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

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

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