[
https://jira.duraspace.org/browse/DS-1333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26548#comment-26548
]
Tim Donohue commented on DS-1333:
---------------------------------
Followup after looking at other items.
* 'dc.creator' : I notice that versioning other items does keep author
metadata as long as it is stored in 'dc.contributor.author'. It's just the
'dc.creator' field that has issues.
* 'dc.type' : The 'dc.type' value of the item above is "text" which doesn't
appear in the default Type field dropdown. However, I still think these
previous values should somehow be kept in tact. It seems improper to remove
existing values by default.
* 'dc.subject' : Similarly, the dc.subject values do not appear in the subject
dropdown. However, I still think these previous values should somehow be kept.
It seems improper to remove existing values by default.
* 'dc.identifer' : I'm not sure why the existing dc.identifier values are not
kept at all.
> Versioning an Item causes some metadata values to be lost
> ---------------------------------------------------------
>
> Key: DS-1333
> URL: https://jira.duraspace.org/browse/DS-1333
> Project: DSpace
> Issue Type: Bug
> Components: XMLUI
> Affects Versions: 3.0
> Reporter: Tim Donohue
> Priority: Critical
> Fix For: 3.0
>
>
> As the demo administrator on demo.dspace.org, I've attempted to create a new
> version of this item:
> http://demo.dspace.org/xmlui/handle/10673/5
> However, after creating the new version & going back into the submission
> process (for that new version), the following metadata fields are lost:
> * dc.creator
> * dc.identifier.*
> * dc.type
> * dc.subject
> Each of these metadata fields has values assigned in version #1 of the Item.
> However, in the new version in the submission workflow, non of these existing
> values are pre-populated.
> You can see this in action by logging in as the Admin user and visiting this
> new version of the item in the submission process.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
