Hi Kevin! DSpace can adapt itself to any metadata structure you wish (as long as it is flat but Authority Control loosens this constraint a bit).
For instance: http://www.windmusic.org is adapted to musicians needs. I propose you to consider the problem "backward": What kind of research your users will make? Which indexes would be needed? Which forms would help them ask for what they need? What metadata is useful to support the searches and the item displays? How this metadata could be produced from the 90 fields you have now? (What could be missing!?) And then a programmer can make you the metadata extraction and recoding from the existing files toward your DSpace repository. In a second phase, this metadata can be funnelled in DC (which is a lowest common denominator anyway) if it make sense to share it in aggregating repositories. But your cherished users will be well served in the first time. Good luck! Christophe Dupriez Le 13/10/2011 16:22, Kevin P. Foote a écrit : > Hi all, > > Apologies for the xpost .. but sort of relevant to both repository > implementations (at least for me). > > We are currently using DSpace (moving to latest version soon). I have > a general high level type metadata question and did not know where else > to post, so here goes. (perhaps someone can point me to a better list) > > We have a largish (in our terms) project that involves map data or rather > (.sid) images[1] produced from said map data. > > We currently have an in-house application that catalogs these images and > stores some crazy 90 field metadata info within it. > > My question is what is the best way (read any way) to handle getting > this content into dspace (or fedora commons) in an intelligent manor. > > My understanding is that dspace and fedora use the dc-metadata > standard to search, catalog, and provide a common way for libraries and > repository software get at content. > > > Would this additional metadata get in the way with operation? > > Would it be best to create dc records for each item and then augment the > dc info with this complete additional metadata set in a new type of metadata > (not in the dc)? > > Is there a common standard for map type metadata? (USGS?) > > > Any help pointers appreciated.. > > > [1] images are 'Multi-resolution Seamless Image Database' files from > what I gather. Related to ArcGIS, ERDAS software.. > > ------ > thanks > kevin.foote > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2d-oct > _______________________________________________ > Dspace-general mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/dspace-general > > ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct _______________________________________________ Dspace-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-general
