Summary: | Possible Duplication of Serials occurs during receiving process | ||
---|---|---|---|
Product: | Koha | Reporter: | Kelly McElligott <kelly> |
Component: | Serials | Assignee: | Bugs List <koha-bugs> |
Status: | RESOLVED INVALID | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | colin.campbell |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: |
Description
Kelly McElligott
2020-09-08 17:53:54 UTC
Hi Kelly, I think you need to change the serial enumeration first, before you open the item form. This way it will copy the new values to the item created. Or if you change in the item, you need to change it above or the recorded serial too. Does that make sense? Maybe change made in $h should automatically be copied to the issue line above as it works the other way around? Reading this again it feels like a misunderstanding. Changing the serial enumeration has no effect on the inner counters of the subscription and the prediction of the next issue. The enumeration, if changed, will be copied to the item form, when it's opened. But otherwise the 2 fields are independent from each other. The next issue predicted will be determined by the value in the subscription only. Katrin, Thank you! I completely understand what you are saying! Thank you! |