...
Available as of Registry v3.3.0, Ad Hoc Attributes are simple key/value pairs attached to CO Person Roles or Organizational Identities. Ad Hoc Attributes are available via the REST API, are supported by Organizational Identity Source Plugins and Pipelines, and are made available to Provisioner Plugins.
Ad Hoc Attributes are not currently validated in any way, do not support Enrollment Flows (CO-1478) or , and are not available to attach to the CO Person (CO-469).
| Note |
|---|
Because Ad Hoc Attributes are not neither namespaced nor typed, they should not be used as a replacement for solutions leveraging properly designed structured data. Ad Hoc Attributes are most suitable for simple, local data extensions where the cost of structured data is not warranted. |
...
More sophisticated requirements can be met by implementing native models, views, and controllers in the CakePHP framework. The best way to do that is probably to write a Plugin.
Extended Types
...
- Address Type
- CO Department Type (as of Registry v3.3.0)
- CO Person Role Affiliation
- Email Address Type
- Identifier Type
- Name Type
- Organization Type (as of Registry v4.0.0)
- Telephone Number Type
If an Extended Type is in use (by specifying an attribute of the type, or by referencing the type in an Enrollment Flow), it cannot be deleted or suspended.
The default types for any Extended Type can be restored by selecting the appropriate Extended Type and clicking Add/Restore Default Types. Any existing non-default types will remain.
As of Registry v4.1.0, Org Identities support Extended Types. Within a CO, CO Person and Org Identity attributes share the same set of available types. Org Identity Affiliation will use the same options as CO Person Role Affiliation.
eduPersonAffiliation and Extended Affiliations
...
When defining Extended Affiliations, the custom affiliations can be mapped to eduPersonAffiliations by selecting the appropriate value from the popup while adding or editing the custom affiliation. If a mapping is left blank, the eduPersonAffiliation will automatically map to an exact match (ie: student = student), otherwise a blank mapping is ignored.
Currently, this This mapping is only used by the LDAP Provisioning Plugin, which uses the mapping to populate the eduPersonAffiliation attribute, and the SQL Provisioning Plugin.