Well, the gap I was not understanding was exactly what Claudia Jürgen said: my problem had to do with Metadata Registry.
When I've found the folder "[dspace-app]/config/registries" and the "dublin-core-types.xml" file I've been able to add the new metadata I was needing, with new qualifiers. Now I have as much elements as I want. Thank you Claudia and Alice. Yuri Cardenas On Thu, Jul 2, 2009 at 10:08 AM, Platt, Alice <[email protected]> wrote: > Hi Yuri, > > One or both of your elements should also have a qualifier in order to make > a distinction between the two. So, for example, the second element that you > want to use for subject could have the qualifier "keyword" so that the > metadata element becomes "subject.keyword". Then DSpace will understand that > the "subject" and the "subject.keyword" are two distinct elements. > > Alice Platt > Digital Initiatives Librarian > Shapiro Library > Southern New Hampshire University > 2500 North River Rd > Manchester, NH 03106 > USA > > Date: Wed, 1 Jul 2009 16:01:53 -0300 > From: Yuri <[email protected]> > Subject: Re: [Dspace-general] Repeatable dc-elements? > To: Claudia J?rgen <[email protected]> > Cc: [email protected] > Message-ID: > <[email protected]> > Content-Type: text/plain; charset="iso-8859-1" > > Hi, Claudia. Thank you for answering. > I got that. But there's some gap I can't understand. I'll give you an > example to (try to) explain why it doesn't make sense: > > Below, two fields from one of my forms: > > <field> > <dc-schema>dc</dc-schema> > <dc-element>subject</dc-element> > <dc-qualifier/> > <repeatable>true</repeatable> > <label>Subject</label> > <input-type>onebox</input-type> > <hint/> > <required/> > </field> > > <field> > <dc-schema>dc</dc-schema> > <dc-element>subject</dc-element> > <dc-qualifier/> > <repeatable>false</repeatable> > <label>Keywords</label> > <input-type>onebox</input-type> > <hint/> > <required/> > </field> > > The first is the subject of the item itself. The other one is for the > keywords' field. I can't merge them into a single repeatable field, once > they have different meanings. > > So, how am I supposed to solve this, considering I can't have duplicated > elements? Dublin Core and Dspace wouldn't limit the number of metadata, of > fields, would them? > > Well, maybe I could insert a qualifier for each element. But the official > DC's qualifiers list* doesn't include as many qualifiers as I need. Can I > write (create) any qualifier I want? Or is there any other solution I'm not > figuring out? > > > Yuri Gomes Cardenas > > * http://dublincore.org/documents/usageguide/qualifiers.shtml > > > 2009/7/1 Claudia J?rgen <[email protected]> > > > Hi Yuri, > > > > this is true with regards to the metadata registry. There an element got > to > > be unique within a schema. As for the input forms, you can mark a field > as > > repeatable to have the possibility to enter multiple values for a field, > > e.g.: > > <field> > > <dc-schema>dc</dc-schema> > > <dc-element>contributor</dc-element> > > <dc-qualifier>author</dc-qualifier> > > <repeatable>true</repeatable> > > <label>Authors</label> > > <input-type>name</input-type> > > <hint>Enter the names of the authors of this item below.</hint> > > <required></required> > > </field> > > > > Setting > > <repeatable>true</repeatable> > > allows for multiple authors to be entered. > > > > Hope this helps > > > > Claudia J?rgen > > > > > > Yuri schrieb: > > > >> Hi, everyone. > >> > >> I've discovered that DSpace does not accept duplicated dc-elements for > the > >> same dc-schema. And discovered also that this verification is done in > >> DCInputsReader, method checkForDups( ). But I don't understand the > reason > >> for it, once there are no problems about repeating elements in Dublin > >> Core. > >> > >> And It doesn't seem a good idea to skip this verification in DSpace's > code > >> as well. > >> > >> Am I wrong, duplicated element are an important thing to check? And if > so, > >> does anyone know why? > >> > >> Thanks in advance. > >> > >> *Yuri Gomes Cardenas* > *** > > Please consider the environment before printing this e-mail. >
_______________________________________________ Dspace-general mailing list [email protected] http://mailman.mit.edu/mailman/listinfo/dspace-general
