Date:         Wed, 14 Nov 2007 09:40:33 -0500
Reply-To:     Metadata Object Description Schema List <[log in to unmask]>
Sender:       Metadata Object Description Schema List <[log in to unmask]>
From:         "Rebecca S. Guenther" <[log in to unmask]>
Subject:      Re: need for projected publication date in MODS
Comments: To: Metadata Object Description Schema List <[log in to unmask]>
In-Reply-To:  <[log in to unmask]>
Content-Type: TEXT/PLAIN; charset=US-ASCII

There are so many dates that are of importance for particular communities
that we provided dateOther for those cases where MODS didn't supply a
specific one (as you noted). We tried to limit defined date types to the
most used sorts of dates. Of course you can use the type attribute with
dateOther and we could consider providing a list of types used, as we do
with note types (http://www.loc.gov/standards/mods/mods-notes.html), if
this would be useful. Maybe other MODS users can speak to your question
about defining a specific date type for this one.

Rebecca

On Tue, 13 Nov 2007, Joe Altimus wrote:

> I wonder if others see a need for a MODS element to hold information that a
> resource is not yet available (similar to the MARC 263 element -- Projected
> Publication Date)?
> 
> The need I see involves citations for faculty publications that appear in
> our digital repository. Sometimes faculty want a minimal citation in the
> repository before the actual details of the publication are known. Having a
> MODS element that indicates the provisional nature of the citation seems
> useful for tracking and other administrative tasks.
> 
> The originInfo/dateOther element can be used, of course, but is there is a
> general need for an element that merits defining a new type of date
> ("dateToBeIssued" or similar)?
> 
> Joe Altimus
> Arizona State University Libraries
>