Types of images
The Person Registry supports the following image types:
| Email type | Occ | Source | Description | ||
|---|---|---|---|---|---|
| min:max | reg | ext | user | ||
| Card | 0:1 | no | yes | yes | University ID card image |
|
|||||
Card
| Registry Database: | table=person_extension, type_cd=cardimage |
| XML Document: | <image type="card"> |
| LDAP Directory: | N/A |
The image that appears on a person's University ID card
Parts of an image
Each image in the registry is stored as a single row in the person_extension table of the Registry database. An image consists of these parts:
| What | Required? | Schema | xml |
|---|---|---|---|
| Type of image | yes | type_cd | <image type="..."> attribute |
| MIME type | no | N/A | <image mimetype="image/jpeg"> attribute |
| Data Encoding | no | N/A | <image encode="base64"> attribute |
| Image data | no | text_value | <image>#PCDATA |
Data integration rules
Image from a source to the registry
Image is a sole-sourced data type where only certain forms can be contributed by external systems per individual source agreement.
Image in the registry outbound Person XML document
All image types are access controlled in the Registry and are only available as needed.
Events
Registry/Directory synchronization events
The Person Registry posts an registry_person:reconcile for any change in image data.
No person events are currently posted for image changes since that data is not in the directory.
