Rowan Brownlee wrote: > That's very useful information. Thanks Scott. > > The metadata that I'm importing from a spreadsheet contains latitude & > longitutude information which I'm using to generate kml files (for > import to dspace along with the other data files). I'm not familiar > with manakin but I'm assuming that at some stage we might use it to > provide a customised user interface to the collection that would include > display of google-map-like features. > Yes, Leo does this for bidwern but uses Manakin (cocoon) to generate the kml on the fly rather than archive it. > >From what you say, it sounds like it could be useful to include path > information in the metadata. Do you have any thoughts on best options > for doing this? E.g. would I add a repeating custom metadata text field > containing an entry for each file? > You could do that, it depends what the metadata represents as to how you map it e.g. does it represent subject, discipline, etc or is it fairly arbitrary. > Also - I'm not familiar with how dspace arranges file storage. Would > the file path metadata entry be a replication of the entry as recorded > in the contents file? > The path used in the "contents" file would be stored as metadata with each bitstream. Each bitstream however is renamed by DSpace and stored in the DSpace assetstore, so the file path, once in DSpace only exists as metadata. > Bye > rowan > > >
------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
