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:

Monospaced Font

LISTSERV Archives

LISTSERV Archives

MODS Home

MODS Home

MODS  January 2004

MODS January 2004

Subject:

Re: Content model of <relatedItem>

From:

Karen Coyle <[log in to unmask]>

Reply-To:

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

Date:

Wed, 14 Jan 2004 08:45:28 -0800

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (145 lines)

Your solution looks quite workable to me. However, an even simpler
solution would be to remove the restriction on MODS, making it
minOccurs=0. As you found, the requirement of a field, any field, means
that even an empty note field creates a valid MODS record, and I think
we can all agree that isn't a much more useful record than one that is
truly empty.

[Aside on library practices: Library cataloging has a concept of "main
entry" which is the minimum necessary to identify an item -- generally
author + title + some edition information. If there were to be some
minimum requirement in MODS it seems that it should be aimed at
enforcing this concept of a minimum bibliographic identifier. If that
isn't enforced, then the record contents might as well be completely
optional.]

You could modify your practice and place the link in the <titleInfo>
field. As a matter of fact, it might be useful to create <titleInfo +
<title> for purposes of quick display, and use the link for "further
info". But I'm fishing here because I don't know what your application
actually will do with the link -- whether it's a "click" or an onLoad
actuate, whether it has an xlink title, etc.

Another solution would be to create an actual "related record" set of
fields from the fields available in MODS and make the choice minOccurs=0
to facilitate linking. I can see how it was an easy short-cut to
"recurse" the entire MODS record inside relatedItem, but in fact there
are things in MODS that you would never really code in relatedItem,
starting with the record level fields (date of creation, etc.), but also
things like subject headings. It's more appropriate to do as you are
doing and create a separate, complete MODS record and point to it from
the relatedItem. In MARC, the related item field contains something that
looks like a bibliographic citation: author, title, edition, date. It
has much less information than a full MARC record.

I'm glad you stumbled onto this and posted it. I hadn't really thought
about the effect of xlink on schema design, and now I see I have a lot
to think about.

kc

On Thu, 2004-01-08 at 09:58, Andrew E Switala wrote:
> Hi MODS folks,
>
> A related entry may have its own record in a MODS infoset, so that the
> <relatedItem> element referring to it needs no content, or at most
> <part> elements. For example, a record for a journal article might have
> the subelement...
>
> <relatedItem type="host" xlink:href="#issn0000-0000">
> <part>
> <detail type="volume">5</detail>
> <extent unit="pages">
> <start>5</start>
> <end>50</end>
> </extent>
> </part>
> </relatedItem>
>
> ...where the journal title, publication information, etc would be
> understood to come from the <mods> record in the same file with
> attribute ID="issn0000-0000".
>
> Since <relatedItem> is derived from <mods>, however, the example is not
> schema valid (because <mods> has to have at least one top-level
> subelement). I've been using an empty <note/> element as filler, but
> perhaps the content model of <relatedItem> could be changed. One way is
> to put the content of <mods> in a group and define both <mods> and
> <relatedItem> in terms of this group (example below), but then the
> "is-a" relationship of <relatedItem> to <mods> is lost. I'm not enough
> of a schema hacker to know if there's a better approach.
>
> --Andy
>
> <xsd:group name="modsContent">
> <xsd:choice>
> <xsd:element ref="titleInfo"/>
> <xsd:element ref="name"/>
> <xsd:element ref="typeOfResource"/>
> <xsd:element ref="genre"/>
> <xsd:element ref="originInfo"/>
> <xsd:element ref="language"/>
> <xsd:element ref="physicalDescription"/>
> <xsd:element ref="abstract">
> <xsd:annotation>
> <xsd:documentation>520</xsd:documentation>
> </xsd:annotation>
> </xsd:element>
> <xsd:element ref="tableOfContents">
> <xsd:annotation>
> <xsd:documentation>505</xsd:documentation>
> </xsd:annotation>
> </xsd:element>
> <xsd:element ref="targetAudience"/>
> <xsd:element ref="note"/>
> <xsd:element ref="subject"/>
> <xsd:element ref="classification"/>
> <xsd:element ref="relatedItem"/>
> <xsd:element ref="identifier"/>
> <xsd:element ref="location">
> <xsd:annotation>
> <xsd:documentation>852 $a $b $j
> $e</xsd:documentation>
> </xsd:annotation>
> </xsd:element>
> <xsd:element ref="accessCondition">
> <xsd:annotation>
> <xsd:documentation>506,
> 540</xsd:documentation>
> </xsd:annotation>
> </xsd:element>
> <xsd:element name="extension"
> type="extensionType"/>
> <xsd:element ref="recordInfo"/>
> </xsd:choice>
> </xsd:group>
>
> <xsd:complexType name="modsType">
> <xsd:group ref="modsContent" maxOccurs="unbounded"/>
> <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
> <xsd:attribute name="version">
> <xsd:simpleType>
> <xsd:restriction base="xsd:string">
> <xsd:enumeration value="3.0"/>
> </xsd:restriction>
> </xsd:simpleType>
> </xsd:attribute>
> </xsd:complexType>
>
> <xsd:complexType name="relatedItemType">
> <xsd:sequence>
> <xsd:group ref="modsContent" minOccurs="0"
> maxOccurs="unbounded"/>
> <xsd:element name="part" type="partType"
> minOccurs="0" maxOccurs="unbounded"/>
> </xsd:sequence>
> <!-- Attributes omitted for clarity -->
> </xsd:complexType>
--
-------------------------------------
Karen Coyle
Digital Library Specialist
http://www.kcoyle.net
Ph: 510-540-7596 Fax: 510-848-3913
--------------------------------------

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

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