Task #365
Story #589: modify metacat native interfaces to support arbitrary identifiers and system metadata
refactor handleDeleteAction() to support GUIDs
100%
Description
Allow GUIDs to be used in handleDeleteAction() to specify objects to be deleted, and map these to LocalIDs before performing the delete operation.
History
#1 Updated by Matthew Jones over 14 years ago
Modified ResourceHandler.deleteObject() to take a globally unique id (guid) as input rather than a metacat-conformant docid. The guid is translated
into a metacat docid which is then used in the handleDelete() call. So now Metacat supports use of arbitrary identifiers for delete operations, but
only through the MetacatRest REST service interface. Still need to handle exceptions that should be generated when a guid is not found. Also modified the MetacatRestClientTest to exercise this functionality. Dealing with exceptions should occur during implementation of the MN_crud.delete() functionality rather than here (which is focused on managing arbitrary identifiers. Still need to adapt other entry points into Metacat to support GUIDs.
#2 Updated by Matthew Jones about 14 years ago
- Target version deleted (
CCI-1.0) - Parent task set to #589
- Milestone set to CCI-0.6
#3 Updated by Dave Vieglais about 14 years ago
- Start date set to 2010-10-07
- Tracker changed from Bug to Task
#4 Updated by Matthew Jones over 13 years ago
- Assignee changed from Matthew Jones to Chris Jones
#5 Updated by Chris Jones over 13 years ago
- Status changed from New to In Progress
#6 Updated by Chris Jones over 13 years ago
- Status changed from In Progress to Closed
Refactored deleteFromMetacat() to now do a GUID lookup to gain a localId prior to deletion, and revert to just a localId deletion if it fails to find a GUID.
