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  May 2003

MODS May 2003

Subject:

Re: copyright dates

From:

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

Reply-To:

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

Date:

Thu, 1 May 2003 16:31:30 -0400

Content-Type:

TEXT/PLAIN

Parts/Attachments:

Parts/Attachments

TEXT/PLAIN (95 lines)

Interesting what you've done with these dates. In your examples,
"inferred" doesn't mean anything to me. Is there a better more descriptive
name for that attribute? This is a limitation on the accuracy of the
date. Any ideas?

We had figured that if you have a date and there is no encoding specified
that it is assumed to be free text. That's why we didn't add anything like
"unstructured". In a number of places in MODS the lack of encoding or
authority means unstructured or uncontrolled. Is it necessary to
explicitly say that? If so, I would think that in terms of dates, it would
be encoding="unstructured", rather than type (also since we now might have
type=copyright under dateIssued).

Rebecca

On Thu, 1 May 2003, Tod Olson wrote:

> >>>>> "RG" == Rebecca S Guenther <[log in to unmask]> writes:
>
> RG> There are various ways to approach this. One problem is that in terms
> RG> of a MARC to MODS conversion where the data being converted has used
> RG> the transcription rules of AACR2, it is unfortunately not that
> RG> predictable the way the data will appear. So the simple case is
> RG> "c1999", but there are all kinds of variations in what would be in the
> RG> 260$c. If you look at the format examples there are things like "1979
> RG> printing, c1975", "April 15 1977". You could also have "ca. 1820". So
> RG> it may not be a good idea to fool with the data and try to take out the
> RG> "c", since the program would have to look at the data and will only
> RG> catch some of them.
>
> [sample options deleted]
>
> One would not blindly remove any "c" in an AACR2 date, but rather write a
> parser to cover a variety of cases. This is something of a nightmare,
> given that the date in AACR2 is little better than free text, but the
> majority of cases can be identified and handled. Currently, those of us
> who need to do date comparisons on exported MARC data have to write these
> parsers anyhow. Here are a few examples of dates I had to parse for a
> recent project:
>
> 1857
> 183-
> c1856
> ca. 1852
> [between 1842 and 1844]
> [not before 1852]
> 1842?
>
> >From this perspective, it would be nice if MODS were more predictable in
> its date formats. As Mr. Tennant points out, additional information, if
> deemed necessary, could be provided by attributes. The conventions here
> have not been well-considered and are for purposes of illustration only:
>
> <dateIssued encoding="iso8601">1857</dateIssued>
> <dateIssued encoding="iso8601" inferred="within decade">1830</dateIssued>
> <dateIssued encoding="iso8601" type="copyright">1856</dateIssued>
> <dateIssued encoding="iso8601" inferred="circa">1852</dateIssued>
> <dateIssued encoding="iso8601" inferred="between">1842/1844</dateIssued>
> <dateIssued encoding="iso8601" inferred="not before">1852</dateIssued>
> <dateIssued encoding="iso8601" inferred="probable">1842</dateIssued>
>
> In case of multiple dates in the 260$c, they will be separated by a comma
> and can be reliably separated into multiple <dateIssued> elements. The
> above example of "1979 printing, c1975" becomes something like:
>
> <dateIssued type="printing">1979</dateIssued>
> <dateIssued type="copyright">1975</dateIssued>
>
> Correct AACR2 terms and punctuation could then be supplied for display by
> an XSLT stylesheet, if desired. This goes further than the guidelines
> currently do in moving responsibility for ISBD punctuation into the
> stylesheets, but the payoff is functional date parsing.
>
> If absolutely necessary, extremely nasty, unparsable date info could
> be marked so that programs can treat it literally for display, and avoid it
> like the plague for date matching:
>
> <dateIssued type="unstructured">1953 [1935]</dateIssued>
>
> (Though here there could, if needed, be some other way to record a
> misprinted date.)
>
> The point is that a well-defined date format is an asset of MODS,
> especially when we consider that applications will need to do date
> processing on MODS data. Conformance to such date formats should be
> explicitly encouraged if not required. Any need to support AACR2 date
> formatting and a MARC to MODS crosswalk should be secondary to support for
> this more basic need.
>
>
> Tod A. Olson <[log in to unmask]> "How do you know I'm mad?" said Alice.
> Sr. Programmer / Analyst "If you weren't mad, you wouldn't have
> The University of Chicago Library come here," said the Cat.
>

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