Registry Data Model

Overview

The COmanage Registry Data Model revolves around the CO Person, which conceptually represents one person associated with a CO.

In order for a person to become a CO Person, they must first have at least one Org Identity, which conceptually represents their identity as asserted by a "home" institution, such as their University or a social identity provider.
A CO Person record is created and one or more Org Identities are linked to it. The CO Person record maintains information that is unique to a person within the CO, such as names and identifiers.
A CO Person may have one or more CO Person Roles within the CO. A CO Person Role record maintains information that is unique to a role a person has within a CO, such as title and physical address.

Table Name	Description	Status
cm_addresses	Addresses	Tentative
cm_api_users	API (Programmtic) Users	To be refactored
cm_applications	Known applications	Not implemented
cm_co_applications	Per-CO configured applications	Not implemented
cm_co_directory_permissions	Per-CO restrictions on publishing of directory information	Not implemented
cm_co_extended_attributes	Per-CO extended attributes	Tentative
cm_co_fifer_servers	Per-CO FIFER services	Experimental
cm_co_groups	Per-CO groups	Tentative
cm_co_group_members	Per-CO group memberships	Tentative
cm_co_invites	Per-CO invitations to join	To be refactored
cm_co_person_roles	Per-CO person role identity	Tentative
cm_co_person_sources	Per-CO link from person to org person	Tentative
cm_co_role_assignments	Per-CO person role assignments	Not implemented
cm_co_role_groups	Per-CO group memberships implied by role	Not implemented
cm_co_roles	Per-CO role definitions	Not implemented
cm_configuration	COordinate configuration values	Not implemented
cm_cos	Definitions of (virtual) organizations	Tentative
cm_cous	Definitions of (virtual) organization units	Tentative
cm_email_addresses	Email Addresses	Tentative
cm_history	Transaction history (human readable)	Not implemented
cm_identifiers	Person identifiers, from organizational source	Tentative
cm_names	Names	Tentative
cm_org_identities	Person identity, from organizational source	Tentative
cm_organizations	Definitions of (real) organizations	To be refactored
cm_permissions	Permissions for COoordinate	Not implemented
cm_telephone_numbers	Telephone numbers	Tentative

View All Tables.
Auditing: If enabled, each table will have a corresponding cma_ table with an additional timestamp column with all previous values.

Data	Potential Storage
Applications	SQL, LDAP?, Config file?
Changelog	SQL, Log files
Groups	SQL, Grouper
History	SQL, Log files
Invites	SQL, LDAP?
Mailing Lists	Mailman, Sympa, /etc/aliases, etc
Monitoring	Nagios, etc
Organizations	SQL, LDAP
People	SQL, LDAP
Permissions	SQL, Grouper, Config file?
Reports	JasperReports, etc
Roles	SQL, Grouper