Loading...

XML

Word

Printable

Type: Task
Resolution: Unresolved
Priority: Major
Fix Version/s: COmanage Registry 5.0.0 (Pupal Eclosion)
Affects Version/s: COmanage Registry 0.9.3 (Essential Enneagon Plus Plus Plus)
Component/s: Registry
Labels:
None

There is currently an API for matching, but it isn't used. (Matching happens via AJAX calls returning new page content.) There are also calls to search org identities and CO people by identifier, but they use a different mechanism and currently rely on a hack in StandardController::index. In addition, various API calls are effectively searches (eg: view all by CO ID) but aren't implemented as such.

Clean this all up and unify it as appropriate. Possibly adopt a more sophisticated search language for the API.

has dependent

CO-1288 Performing a search of CO Person records from within an enrollment flow exits the enrollment flow

Resolved

is related to

CO-1007 Refactor search.inc

Resolved

CO-906 "Search" should be "search"

Resolved

CO-324 Support Pagination in REST API

Open

CO-209 Search Box (Simple Search)

Resolved

CO-819 Cross Model Search

Resolved

CO-1101 Search on CO Person Role Attribues

Open

CO-298 Make Reconciliation More Configurable (Enrollment Flow Integration with Match Server)

Resolved

CO-2288 REST API Search By EmailAddress

Resolved

CO-1824 Add search by email in CoPerson's REST API

Resolved

(5 is related to)

Assignee:: Benn Oshrin (internet2.edu)
Reporter:: Benn Oshrin (internet2.edu)
Votes:: 0 Vote for this issue
Watchers:: 2 Start watching this issue

Created:: 29/Mar/15 12:04 AM
Updated:: 12/Jul/23 2:57 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates