Page Comparison

...

1. Add new person:

   Code Block
   HTTP POST /sor/{sorSourceId}/people

   • HTTP request headers:
     • Content-Type: application/xml
   • HTTP request entity body:
     • <open-registry-person> XML representation
   • HTTP response entity body:
     • www-form-urlencoded representation of activation key (in case of 201). Example: activationKey=rsoktfqw
     • <open-registry-resources> XML representation (in case of 409)
   • HTTP status codes:
     • 201: the new person resource is successfully created
     • 400: the person XML representation is malformed or incomplete e.g. required fields are missing
     • 303: the exact person already exists in the system e.g. the system has found an exact match based on the incoming person representation
     • 409: possible one or more people exist in the system e.g. the system has found possible matches based on the incoming person representation
     • 415: the request entity body is missing
     • 401/403: the authentication/authorization fails
     • 500: any other server error that occurs
   • HTTP response headers:
     • Location: /people/{personIdType}/{personId} (URI of a newly created calculated person resource in case of 201)
     • Location: /people/{personIdType}/{personId} (URI of an existing calculated person resource in case of 303)
     • Content-Type: application/x-www-form-urlencoded (in case of 201)
2. 'Force Add' new person:

   Code Block
   HTTP POST /sor/{sorSourceId}/people?force=y

   • HTTP request headers:
     • Content-Type: application/xml
   • HTTP request entity body:
     • <open-registry-person> XML representation
   • HTTP response entity body:
     • www-form-urlencoded representation of activation key (in case of 201). Example: activationKey=rsoktfqw
   • HTTP status codes:
     • 201: the new person resource is successfully created
     • 400: the person XML representation is malformed or incomplete e.g. required fields are missing
     • 415: the request entity body is missing or is not of an appropriate media type
     • 401/403: the authentication/authorization fails
     • 500: any other server error that occurs
   • HTTP response headers:
     • Location: /people/{personIdType}/{personId} (URI of a newly created person resource in case of 201)
     • Content-Type: application/x-www-form-urlencoded (in case of 201)

Update/Edit SoR Person

HTTP PUT/sor/{sorSourceId}/people/{sorPersonId}

• HTTP request headers:
  • Content-Type: application/xml
• HTTP request entity body:
  • <open-registry-modify-person> XML representation
• HTTP response entity body:
  • empty (in case of 204)
• HTTP status codes:
  • 204: the system of record person resource has been successfully modified
  • 400: if one of the required arguments is missing
  • 404: the system of record person resource is not found
  • 401/403: the authentication/authorization fails
  • 409: update/edit request changes key data about the person such that they no longer reconcile to the same person.
  • 500: any other server error that occurs

Representations

Request for: Add Person

...

<?xml version="1.0" encoding="UTF-8"?>
<open-registry-resources>
    <link href="http://localhost:8080/openregistry/api/v1/people/RCPID/82" rel="person"/>
    <link href="http://localhost:8080/openregistry/api/v1/people/RCPID/83" rel="person"/>
</open-registry-resources>

Request for: Update/Edit Person

<?xml version="1.0" encoding="UTF-8"?>
<open-registry-modify-person>
    <dob>1978-03-11</dob>
    <ssn>195534444</ssn>
    <gender>m</gender>
    <names>
          <name type="FORMAL">
                 <prefix>Mr.</prefix>
                 <first-name>Joseph</first-name>
                  <middle-name>John</middle-name>
                 <last-name>Jackson</last-name>
           </name>
     </names>
</open-registry-modify-person>