Bibliographic metadata - What do you think? The major shortcoming with the dc.bibliographic.citation (or dcterms:bibliographicCitation) format of capturing bibliographic citation information is that it's a large string of text in which can be in many different formats, so parsing it out for reuse in Open URL resolvers, for harvesting by citation and referencing software, to create RDF, XML, and other structured data is difficult. (This is not impossible as crosswalking and creating special parsers is achievable.) Would it be better to store the parts of a dc.bibliographic.citation separately and then employ programmatic way to render these as one field? This would be easy and consistency assured. The separate parts would still be available for other functions. There is a slight issue in that DC does not have fields for all the parts of a dc.bibliographic.citation; e.g., volume, issue, pages etc however PRISM does, http://www.idealliance.org/specifications/prism/ so this is what we have implemented in our DSpace https://researchspace.auckland.ac.nz/; its a Prism like schema. However, instead of creating local schema, this issue is probably common enough to be better included into standard DSpace schema. I would suggest this to future proof your databases and to maximise flexibility and interoperability with other systems. Any comments/thoughts/suggestions welcome. Yanan
---------------------------------- Research Support Services Te Tari Kotuitui Mohiotanga General Library, The University of Auckland Kua tawhiti ke to haerenga mai kia kore e haere tonu He tino nui rawa ou mahi kia kore e mahi nui tonu ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_jan _______________________________________________ Dspace-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-general
