I have a Filemaker database of records associated with a set of image files
produced from archaeological fieldwork. I'd like to transfer copies of the
records and images to dspace. I'd like the metadata to be keyword searchable
through the default jspui dspace interface. (I'd also like to provide a
collection-specific advanced search option though I'm unfamiliar with
customisation tools like MANAKIN, so I don't know if this is feasible).
There are no technical issues involved in extracting and packaging the metadata
and images into a dspace-compatible submission format. I do however have
questions about how best to manage metadata.
I can think of several options concerning metadata management. I'd really like
to hear other ideas or issues for consideration. I'm not keen on any of the
options below. If I wasn't interested in providing a service to support
granular search as well as archiving, I could simply generate basic dspace-DC
records made up of primary keywords extracted from the source metadata, and
accompany these with XML bitstream submissions comprising the native metadata
records.
Each of the native metadata records has up to 50 descriptive and administrative
metadata elements. Off the top of my head, I could...
1) Map the native metadata to existing dspace DC elements. This would result
in a loss of metadata granularity. Many items of metadata would not make sense
without the contextual information provided by a particular tag name. All of
the keywords would be searchable, though I'd have no hope of ever being able to
supply a customised advanced search interface.
2) Create a number of customised qualifiers for existing DC tags (e.g.
description.x, description.y), along with scope notes which relate each tag to
its collection. I wouldn't need to setup any new keyword indexes and I'd
retain the granularity of the original metadata. I would however need
additional and ongoing recordkeeping and maintenance procedures.
3)Create a custom schema identical to the native metadata set. In
administrative terms this would enable me to partition maintenance of the
custom schema from the default dc schema. I imagine I'd need to setup new
keyword indexes for the custom tags, as well as modify the default indexes to
include the new tags. As in option 2, I'd need ongoing recordkeeping and
maintenance procedures.
What do you think? How are others dealing with these issues?
Rowan Brownlee
Digital Project Analyst
University of Sydney Library
NSW 2006 Australia
Phone: +61 2 9036 6450
Fax: +61 2 9351 3689
http://escholarship.usyd.edu.au/dpa/
-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
