Issue Type: Bug Bug
Affects Versions: 3.1
Assignee: Unassigned
Components: DSpace API
Created: 26/Aug/13 8:53 PM
Description: Sometimes DSpace looks up a schema by the long namespace, and not the short name while serializing metadata for an Item. This causes metadata registered in DSpace through the UI metadata registry and present within an atom+xml document submitted via the Sword2 protocol, unable to be added. This patch fixes this issue. It also throws a RuntimeException (I didn't want to change the signature, so there could be a much better way to express this) when the schema is not available via either method. This alleviates the mystery of why DSpace cant' find a defined symbol when parsing the metadata for an Item, as an Item with a bad reference to internal metadata should be recorded as an error. Sword2 protocol users will then know that something is wrong with the metadata in their document and be able to debug.

I submitted the following pull request three months ago (as of this posting) that resolves the issue. Please review and let me know your thoughts, we'd love to see this closed. https://github.com/DSpace/DSpace/pull/230
Environment: Reproduces on OSX with JDK 1.6/1.7 and Ubuntu under JDK 1.6.
Project: DSpace
Priority: Blocker Blocker
Reporter: Andrew Waterman
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
------------------------------------------------------------------------------
Introducing Performance Central, a new site from SourceForge and 
AppDynamics. Performance Central is your source for news, insights, 
analysis and resources for efficient Application Performance Management. 
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel

Reply via email to