Search Results when selected Search Type: All
Description
Environment
Potential Workaround
Attachments
is blocked by
is cloned by
Checklist
hideTestRail: Results
Activity
Charlotte Whitt December 28, 2017 at 10:00 PMEdited
Updated UX design:
1) Local & KB are selected; filter setting:
2) Local & KB are selected; Dropdown menu with Search Criteria
3) Local & KB are selected; View a detailed page of a printed book
4) Local & KB are selected; View a detailed page of a printed journal
5) Local & KB are selected; View a detailed page of an electronic journal
Mike Taylor December 18, 2017 at 2:47 PM
They're wired in. I'm calling this done (though there are column-width errors that I will file separately).
Mike Taylor December 11, 2017 at 5:32 PM
Filip has supplied the icons. I will wire them into the app tomorrow.
Mike Taylor December 8, 2017 at 3:41 PM
Do the source-type icons in the screenshot exist? Where can I find them?
Mike Taylor December 8, 2017 at 3:36 PM
Adding and to discuss this part:
When searching across all sources (Inventory and eHolding)
The default setting for search will be
all titles in Inventory which is not suppressed from staff view
all titles in the eHolding app which are 'selected' by the library
How do we imagine that constraints like "not suppressed" will be implemented? The Codex UI application certainly can't include anything in its CQL that specifies such constraints, as it is constructing a generic query suitable for all the back-ends. I assume that the Codex multiplexer also doesn't want to have to know such details, so that it tweaks the query differently for each back-end that it contacts. So are we just relying on the back-end modules that implement the codex interface to know that they must omit suppressed records?
Assumption is that print and eResources are blended in search results, and we don’t have any merging or de-duplication of records from local inventory and KB instances in eHoldings (in alpha)
Purpose:
When using the Codex App, then the librarian can search in Codex, and search across the local catalog (the Inventory, for alpha) together with KB-sources (which is equal the eHolding app for alpha).
Scenarios:
1. Scenario
When in the Codex Search app
The default setting will be All sources
2. Scenario
When in the Codex Search app, and the default setting is All
Then search will be conducted across the Inventory app and the eHolding app (for alpha)
3. Scenario
When searching across all sources (Inventory and eHolding)
The default setting for search will be
all titles in Inventory which is not suppressed from staff view
all titles in the eHolding app which are 'selected' by the library
4. Scenario
When in searching for a title the 'All ...' source is marked
Then the user fill in a search in the search box e.g. Abigail
When viewing the search results the user sees titles from both Local-titles and KB titles
The search result is blended showing printed, and e-resources sorted by title as default
5. Scenario
When viewing the search result the user can see a little icon for
indicating this is a local title or
indicating this is a KB title
(see the attached screendump)