[ 
https://jira.duraspace.org/browse/DS-433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=22105#comment-22105
 ] 

Bram Luyten (@mire) commented on DS-433:
----------------------------------------

Some initial comparing work:
https://wiki.duraspace.org/display/cmtygp/NewDublinCore

In short:
- there seems new & more focus on Domain (limitations on the type of resources 
a field can be used for) and Range (which values are allowed as contents of a 
field)
- For the older set of 15 DC elements, it just seems a matter of 
implementing/enforcing range on some of the properties (e.g. ensuring correct 
dc.date values, language values, ...)
- Lots of the newer DC Terms are already present in DSpace. Like many of DSpace 
qualified dates, like dc.date.issued dc.date.available, are now defined as 
individual elements. This is a great opportunity to ensure that no information 
gets lost while element qualifiers do get lost when harvesting.
- DCMI still seems to struggle with the idea of relations between fields. Some 
fields are indicated that they should be used with non-literal values (e.g. 
things instead of strings) but they haven't come up with a formal range 
declaration.
                
> Update DublinCore Registry to Implement lates DC Standards
> ----------------------------------------------------------
>
>                 Key: DS-433
>                 URL: https://jira.duraspace.org/browse/DS-433
>             Project: DSpace
>          Issue Type: Improvement
>          Components: DSpace API
>            Reporter: Jeffrey Trimble
>            Priority: Major
>   Original Estimate: 17 weeks, 2 days, 8 hours
>  Remaining Estimate: 17 weeks, 2 days, 8 hours
>
> DSpace's current implementation of Dublin Core was a subset or simplified 
> version of the Dublin Core standard created by OCLC.  Since the first release 
> of DSpace, Dublin Core has undergone major revisions.  DC version 1.1 was 
> implemented in 2007 with 15 base elements a subset of the larger DCMI.  Some 
> users  are currently misusing the DC standards, or lack knowledge how to use 
> it properly due to the age of the current element set and the descriptions 
> contained therein.
> I recommend that the DSpace Developers look at using the full implementation 
> of DCMI for the next major release after 1.6.  Additionally tools will need 
> to be provided
> for conversion of existing DC Metadata Schema.  
> Also, it would be advantageous to build into the software a validation of DC 
> elements in a stricter sense than is now being used.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.duraspace.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

------------------------------------------------------------------------------
EMC VNX: the world's simplest storage, starting under $10K
The only unified storage solution that offers unified management 
Up to 160% more powerful than alternatives and 25% more efficient. 
Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
  • [Dspace-devel] [DuraSpace... Bram Luyten (@mire) (Commented) (DuraSpace JIRA)

Reply via email to