Folks, Several years ago, it was noticed that 9 item records were sharing 2 handles each in our DSpace 1.8.2 installation.
Based on metadata information, it theory is that a pending submission was withdrawn, evaluated, then eventually resubmitted and approved. Somehow, that final submission action caused a new handle to be created and the dc.identifier.uri field was overwritten with the second CNRI handle address. In other words, a normal submission would look similar to this: http://server_address/dspace/handle/1234567/12345 http://hdl.handle.net/1234567/12345 item_id: 555123 And these 9 looked more like this: http://server_address/dspace/handle/1234567/12345 http://hdl.handle.net/1234567/12345 item_id: 555123 http://server_address/dspace/handle/1234567/12346 http://hdl.handle.net/1234567/12346 item_id: 555123 But note that when viewing the item, the handle.net address ONLY shows the second handle.net address. Since the second instance was generated fairly rapidly after the first and the item made public only with the secondary handle address, an easy solution would be to delete the first submission instance as a whole. They share the same item_id, however, so deleting one will result in deleting the other (while leaving some artifacts in various tables). Also, deleting one handle reference from the handle table doesn't cause the handle.net address to properly be decommissioned by DSpace internals. After speaking with CNRI, looking at the handle server software, and reading technical documents on how handles are managed by DSpace, it appears that there isn't much in the way of management. Ideally, I'd like to remove the first handle entry from the database and either modify the unpublished, first, handle.net address to resolve to the second generated URL for the item or simply delete that first handle.net outright manually. My understanding is that the handle server binaries are not useful when DSpace is in control of handle creation/deletion. Makes sense? Thoughts? -Jeff ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ Dspace-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-general
