Summary: | In reserve/request.pl biblioitemnumber is used where biblionumber is required. | ||
---|---|---|---|
Product: | Koha | Reporter: | Andreas Jonsson <andreas.jonsson> |
Component: | Circulation | Assignee: | Bugs List <koha-bugs> |
Status: | RESOLVED DUPLICATE | QA Contact: | Testopia <testopia> |
Severity: | normal | ||
Priority: | P5 - low | CC: | gmcharlt, jonathan.druart, kyle.m.hall, martin.renvoize, nick, nugged |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
See Also: | https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26518 | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: | |||
Bug Depends on: | 24185 | ||
Bug Blocks: |
Description
Andreas Jonsson
2020-09-23 18:01:21 UTC
biblioitemnumber and biblionumber must be contain the same value. If not you are going to face some oddities. There is nothing enforcing the sameness of these two identifiers and they typically are not the same on any of our installations. (If the relationship between biblio and biblioitem is one-to-one I think that biblioitemnumber should be removed as it only provokes this type of coding errors.) The relationship is 1:1 in modern Koha, but it didn't use to be. The change is not so easy overall, but it has been discussed to merge tables many times I think. I am not sure why they are not the same in your dbs - they are in ours. It means, sometime they must have gotten out of sync. Bug 26518 - it is quite easy to get these numbers out of sync I think we can safely de-escalate this one.. bug 26518 goes a long way to preventing the fields from getting out of sync and we can continue working on removing biblioitemnumber entirely in due course. |