Summary: | Inventory lists incorrectly sorted | ||
---|---|---|---|
Product: | Koha | Reporter: | David Cook <dcook> |
Component: | Tools | Assignee: | Bugs List <koha-bugs> |
Status: | CLOSED WONTFIX | QA Contact: | Testopia <testopia> |
Severity: | normal | ||
Priority: | P5 - low | CC: | black23 |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
See Also: |
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19021 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22263 |
||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: |
Description
David Cook
2018-09-28 06:29:31 UTC
Maybe the name of this bug should then be "Add a script to update cn_sort"? This is a data problem and not a problem of the sorting itself. touch_items is rather costly/time consuming, we recently fixed it using a little script creating SQL statements for the updates. (In reply to Katrin Fischer from comment #1) > Maybe the name of this bug should then be "Add a script to update cn_sort"? > This is a data problem and not a problem of the sorting itself. > Yeah that could be a good idea. I guess I'm not sure at this point why the cn_sort values became inconsistent, so looking for ideas. Although based on what you said on IRC, I'm thinking maybe it's an issue with an external dependency? If it is an external dependency, maybe I can trace in what version it changed and then base the update around that? > touch_items is rather costly/time consuming, we recently fixed it using a > little script creating SQL statements for the updates. You mean you created a little script for updating cn_sort? I hadn't thought of doing the update directly like that. That's a good idea. I don't suppose we use the cn_sort value in any indexes? I think we have foregone the Zebra updates - but we will update them soon anyway which will include a full reindex. Another thing to check: Is cn_source set correctly in all items? It's easy to have some bad configuration there. (In reply to Katrin Fischer from comment #3) > Another thing to check: Is cn_source set correctly in all items? It's easy > to have some bad configuration there. I was thinking that as well but in my case the items seemed to all have cn_source set correctly. I feel if we agree this is a data issue, the bug could probably be closed? I filed bug 22263 for adding a maintenance script. (In reply to Katrin Fischer from comment #5) > I feel if we agree this is a data issue, the bug could probably be closed? > I filed bug 22263 for adding a maintenance script. Sounds good to me. |