Problem Description:
Users may want to conduct a search for records across multiple scopes. However, this is not currently possible.
One example of a scenario where one might want to do this is when searching for the members of an archival set. Right now, the frontend searches and sorts Objects and Works separately, because there is no possible way to search for them at the same time. (as was implemented in https://github.com/project-lux/lux-frontend/issues/27) However, searching and sorting for them together would allow for the correct sorting order.
Expected Behavior/Solution:
Users can search for records across multiple scopes (e.g. Objects and Works)
Requirements:
Other requirements TBD?
May have to have to do one or both of the following:
limit search terms to those that are the same in both scopes
Conduct 2 separate searches for each of the scopes and OR them together
Needed for promotion:
If an item on the list is not needed, it should be crossed off but not removed.
[ ] Wireframe/Mockup - Mike
[ ] Committee discussions - Sarah
[ ] Feasibility/Team discussion - Sarah
[ ] Backend requirements - TBD
[ ] Frontend requirements- TBD
[ ] Are new regression tests required for QA - Amy
[ ] Questions
List of questions for discussions. Answers should be documented within the issue.
UAT/LUX Examples:
TBD
Dependencies/Blocks:
Blocked By: Issues that are blocking the completion of the current issue.
Blocking: Issues being blocked by the completion of the current issue.
Related Github Issues:
Issues that contain similar work but are not blocking or being blocked by the current issue.
Sorting is critical for archival findings and the requirement for this issue is to sort by archival sort numbers. (merging objects/works in this context)
set tabs would be easy to support with this
OR could be a search scope for archival sets and archival materials.
This issue is a research ticket and will need to be prioritized.
Problem Description: Users may want to conduct a search for records across multiple scopes. However, this is not currently possible.
One example of a scenario where one might want to do this is when searching for the members of an archival set. Right now, the frontend searches and sorts Objects and Works separately, because there is no possible way to search for them at the same time. (as was implemented in https://github.com/project-lux/lux-frontend/issues/27) However, searching and sorting for them together would allow for the correct sorting order.
Expected Behavior/Solution:
Users can search for records across multiple scopes (e.g. Objects and Works)
Requirements:
Other requirements TBD? May have to have to do one or both of the following:
Needed for promotion: If an item on the list is not needed, it should be crossed off but not removed.
UAT/LUX Examples:
Dependencies/Blocks:
Related Github Issues:
Related links:
Wireframe/Mockup: Place wireframe/mockup for the proposed solution at end of ticket.