https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34482 --- Comment #13 from Martin Renvoize (ashimema) <martin.renvoize@openfifth.co.uk> --- Hi all, An update on the order of work I suggested above. Patches are now attached for most of it: 1. Bugs 35117 and 41713: no 001 should not search for an undefined value. - 35117 (Needs Signoff): rebased, with a title search when there is no 001, for both volumes and components. - 41713 (Failed QA): depends on 35117, waiting for the authors to agree what is kept from it. - 44063 (Signed Off): the component sort preferences were never applied (found while doing this). 2. More specific indexes: - 39287 (Signed Off): rcn-volumes, now also mapped for Elasticsearch, used by the OPAC link, and with an atomic update. - 38252 (Needs Signoff): rcn did not hold the $w of 760, 762, 765, 767, 786 and 788. - 42027 (Needs Signoff): Show volumes for serials, using rcn-volumes. - 35330 (Needs Signoff): rcn-components, that only holds 773$w, for the components (analytics) of a record. It also moves the series links to rcn-volumes. 3. Matching $w on the (OrgCode)control number form: bug 44064 is the design bug, with bugs 27507, 29268 and 21472 as related work. This is not started. 4. Re-testing bugs 31608, 43113, 26480 and 26333 once the above is in. Things for whoever tests and pushes: - 39287, 38252 and 35330 all add or change search index definitions, so they touch bib1.att, ccl.properties, the Zebra index definitions and mappings.yaml in nearby places. 35330 builds on 39287, so push 39287 first. The others may need a trivial rebase. - Installations need to reindex after each of them, and with Zebra copy bib1.att, ccl.properties and biblio-zebra-indexdefs.xsl to their configuration first, so this needs a release note. Elasticsearch installations get the new fields through the atomic updates. - A few of the patches change the number of tests at the top of t/db_dependent/Koha/Biblio.t, which will also need a trivial rebase. Testing notes from David on bugs 35117 and 44063 are very helpful, thanks David. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.