Title: Message Title
|
|
OK, Hilton doesn't have the broken metadata anymore so he's not going to use the SQL to fix it. I'm fairly confident it will work, but it hasn't been tested on an affected instance. To use it, replace 10019 with your handle prefix. E.g. If your handle prefix is 12345.1, replace 10019 with 12345. Find the affected items: SELECT handle, text_value AS current, 'http://hdl.handle.net/'||handle as fixed FROM metadatavalue, metadatafieldregistry, handle WHERE text_value = 'http://hdl.handle.net/10019' AND metadatafieldregistry.metadata_field_id = metadatavalue.metadata_field_id AND metadatafieldregistry.element = 'identifier' AND metadatafieldregistry.qualifier = 'uri' AND handle.resource_type_id = 2 AND handle.resource_id = metadatavalue.item_id; Fix the affected items: UPDATE metadatavalue SET text_value = 'http://hdl.handle.net/14'||handle FROM metadatafieldregistry, handle WHERE text_value = 'http://hdl.handle.net/10019' AND metadatafieldregistry.metadata_field_id = metadatavalue.metadata_field_id AND metadatafieldregistry.element = 'identifier' AND metadatafieldregistry.qualifier = 'uri' AND handle.resource_type_id = 2 AND handle.resource_id = metadatavalue.item_id
|
|
|
|
|
|
|
------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel