Page Comparison

...

1. PRE1: User is authenticated and authorized to use system.
2. PRE2: User has chosen SoR to work with.
3. PRE3: User has chosen Person to update (most likely via Search Person Use Case)
4. PRE4: User has permissions to update person.
5. PRE5: Pre-defined list of Address, Email, Phone, Url TypesPRE6: Pre-defined list of prefixes, name types.
6. PRE7PRE6: Defined Standardization and Normalization Algorithms

...

1. User modifies and submits changes to the person. The following changes are allowed:
   • Modification to an existing name (i.e. changing name type)
   • Addition of a new name
   • Deletion of an existing name
   • Changes to birth date, gender, source identifiers (generated identifiers cannot be changed by an SoR)
2. If an existing name, birth date, gender, or source identifier is modified, reconciliation MUST be re-executed similar to the rules in the Add Person Use Case.
3. If the legal or formal name changes, reconciliation MUST be re-executed similar to the rules in the Add Person Use Case.
4. If reconciliation results in a change of association then the update will fail.
5. Standardization and Normalization occur per PRE7PRE6.
6. Calculated Person Re-calculated [is this a post condition] (election algorithms, etc.)
7. Attribute Re-calculation

...