Types of location
Location information in the Person Registry is a variety of coded information that relates to real or virtual locations.
The Person Registry supports the following types of locations:
| Location type | Occ | Source | Description | ||
|---|---|---|---|---|---|
| min:max | reg | ext | user | ||
| commjack | 0:1 | no | yes | no | Communication Jack number |
| idmail | 0:1 | no | yes | yes | Campus ID Mail routing code |
| residence | 0:1 | no | yes | no | Campus residence housing location |
|
|||||
Communications jack number
| Registry Database: | table=location, type_cd=commjack |
| XML Document: | <location type="commjack"> |
| LDAP Directory: | suResidenceTSO |
Communication Services communications jack number, also known as a TSO (Terminal Service Outlet). These identity physical service outlets in specific locations on campus. The commjack value for a person associates them with specific phone number served at a specific location.
ID mail code
| Registry Database: | table=location, type_cd=idmail |
| XML Document: | <location type="idmail"> |
| LDAP Directory: | suMailCode |
A coded location for campus ID Mail service delivery.
Residence location
| Registry Database: | table=location, type_cd=residence |
| XML Document: | <location type="residence"> |
| LDAP Directory: | suResidenceLocation |
A Communications Services assigned student subscription location for campus residential service.
Parts of a location
Each location in the registry is stored as a single row in the location table of the Person Registry database. A location consists of these parts:
| What | Required? | Schema | xml |
|---|---|---|---|
| Type of location | yes | type_cd | <location type="..."> attribute |
| Code | no | code | <location code="..."> attribute |
| Address | no | address | <location> #PCDATA |
| Room | no | room | <location room="..."> attribute |
| Effective date | no | effective_date | <location effective="..."> attribute |
| Label | n/a | label | Future use |
Type of location
Type of data per above.
Code
Coded value. The specific encoding depends on the type of location and is determined by the source. For instance, for residence information, it is the Housing Office-assigned code for a campus residence.
Address
The expanded, textual form of the address, usually the descriptive value associated with the code.
Room number
Optional ability to qualify building level location with a specific room number or similar information.
Effective Date
An optional date to indicate when the association with the room takes effect. Note that this is NOT a general "effective dated" capability to control applicability of data to the person such as found in the PeopleSoft applications. Here the date, e.g., a future move-in date, is part of the current information for the person.
Data integration rules
Locations from the source to the registry
The Person Registry has a domain of expected location types that it will process from external systems by agreement with those sources. The use and meaning of optional attributes like room and effective date are determined by those sources as well.
Locations in the registry outbound Person XML document
Locations in the Person registry are contained in the person level <location> element or in an <affiliation><place><location> element (for affiliated locations) in the document.
Events
Registry/Directory synchronization events
The Person Registry posts an registry_person:reconcile for any change in location data.
Infrastructure person events
The person Slog process that maintains Person data in the Directory posts the following events when directory attributes change. The parms designating the specific data type allow consumers to filter the events to select only changes needed by their system.
| Directory attribute | event (domain:topic) | parm1 |
|---|---|---|
| suResidenceTSO | person:location | commjack |
| suMailCode | person:location | idmail |
| suResidenceLocation | person:location | residence |
