Story #5141
Describe the mn.updateSystemMetadata behavior in use case document
Status:
In Progress
Priority:
Normal
Assignee:
Category:
Documentation
Target version:
Start date:
2014-09-25
Due date:
2014-09-25
% Done:
30%
Story Points:
Sprint:
Description
The behavior for the mn.updateSystemMetadata call is a bit cryptic in how it's supposed to be implemented.
The implication is that it should be asynchronous with interaction with the CN, but even metacat seems to be passing back exceptions from CN interaction. (There currently isn't another way for MNs to report errors from the CN)
History
#1 Updated by Dave Vieglais about 10 years ago
- Due date set to 2014-09-25
- Target version set to Maintenance Backlog
- Start date set to 2014-09-25
#2 Updated by Dave Vieglais almost 7 years ago
- % Done changed from 0 to 30
- Status changed from New to In Progress
#3 Updated by Dave Vieglais almost 7 years ago
- Sprint set to CCI-2.3.8
