[Dspace-tech] Followup: Managing custom metadata
Last December I posted a message titled "Managing custom metadata / advanced search options," describing some thoughts and questions I had regarding metadata for non-DC research data collections submitted to the repository. Later I drafted a discussion document outlining options, including benefits and issues. Following some discussion within the Library we've decided to go with a general approach which will see custom metadata mapped to DC (to enable simple keyword search within dspace and OAI harvesting) and submission of native metadata as accompanying bitstreams. If others are interested in this discussion, I've posted the document at... http://escholarship.library.usyd.edu.au/dpa/meta.html <http://escholarship.library.usyd.edu.au/dpa/meta.html> The scope of the discussion reflects the types of data collections currently being offered to the repository (records from relational databases and accompanying digital objects stored on departmental or personal computers). I'd welcome any feedback, advice or ideas reflecting how others are managing these issues. bye rowan 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/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
[Dspace-tech] Managing custom metadata / advanced search options
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 DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] importing a collection of files with identical names (from different directories)
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. >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? 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? 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 DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
[Dspace-tech] importing a collection of files with identical names (from different directories)
I have a collection of document files sitting on a file server. Each document is associated with a set of data files. The data files live in subdirectories of the parent document file. Many of a document's data files have identical names and are only differentiated by their position within the directory structure. I wrote a python script which reads metadata from a spreadsheet, grabs the associated document and data files and creates simple archive directories suitable for import using itemimport. My understanding is that itemimport directories cannot contain subdirectories. (i.e. I can't replicate the fileserver's document/data tree in the dspace simple archive format). Is that correct? For any given document, I can't copy all of the data files to one directory. The file names are identical so they end up overwriting each other. There's also the problem of loss of contextual information. (For any data file, a great deal of identifying information is contained in the name of its directory. e.g. directory name "High rainfall maps", data file name "Co_surface.jpg" / directory name "Quiescent maps", data file name "Co_surface.jpg") I'm thinking that I'll need to prefix each of the data file names with their original directory names, so as to retain the contextual information. I'm fairly new to dspace so I'm wondering - are there other options? Eg. can I associate a single metadata record with easily navigable related sets of data files in a way that would make sense to a user approaching the default dspace interface? How do others deal with this sort of issue? thanks rowan 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/ - 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 DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] blank page at point of submission
I had no luck with the blank page problem - despite checking settings & several complete reinstallations (including a fresh linux installation). However when I tried installing on a Windows 2003 server the problem didn't occur. Fortunately this installation is simply to support examination of customisation features around forms, metadata schemas & the controlled vocabularies - so it isn't meant to operate in a production environment. Its very puzzling that I kept on having problems on my linux installation that didn't appear on windows. 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/ -Original Message- From: [EMAIL PROTECTED] on behalf of Rowan Brownlee Sent: Thu 14/06/2007 10:33 PM To: dspace-tech@lists.sourceforge.net Subject: [Dspace-tech] blank page at point of submission I've just installed dSpace (1.4.2) for the first time. I created a community, collection and custom submission form. Everything works fine until I upload a file. At that point I see a blank page. I don't recognise any hints in the dspace.log. (I also get a blank page at file upload if I use the default submission form) - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
[Dspace-tech] blank page at point of submission
I've just installed dSpace (1.4.2) for the first time. I created a community, collection and custom submission form. Everything works fine until I upload a file. At that point I see a blank page. I don't recognise any hints in the dspace.log. (I also get a blank page at file upload if I use the default submission form) 2007-06-14 08:42:42,736 INFO org.dspace.core.ConfigurationManager @ DSpace logging installed using log4j.properties 2007-06-14 08:42:43,313 INFO org.dspace.core.ConfigurationManager @ DSpace logging installed using log4j.properties 2007-06-14 08:42:43,571 INFO org.dspace.search.DSIndexer @ (Re)building index from scratch. 2007-06-14 08:42:43,596 INFO org.dspace.search.DSIndexer @ Done with indexing 2007-06-14 08:47:08,684 INFO org.dspace.core.ConfigurationManager @ DSpace logging installed using log4j.properties 2007-06-14 08:47:44,139 INFO org.dspace.eperson.EPerson @ anonymous::create_eperson:eperson_id=1 2007-06-14 08:47:44,328 INFO org.dspace.eperson.EPerson @ anonymous::update_eperson:eperson_id=1 2007-06-14 08:47:44,410 INFO org.dspace.eperson.Group @ anonymous::update_group:group_id=1 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/ - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
