Title: Message Title
|
|
|
|
Good that I asked, I just had the feeling, that I don't overlook all side effects of update-sequences.sql.
I don't know AIP Backup and Restore as we don't use it here. As far as I just took a look on it, AIP backups item metadata and technical metadata. Whenever a DOI got registered it gets written into the item metadata and will be restored as dc.identifier.uri. But the information in the DOI table gets lost. This information is important to generate new DOIs and to send updated metadata to DataCite.
We have two possibilities: Either we store the information of the DOI table as technical metadata or we try to detect dois whenever we restore a dc.identifier.uri field and try to regenerate the information in the DOI table with these information. In both cases we could set the doi_id as expected to make the simple bugfix (using max(dom_id) to set doi_seq) work. Tim, can you confirm these ideas?
I don't know if and when I'll have time to look on AIP. For us it is not important as we want to use Item Level Versioning which is not supported by AIP as well. Nevertheless, I hope I'll have the time to write a bugfix until DSpace 4.1.
|
|
|
|
|
|
|
|
|
|
------------------------------------------------------------------------------
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
