Hi Malcolm,

Hm, if the date of deposit denotes the creation of the archival copy,
<dateCreated> might work, but only because this is a digital archive so
acquiring a resource is the same as creating a copy.  In general, what
you're talking about sounds like holdings metadata, for which there are
other XML schemata.  In MODS, you'd put the elements from that schema in
<extension>; if you change <originInfo>, you aren't using MODS anymore!
If interoperability is not a concern, though, just write your own XML
schema that imports the standard MODS schema and then redefines the
content model of <originInfo>.


>>> [log in to unmask] 2004-05-11 07:56:33 >>>

Could somebody advise me please? The AHDS is a digital archive and we
like to record the 'date of deposit' in addition to the standard
date-related subelements of MODS (date issued, created, captured,
valid, and
modified). Could this be done by qualifying <originInfo> by the use of
local subelement such as <ahds:dateDeposited>?

e.g. <mods:originInfo>

or would I have to use <extension>?

e.g. <mods:extension><ahds:dateDeposited>

 - the latter would seem rather clunky in that 'date of deposit' is
date-related and therefore concerns the same basic concept as the
date-related subelements of <originInfo>.

There are quite a few MODS elements that we would like to refine
locally but
but the user guidelines seem to me to only offer a mechanism for
completely new elements. Are local subelements permissible and is there
recommended approach? Similarly, can one introduce local attributes?

Any help would be appreciated. We're at the stage of considering
whether to
use MODS.

Thanks in advance,

Malcolm Polfreman

Malcolm Polfreman
Information Officer
Arts & Humanities Data Service (AHDS)
King's College London
26 - 29 Drury Lane
3rd Floor
Tel: 0207 848 1985
Fax: 0207 848 1989
Email: [log in to unmask]