Hi all, I just want to make a longer note to the discussion. We have jumped into trouble with journal, issue, volume, pagination and things like these in our DML-CZ (http://dml.cz/) project. For qualified DC, we have followed the basic terms (contributor, description, ...) and set up several new qualifiers (because it's not possible to live only with the ones defined) - I have always tried to let the basic terms to have their general meanings, so "description" is used a lot:
description.volume description.issue etc. etc. However, the trouble is not the "internal" qualified DC. The real troubles have started with the EuDML (http://www.eudml.eu/) when we have needed to share our metadata via OAI-PMH and especially via nonqualified DC. Then "descrition.volume = 10" is just "description = 10" (or <dc:description>10</dc:description> to be precise). The "dirty" solution we have choosen (according to or better inspired by http://projecteuclid.org/documents/metadata/dml_dc/) uses qualifiers as prefixes: <dc:description>volume:10</dc:description> <dc:identifier>isbn:0268034869</dc:identifier> Together with defined rules (what prefix means what) it is useful I think. And it is correct DC. You can check out our OAI (oai.dml.cz) for inspiration. Vlastik ---------------------------------------------------------------------------- Vlastimil Krejčíř Library and Information Centre, Institute of Computer Science Masaryk University in Brno, Czech Republic Email: krejcir (at) ics (dot) muni (dot) cz Phone: +420 549 49 3872 ICQ: 163963217 Jabber: [email protected] ---------------------------------------------------------------------------- On Fri, 17 Sep 2010, Platt, Alice wrote: > The librarian's point of view: > > I agree with Mark that it's not a great idea to make up non-standard terms. > > The issue here lies not with DSpace, but with the Dublin Core schema. The > reason Dublin Core is silent about pagination is because of a principle > behind the schema, which states "In general Dublin Core metadata describes > one manifestation or version of a resource, rather than assuming that > manifestations stand in for one another" (Diane Hillmann, Using Dublin Core, > http://dublincore.org/documents/usageguide/). Since Dublin Core was strictly > designed to describe digital resources, and digital resources inherently do > not have pages, Dublin Core ignores the concept of pagination. It's a concept > left over from print media. > > With all that said, I do understand the frustration. But ultimately, it's > best to follow guidelines and best practices, to ensure interoperability and > the longevity of your metadata. If pagination is a priority, it may indeed be > best to use MODS, which is more closely related to describing print media and > includes more of the traditional types of cataloging fields. > > Alice Platt > Digital Initiatives Librarian > Shapiro Library > Southern New Hampshire University > 2500 North River Rd > Manchester, NH 03106 > USA > 603-668-2211 x 2156 > > Visit the SNHU Academic Archive at http://academicarchive.snhu.edu > > > Date: Fri, 17 Sep 2010 10:23:27 -0400 > > From: "Mark H. Wood" <[email protected]> > > Subject: Re: [Dspace-general] Metadata, enumeration & pagination > > To: [email protected] > > Message-ID: <[email protected]> > > Content-Type: text/plain; charset="us-ascii" > > > > IMHO people shouldn't be making up nonstandard terms in the "dc" namespace. > > > > We need help from librarians here: isn't there *some* metadata standard for > representing articles in dead-tree periodicals? If not, then let's stir > people up, get one made and promote it. > > > > -- > > Mark H. Wood, Lead System Programmer [email protected]<mailto:[email protected]> > > Balance your desire for bells and whistles with the reality that only a > little more than 2 percent of world population has broadband. > > -- Ledford and Tyler, _Google Analytics 2.0_ > > > > > > Date: Fri, 17 Sep 2010 18:13:27 +0800 > > From: "David Palmer" <[email protected]> > > Subject: [Dspace-general] Metadata, enumeration & pagination > > To: <[email protected]> > > Cc: [email protected], 'Repositories discussion list' > > <[email protected]> > > Message-ID: <046601cb5650$f8896f40$e99c4d...@hk> > > Content-Type: text/plain; charset="us-ascii" > > > > Japan's National Institute of Informatics (NII) has made guidelines for > metadata usage in IRs; "junii2 Guidelines", > > http://www.nii.ac.jp/irp/archive/system/pdf/junii2guide_ver1.0.pdf > > > > They give these tags, > > - dc.identifier.volume > > - dc.identifier.issue > > - dc.identifier.spage > > - dc.identifier.epage > > > > I can see several IRs in Japan using these codes. An example, > > > > http://ir.lib.shizuoka.ac.jp/handle/10297/2183?mode=full&submit_simple=Show+ > > full+item+record > > > > I assume they use (created?) these because Dublin Core is silent on the > issue. We have the same problem in Hong Kong. What to do for tags to show > enumeration & pagination? Now it is hopelessly all jumbled into > dc.identifier.citation. > > > > Do IRs outside Japan use these same tags? If not, what tags are used to show > enumeration & pagination? Is this issue being addressed in DSpace 1.6 or > 1.7? Will all of us solve this problem by ourselves individually and thus > create tags, variously weird & wonderful? Let a thousand flowers bloom? > > > > David Palmer > > Scholarly Communications Team Leader > > The University of Hong Kong Libraries > > Pokfulam Road > > Hong Kong > > tel. +852 2859 7004 > > http://hub.hku.hk > > > Please consider the environment before printing this e-mail. > ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ Dspace-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-general
