Local System Unable to Push Update to NDR
|
The local system has applied an update to its local data store.
The local system tries to push change to NDR, but fails e.g. due to network failure.
|
Nothing; the NDR is not aware of the attempted update.
|
Retry, e.g. overnight.
If the retry also fails, log a notification according to a suitable (local) mechanism – e.g. write to an error log.
Once connectivity is restored, the local system will have to re-POST the update (possibly with manual intervention by local system admin).
|
Local System Attempts to Push and Update to NDR Without Sufficient Privileges
|
The local system has write privileges to certain fields, but tries to update other fields.
|
NDR responds with “invalid” request, as per Section 5.7.2.
|
Local system should ensure such data is “read only”, so the local operator does not inadvertently edit such data.
If multiple POST transactions are available (e.g. to Dog Entity) then the local system should use the most appropriate POST – e.g use Update (owner) rather than Update on the entire Dog Entity.
|
Client Attempts an Update Based on Stale Data
|
The local system attempts to update the NDR based on stale data (i.e. without having first picked up previous changes).
|
NDR responds with “invalid” request, as per Section 5.7.2.
|
Local system should perform a GET just prior to allowing a user to modify data.
Note that this will minimise the chance of collision; however collision is still possible.
|
Update Missed by Local System
|
Local system was down when update was published.
|
Nothing; the NDR is not aware this has occurred.
|
Local system should regularly poll the NDR to ensure if picks up all changes.
Local system should perform a GET just prior to allowing a user to modify data.
Local system should maintain a log of which events have been processed.
|
