Batch Metadata Import needs to validate metadata fields specified in CSVs
-------------------------------------------------------------------------
Key: DS-632
URL: http://jira.dspace.org/jira/browse/DS-632
Project: DSpace 1.x
Issue Type: Bug
Components: DSpace API
Affects Versions: 1.6.2, 1.6.1, 1.6.0, 1.5.2, 1.5.1, 1.5.0
Environment: All
Reporter: Kim Shepherd
Assignee: Stuart Lewis
Fix For: 1.7
Batch metadata importer does not properly validate metadata fields specified in
the uploaded CSV.
If a user uploads a CSV with a non-existent metadata field name, changes will
be displayed as though the CSV were valid, then when the user confirms, they
will be told "No changes detected, 0 processed".
However, the items get ingested as completely empty items containing no
metadata, without being deleted from the uploader's workspace.
As a result, the administrator/uploader can not delete the item from the
collection (as there is an fkey reference to workspace_items) and can not
remove the item from the workspace, as there is a reference to collection2item.
Manual SQL queries must be run to completely remove the object.
Proposed solution: Quick validation against metadata registries before
displaying confirmation of changes, and display an error if a field does not
exist or is invalid in some other way (formatting, rights, etc.)
--
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
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
