Hi Deena,

 

We simply use our Xpaths to distinguish which date to display. We put our machine readable dates (e.g. 2019-08-20) in dateCreated or dateIssued with an encoding attribute of edtf. The display dates (e.g. August 20, 2019) are put in the same elements, but they don’t have any attributes. This means for each date we have two date elements (one with encoding, one without). I think you can do whatever works best for you as long as you are consistent.

 

Meredith

 

Meredith Hale
Metadata Librarian
The University of Tennessee Libraries
653 John C. Hodges Library
1015 Volunteer Blvd.
Knoxville, TN 37996-1000

865-974-0029

[log in to unmask]" alt="signature_552826444">

Information is Our Game.

 

From: Metadata Object Description Schema List <[log in to unmask]> on behalf of Deena Schwimmer <[log in to unmask]>
Reply-To: Metadata Object Description Schema List <[log in to unmask]>
Date: Tuesday, August 20, 2019 at 12:41 PM
To: "[log in to unmask]" <[log in to unmask]>
Subject: [MODS] <dateOther> as display date?

 

Hello, I’m new to MODS and looking for some guidance.

Our collections have a lot of dates with ranges and qualifiers, which our current platform doesn’t display fully or in a user-friendly way.

It has been suggested to me to put a user-friendly formatted date in the <dateOther> element that would be used for display.  I see there’s a <displayForm> for name (which we’re also planning on using this way), but I don’t see this as analogous from reading the element description.  I’m wondering if you’ve ever done this, and what your reactions are to the proposal. 

Thank you.

Deena

 

________________

Deena M. Schwimmer, Archivist

Yeshiva University Archives

mail:  500 W. 185th St. / New York, NY 10033 / interoffice: MGL – 304

email: [log in to unmask] / phone: (646) 592-4058 / fax: (212) 960-0066