Hi Srijan,

Copying back in dspace-tech on this discussion. It's best to keep this 
on the listserv, as this discussion could also be helpful to others. 
(Plus others may have additional ideas for how you could implement this 
in DSpace)

I'd actually recommend *against* creating non-standard 'dc' (Dublin 
Core) fields (as we no longer encourage that in your local DSpace 
instance). Rather, you may want to create your own custom 
'music/recording' metadata schema (or base it on an existing metadata 
schema that is already out there).

DSpace supports metadata fields of the form:
[schema].[field].[qualifier]

What you choose as your 'schema' is up to you. But, I'd recommend 
against pushing everything into the 'dc' schema, as this really isn't 
basic Dublin Core anymore.  So, if you called your schema 'local', you 
could do something like:

local.contributor.drummer
local.contributor.pianist

Or you could even do:

local.instrumentalist.drummer
local.instrumentalist.pianist

You could also replace 'local' with 'music' or 'recording' or whatever 
you feel is the most appropriate name for this custom metadata schema.

As for MODS mapping, generally speaking, you should be able to map any 
[schema].[field].[qualifier] value into any MODS field.  To see how this 
is done, take a look at the [dspace]/config/crosswalk/mods.properties 
file.  This is the file that defines all the crosswalks to MODS. It just 
maps an internal DSpace metadata field to its appropriate output in MODS.

Hopefully that helps,

- Tim


On 6/17/2011 12:51 AM, Srijan Deshpande wrote:
> That's bad news, Tim, but thanks!
> So in that case my only alternative would be to use
> dc.contributor.singer. While this sounds ok, my problem is this: I also
> need to use dc.contributor.instrumentalist but then there would be no
> way to tell which instrument that person is playing in that recording.
>
> I suppose I'll have to use a custom qualifier like
> dc.contributor.drummer or dc.contributor.pianist.
>
> I was hoping I could go the whole hog and have either
> dc.contributor.instrumentalist.drummer or dc.contributor.instrumentalist
> - John Doe:drummer - but apparently neither is an option in DSpace!
>
> Suppose I used dc.contributor.drummer - Would there be a way to map this
> in mods to contributor.instrumentalist with a role of 'drummer' ?
>
> Thanks,
> Srijan
>
>
>
> On Friday 17 June 2011 at 1:54 AM, Tim Donohue wrote:
>
>> Hi Srijan,
>>
>> Unfortunately, at this point in time DSpace doesn't look for any special
>> punctuation in any metadata fields. So, it wouldn't be able to treat
>> "John Doe:singer" any differently than just "John Doe", or "John
>> Doe:editor".
>>
>> At this time, there is also not way to parse "John Doe:singer" to the
>> appropriate MODS file on export. The MODS export functionality just
>> maps DSpace fields to MODS fields. So, it could map a custom field
>> called "mods.contributor.singer" to a particular MODS role, but it
>> wouldn't be able to parse out special punctuation.
>>
>> Let us know if that doesn't make sense.
>>
>> - Tim
>>
>> On 6/11/2011 1:32 AM, Srijan Deshpande wrote:
>>> Hello, quick metadata question:
>>>
>>> I need to capture each dc.contributor's role in my item metadata in
>>> dspace - since DSpace doesn't support heirarchical metadata, can I use
>>> punctuation, as suggested
>>> athttp://www.loc.gov/standards/mods/dcsimple-mods.html
>>> <http://www.loc.gov/standards/mods/dcsimple-mods.html> to list each
>>> contributor's role?
>>>
>>> So my dc.contributor field would have a value like 'John Doe:singer'
>>>
>>> This way if I have to export this data in the future, I could export it
>>> to a MODS file correctly, including <role> information, right?
>>>
>>> Also, is there a way to parse this information and customize how it is
>>> displayed in search results / item pages?
>>>
>>> Thanks,
>>> Srijan Deshpande
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> EditLive Enterprise is the world's most technically advanced content
>>> authoring tool. Experience the power of Track Changes, Inline Image
>>> Editing and ensure content is compliant with Accessibility Checking.
>>> http://p.sf.net/sfu/ephox-dev2dev
>>>
>>>
>>>
>>> _______________________________________________
>>> DSpace-tech mailing list
>>> [email protected]
>>> <mailto:[email protected]>
>>> https://lists.sourceforge.net/lists/listinfo/dspace-tech
>

------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech

Reply via email to