Details
-
Story
-
Status: Closed (View Workflow)
-
P2
-
Resolution: Done
-
-
LIBAPP Sprint 5
Description
Purpose: Extend basic search for Users app and modify so it makes use of CQL. Because these are fields that are currently available in the schema, the initial search will be of the Username and Full Name only. We plan to change that later to include all Identifiers, once those have been added to the record metadata. Eventually we plan to have an unqualified search that searches all user metadata, but that will require implementing special sorting logic to ensure the most relevant matches are at the top. Given that, our first increments of search will be against a subset of fields.
As a library administrator who is working with the Users app
I want to be able to search users by Username or Full Name
So I can locate a user to view and/or edit
TestRail: Results
Attachments
Issue Links
- is blocked by
-
DMOD-119 use CQL for searching/filtering records in mod-users
-
- Closed
-
-
DMOD-143 CQL queries should match words, not substrings
-
- Closed
-
-
LIBAPP-56 Search Users v1 - Keyword Search
-
- Closed
-
-
STRIPES-126 Add hack to Okapi Console, sending new magic request when modules are deployed
-
- Closed
-
-
STRIPES-128 Change Users module to send CQL instead of Postgres JSON. Hurrah!
-
- Closed
-
- is cloned by
-
LIBAPP-68 Search Users v3 - Search by First Name, Last Name and Username
-
- Closed
-
-
UIU-5 Search Users v3 - Search by All Identifiers
-
- Closed
-
- relates to
-
LIBAPP-53 View User List - Default Sort by Username
-
- Closed
-
-
DMOD-144 CQL queries should be against abstract indexes, not schema elements
-
- Open
-
-
DMOD-145 CQL searching should be case-insensitive
-
- Closed
-
-
LIBAPP-54 Filter User List by Status
-
- Closed
-