MARCcat: MARC Bibliographic records
(UXPROD-786)
|
|
| Status: | Closed |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None | Parent: | MARCcat: MARC Bibliographic records |
| Type: | New Feature | Priority: | P3 |
| Reporter: | Annalisa Di Sabato | Assignee: | Tiziana Possemato |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | MARCcat-Bib, complex_query, indexed, po-mvp, po-sow, q4-2019-spillover, search, team-mvp | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||||||||||||||||||||||
| Potential Workaround: | Laura : Perform complex searches elsewhere (e.g., OCLC, National Catalog, Inventory), then search MARCcat by record identifier.
Tiziana: MARCcat provides more than 400 indexes and obviously includes secondary indexes. The problem now is that we don't have the Stripes components to create pages to perform this search using secondary indexes. We have back-end services and we are waiting for user interface components. So how can we include po-mvp if we are not sure of the ability to do it? |
||||||||||||||||||||||||||||||||||||||||
| Epic Link: | MARCcat: MARC Bibliographic records | ||||||||||||||||||||||||||||||||||||||||
| Analysis Estimate: | Small < 3 days | ||||||||||||||||||||||||||||||||||||||||
| Front End Estimate: | Small < 3 days | ||||||||||||||||||||||||||||||||||||||||
| Front End Estimator: | Matteo Pascucci | ||||||||||||||||||||||||||||||||||||||||
| Back End Estimate: | Small < 3 days | ||||||||||||||||||||||||||||||||||||||||
| Development Team: | @cult | ||||||||||||||||||||||||||||||||||||||||
| UX Lead: | Matteo Pascucci | ||||||||||||||||||||||||||||||||||||||||
| Rank: Chalmers (Impl Aut 2019): | R5 | ||||||||||||||||||||||||||||||||||||||||
| Rank: Chicago (MVP Sum 2020): | R4 | ||||||||||||||||||||||||||||||||||||||||
| Rank: Cornell (Full Sum 2021): | R5 | ||||||||||||||||||||||||||||||||||||||||
| Rank: Duke (Full Sum 2021): | R2 | ||||||||||||||||||||||||||||||||||||||||
| Rank: 5Colleges (Full Jul 2021): | R3 | ||||||||||||||||||||||||||||||||||||||||
| Rank: GBV (MVP Sum 2020): | R5 | ||||||||||||||||||||||||||||||||||||||||
| Rank: hbz (TBD): | R1 | ||||||||||||||||||||||||||||||||||||||||
| Rank: Hungary (MVP End 2020): | R1 | ||||||||||||||||||||||||||||||||||||||||
| Rank: Lehigh (MVP Summer 2020): | R1 | ||||||||||||||||||||||||||||||||||||||||
| Rank: TAMU (MVP Jan 2021): | R1 | ||||||||||||||||||||||||||||||||||||||||
| Rank: U of AL (MVP Oct 2020): | R1 | ||||||||||||||||||||||||||||||||||||||||
| Description |
|
NOTE: This feature covers complex queries for Bibs, Holdings, and Authorities We need to include in the Search module of MARCcat the Secondary indexes to make complex query. We're waiting David's prototype. Complex queries need to search across bibs, holdings, and authorities Figure out what can be handled via Filters versus CQL query (adapt the CQL query being used by Inventory now?) |
| Comments |
| Comment by Anya [ 29/Mar/19 ] |
|
Comment from the March meeting : Need an example - how is this different from primary searching? |
| Comment by Annalisa Di Sabato [ 31/May/19 ] |
|
Primary indexes refer to the searchable indexes or fields, like NA (index to search an author that start with name XXX), TI (index to search a title that start with title YYY), SU (index to search a subject that start with subject ZZZ) and so on... Secondary indexes are used to modify and refine a search statement. These indexes are called Secondary because they must me combined with a Primary index. We have a lot of Secondary indexes, like for example: "BIB=a" to search record with a particular bibliografic level , that is part of monograph, "BIB=s" to search a record that is a serial .... to resume are all indexes that allow to search the values set in all tag MARC21, above all in tag 000/006/007/008. |
| Comment by Annalisa Di Sabato [ 26/May/20 ] |
|
We can not develop the function to do an advanced search using the Secondary Index, because there aren't suitable components in Stripes that allow to manage these several indexes. So we will develop the function search related to the complex query described in the https://folio-org.atlassian.net/browse/UICAT-3. |
| Comment by Tiziana Possemato [ 11/Nov/20 ] |
|
We need to freeze this issue until a technological solution to manage, in the UI, the selection of secondary indexes to build complex queries. Check with UI FOLIO designers to find a practical/graphical solution. All primary and secondary indexes are already present and working on the MARCcat backend. |
| Comment by Jacquie Samples [ 13/Jan/21 ] |
|
We are re-ranking this JIRA for the functionality, not as part of MARCcat epic. This functionality is more greatly desired due to the lack of the MARCcat tool as envisioned by the sub-group. |
| Comment by Ann-Marie Breaux (Inactive) [ 19/Jan/21 ] |
|
As of Jan 2021, development of MARCcat has ceased. Will incorporate some features into quickMARC. |