Title: Message Title
|
|
|
|
If the DOI is being copied to metadata (dc.identifier.uri), then it is already being automatically stored in the AIPs as dc.identifier.uri. Trying to store additional information from the DOI table in the AIPs seems duplicative (and hopefully unnecessary).
It seems like the DOI table is really nearly the same idea as the Handle table. For Handles, they are stored in AIPs as dc.identifier.uri and they are automatically restored (rewritten to the handle table) by the InstallItem.restoreItem() method:
https://github.com/DSpace/DSpace/blob/master/dspace-api/src/main/java/org/dspace/content/InstallItem.java#L97
Essentially this takes the passed in Handle (in this case) and re-registers it in the Handle table. So, it might be best to do something similar with DOIs. I'm not very familiar yet with all the DOI code though, so I don't know if this can be done in the same manner or not. Ideally though, I don't think we should be writing the DOI table content into the AIPs. As I said, it's duplicative information and that DOI table is only there to map DOIs to objects, which should be something we can regenerate on restoration.
|
|
|
|
|
|
|
|
|
|
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
