[
http://jira.dspace.org/jira/browse/DS-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10391#action_10391
]
Kim Shepherd commented on DS-125:
---------------------------------
According to the original Dublin Core RFC:
Each element is optional and repeatable. Metadata elements may
appear in any order. The ordering of multiple occurrences of the
same element (e.g., Creator) may have a significance intended by the
provider, but ordering is not guaranteed to be preserved in every
system.
So unless there's a specific reason DSpace can't / shouldn't allow repeatable
date fields, I'll make a patch that changes org.dspace.submit.step.DescribeStep
(readDate() and doProcessing()) appropriately.
RE: Christina's comment: I'm not aware of any problems with multiple
dc.contributor.* fields since 1.4.x, but if upgrading DSpace isn't an option,
someone might be able to contribute a 1.2 patch. This should be logged as a
separate JIRA issue.
> Date type can't be repeatable in the submission
> -----------------------------------------------
>
> Key: DS-125
> URL: http://jira.dspace.org/jira/browse/DS-125
> Project: DSpace 1.x
> Issue Type: Bug
> Components: JSPUI, XMLUI
> Affects Versions: 1.5.0, 1.5.1
> Reporter: Andrea Bollini
> Priority: Trivial
>
> If you define a date metadata as repeatable it doesn't work properly in the
> submission both for JSPUI and XMLUI.
> In the JSPUI the value are not saved, in the XMLUI only a value are allowed,
> the add button replace the previous value.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.dspace.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
