Registry offers two ways to find operational records: Filtering and (available since Registry v3.1.0) Searching. (Prior to Registry v3.1.0, Filtering was called "searching".)
Filtering involves navigating to the main index view for a type of object, typically from the main menu. Once there, it is possible to filter the list of objects by specifying attributes in the filter form.The following models support filtering:
- CO People
- Org Identities
Only CO and COU Administrators may perform filtering.
Searching operates across the entire Registry. If an exact match for a given search term is found, the resulting match record will be displayed, otherwise a set of search results, grouped by object type, will be presented. Each model determines how to handle a search, including which fields to search, whether to look for a substring or an exact string, and whether to tokenize the search time (ie: split it on spaces and treat each token individually). The following models support searching:
- Address* (street, tokenized)
- CoDepartment (name, tokenized)
- CoEmailList (name)
- CoEnrollmentFlow (name, tokenized)
- CoGroup (name, tokenized)
- CoPerson (via associated models)
- CoPersonRole (title, o, ou, tokenized; also via associated models)
- CoService (name, tokenized)
- EmailAddress* (mail, exact match only)
- Identifier* (identifier, exact case sensitive match only)
- Name* (given, middle, family, tokenized)
- TelephoneNumber* (identifier, exact case sensitive match only)
- As of Registry v3.2.0, Registry Plugins may implement custom search backends
*Only records associated with a CO Person or CO Person Role are currently supported. Searching records associated with an Org Identity is not currently supported. (CO-1537)
Any CO Person may perform a search within the CO, however the search results will be limited to the records they have permission to see.
Other Types of Searching
Organizational Identity Sources must be searched individually, since their databases are external to Registry.