This is actually technical metadata and the better approach (if you were
using METS) is to put it in a METS techMD section and linked to the
appropriate part of your structmap, but I don't suppose you're doing METS
at the moment. In fact, MIX, the XML schema for the NISO standard for
technical metadata for digital still images, indeed has exactly this
element: <cameraCaptureSettings>.
But assuming you are only creating a descriptive record in MODS, there are
a few options. One is using a note in physical description:
<physicalDescription><note>Camera settings: 100 f 4.5 TL
</note></physicalDescription>
The note does have a displayLabel if you prefer the following:
<physicalDescription><note displayLabel="Camera settings">100 f 4.5 TL
</note></physicalDescription>
although one usually would expect the note to be free text anyhow.
Another alternative might be to use the <extension> element, where you can
use elements from another schema. Using that you could point to the
namespace for MIX and then use the MIX element. Here is what it would
like like:
<extension><CameraCaptureSettings xmls:
"http://www.loc.gov/standards/mix/mix.xsd">
then you would parse the data into its appropriate subelements as detailed
in MIX. (see: http://www.loc.gov/standards/mix/mix.xsd or the example at:
http://www.loc.gov/standards/mix/instances/mix_test.xml)
Another alternative if you are just using this locally is to use the
<extension> element with your own local element, e.g.
<extension><cameraSettings>100 f 4.5 TL</cameraSettings>
The intent of extension is to either use a local element or bring in one
from another namespace. If the latter, including the namespace allows it
to validate against that other schema. If you just use a local element, it
doesn't validate the data under it.
If you need further help with using the MIX element, let me know and we
can help.
Rebecca
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^^ Rebecca S. Guenther ^^
^^ Senior Networking and Standards Specialist ^^
^^ Network Development and MARC Standards Office ^^
^^ 1st and Independence Ave. SE ^^
^^ Library of Congress ^^
^^ Washington, DC 20540-4402 ^^
^^ (202) 707-5092 (voice) (202) 707-0115 (FAX) ^^
^^ [log in to unmask] ^^
^^ ^^
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
On Mon, 1 Nov 2004, Riley, Jenn wrote:
> Hello all-
>
> I have a slide collection that I'm in the final stages of mapping to
> MODS from a native metadata format (i.e., *not* from MARC). We have the
> great luck of being provided with very specific camera settings used
> when taking many of the slides in the collection, e.g., "100 f 4.5 TL"
> (TL = telephoto lens). I'm thinking this bit of information might be
> useful to include in the MODS records for each of the slides, but I'm
> not quite sure where to put it. It would be convenient to put it in an
> element with a "displayLabel" attribute so I can say
> 'displayLabel="Camera Settings"' - but which element? It could possibly
> go in <note>, or maybe <physicalDescription><note> (although I'm not
> sure that quite fits). <abstract> doesn't seem to quite fit either. I
> don't have enough experience with visual resources cataloging in MARC to
> know where the best place for this bit of info would be in a MARC
> record, so looking at MARC->MODS mappings hasn't helped me make a
> decision.
>
> I could just leave it out, but I think there are people who would be
> interested, so if there's a reasonable place to put it, I'd like to.
> Does anyone have any comments on any of the above options, or
> alternative options? I'd appreciate any advice you have.
>
> Thanks!
>
> Jenn
>
> ========================
> Jenn Riley
> Metadata Librarian
> Digital Library Program
> Indiana University - Bloomington
> Main Library E170
> (812) 856-5759
> www.dlib.indiana.edu
>
|