Delete SoR Person Flow

Overview

This document describes some sample flows for deleting a person from the registry and a general explanation of the process.

A System of Record (SoR) may wish to delete their record of a person from the Registry. The following is an example request for SoR 123 to delete a person known to the SoR as 124:

https://test-registry.rutgers.edu/api/v1/sor/123/people/124

DELETE /api/v1/sor/123/people/124 HTTP/1.1
Host: test-registry.rutgers.edu
Content-Type: application/xml
Authorization: Basic cmF0czpSQVQxMjM0

Sample Response:

HTTP/1.x 204 No Content

All roles associated with the SoR Person that is being deleted will also be deleted.

Deleting SoR Person Records to Correct a Mistake

SoR Person records may be deleted from the Registry because they were added by mistake. In the event that the person should never have been added, the delete request would look like this:

https://test-registry.rutgers.edu/api/v1/sor/123/people/124&mistake=true

DELETE /api/v1/sor/123/people/124&mistake=true HTTP/1.1
Host: test-registry.rutgers.edu
Content-Type: application/xml
Authorization: Basic cmF0czpSQVQxMjM0

Sample Response:

HTTP/1.x 204 No Content

When it is indicated that the delete is being done to correct a mistake, all traces of the person are removed from the Registry.  When "mistake" is not indicated, some information about the person is retained.

Please see http://www.ja-sig.org/wiki/display/ORUM/SoR+Person+Resource for a detailed explanation of all possible return codes.