------- Forwarded Message
From: [log in to unmask]
To: [log in to unmask] (Non Receipt Notification Requested)
Subject: Re: Updated DC Qualifiers document
Date: Wed, 8 Jan 1997 09:04:39 +0000
-----Multi-Part-Message-Level-1-1-5185
Content-type: text/plain; charset="us-ascii"
> http://www.roads.lut.ac.uk/Metadata/DC-Qualifiers.html
-----Multi-Part-Message-Level-1-1-5185
Content-type: text/plain; charset="us-ascii"
Jim,
A brief (well it started briefly) comment on a detail of the new DC-Qualifiers
list - CREATOR element, USMARC Scheme:
>USMARC
>The information provided is a field from a USMARC record. It should >start wit
h the field number, followed by the field itself and then
>any sub-fields.
This wasn't clear to me since a USMARC field (e.g. 110 Corporate Name) is typic
ally represented as a three digit field number, followed by two "Indicators", a
nd a series of subfields, each preceded a subfield marker of the form $x.
I guess "the field itself" refers to the $a subfield, which contains the main d
ata element.
Will the USMARC indicators be included ?
Would other subfields be flagged as such or simply concatenated ?
e.g. EFILA Meeting 1996 in Brussels as CREATOR of a document:
1) 110EFILA, Brussels, 1996
or (with USMARC Indicators):
2) 1102 EFILA, Brussels, 1996
or (USMARC compliant with indicators and subfield tags)
3) 1102 $aEFILA$cBrussels$d1996
Librarians and others using USMARC (Z39.50/GILS) would find format 3) more usef
ul, and there is a lot to be said for having some minimal compatibility between
the data formats used by the DC elements and those used by USMARC/Z39.50/GILS/
ZSTARTS applications.
One could argue that full USMARC compliance would add extra complexity and that
the presence of the USMARC tag in format 1) already provides useful informatio
n about the type of CREATOR involved.
However a USMARC-compliant CREATOR meta-data element could be input via an entr
y form (with simple and expert modes) without requiring the user to know about
Indicators and the various additional subfields.
Software for user-friendly search/presentation of USMARC data already exists in
the form of Z39.50 clients (field tag, indicator and subfield tag info is used
to generate readable explanatory prefixes).
Any comments ?
PS Keep up the good work, we are following the DC developments with great inter
est
[log in to unmask] (Library/Internet Applications, European Commission)
-----Multi-Part-Message-Level-1-1-5185--
------- End of Forwarded Message
|