Print

Print


I think this would be useful for purposes other than traditional
bibliographic citation.  For services which are selecting and describing
websites (e.g. subject gateways), there is always the problem of whether to
describe a resource which might disappear, and how to describe a resource
which might change significantly from the time it is described.  In these
scenarios, having a <dateAccessed> - which could be updated if there is a
significant review of the resource and record - would be a helpful way of
indicating to users 'We accessed and described the resource as we found it
on this date.  It may have changed/moved since then'.

Cheers

Marie-Louise

> ----------
> From:         Rebecca S. Guenther[SMTP:[log in to unmask]]
> Reply To:     Metadata Object Description Schema List
> Sent:         Friday, 29 August 2003 7:18 AM
> To:   [log in to unmask]
> Subject:      [MODS] Date accessed
>
> It has been suggested that MODS include a date of access. The example
> given was for bibliographic citations. The Chicago Manual of Style
> includes an access date for an electronic resource (i.e. date it was last
> accessed, since Web sites change frequently) in standard bibliographic
> citations. This is different from dateModified, which is being added to
> MODS in version 3.0, in that dateModified tells you date that the resource
> was last changed, while date accessed would tell you when it was last
> viewed or accessed and makes no claims about when it was last modified. In
> addition to being able to accurately produce bibliographic citations, this
> date might be useful for any resource that is updated regularly-- Web
> sites, documents made available electronically, databases.
>
> AACR2 cataloging generally includes this information in a general note for
> Web sites. Since this is a date, a note does not seem an appropriate
> solution (a note can still be input regardless).
>
> The original suggestion was to add a type attribute to dateOther, but this
> is not how we have handled dates in MODS. If a specific type of date, a
> separate element is used. We wouldn't want to mix using a type attribute
> and a separate named element.  Are there any thoughts about adding another
> date to MODS? Under <originInfo> it would be <dateAccessed>. It then would
> use the dateType definitions.
>
> Rebecca
>