April 2020 - Koha-bugs - lists.koha-community.org

[Bug 23593] New: Link between suggestion and bibliographic record on OPAC
by bugzilla-daemon＠bugs.koha-community.org 18 May '20

18 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23593 Bug ID: 23593 Summary: Link between suggestion and bibliographic record on OPAC Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: severine.queune(a)bulac.fr QA Contact: testopia(a)bugs.koha-community.org The BULAC (http://www.bulac.fr/) would like to sponsor 3 different enhancements to ease the links between suggestion and bibliographic record. On this ticket : when suggestions’ status are ‘Ordered’ or ‘Available’ (=suggestions.biblionumber IS NOT NULL), add a link from the “Your purchase suggestions” tab to the bibliographic record on the OPAC. See also Bz 23592 for same behaviour on staff client. As long as “Change sponsored?” is set on “Seeking developer”, anyone wanting to quote us for the development of such a feature or just ask for more information is welcome to write to us: <sigb(a)bulac.fr>. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 23592] New: Link between suggestion and bibliographic record on staff client
by bugzilla-daemon＠bugs.koha-community.org 18 May '20

18 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23592 Bug ID: 23592 Summary: Link between suggestion and bibliographic record on staff client Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: severine.queune(a)bulac.fr QA Contact: testopia(a)bugs.koha-community.org The BULAC (http://www.bulac.fr/) would like to sponsor 3 different enhancements to ease the links between suggestion and bibliographic record. On this ticket : when suggestions’ status are ‘Ordered’ or ‘Available’ (=suggestions.biblionumber IS NOT NULL), add a link from the ‘/cgi-bin/koha/suggestion/suggestion.pl’ page to the bibliographic record on the staff client. As long as “Change sponsored?” is set on “Seeking developer”, anyone wanting to quote us for the development of such a feature or just ask for more information is welcome to write to us: <sigb(a)bulac.fr>. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 22685] New: Koha::Acquisition::Bookseller->baskets returns a dbic resultset rather than Koha::Objects
by bugzilla-daemon＠bugs.koha-community.org 18 May '20

18 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22685 Bug ID: 22685 Summary: Koha::Acquisition::Bookseller->baskets returns a dbic resultset rather than Koha::Objects Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- As the title says.. the relationship accessor passthrough here returns a plain dbic resultset rather than a Koha::Objects bassed object. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 25172] New: Koha::Logger init is failing silently
by bugzilla-daemon＠bugs.koha-community.org 18 May '20

18 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25172 Bug ID: 25172 Summary: Koha::Logger init is failing silently Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org This is terribly wrong as we are not aware the logger did not initiated correctly and we are going to lose logs. We should indeed make sure the error will be blocking and propagated to the interface. -- You are receiving this mail because: You are watching all bug changes.

1 42

[Bug 24080] New: Add a 'payout' process to accounts
by bugzilla-daemon＠bugs.koha-community.org 18 May '20

18 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24080 Bug ID: 24080 Summary: Add a 'payout' process to accounts Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, koha-bugs(a)lists.koha-community.org, testopia(a)bugs.koha-community.org Depends on: 23355, 23442 Blocks: 13985 There are times when a patron may end up with surplus credit on their account. The library should be able to pay out this credit as required and record the payout as a transaction. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13985 [Bug 13985] Cash Management - Koha as 'Point of Sale' https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23355 [Bug 23355] Add 'cashup' process to the accounts system https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23442 [Bug 23442] Add a 'refund' process to accounts -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. You are watching all bug changes.

1 85

[Bug 23596] New: Update/Delete suggestion reason when receiving the item
by bugzilla-daemon＠bugs.koha-community.org 18 May '20

18 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23596 Bug ID: 23596 Summary: Update/Delete suggestion reason when receiving the item Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: severine.queune(a)bulac.fr QA Contact: testopia(a)bugs.koha-community.org The BULAC (http://www.bulac.fr/) would like to add the ability to update and/or delete the suggestions.reason field when receiving an item. It’s a field we mostly use to inform the patron on the future acquisition of this title, and after the receipt, it becomes obsolete so need to be emptied. It could also be used to add a new comment or to update the existing one to inform the patron (for example, about the cataloguing times, eg: “we won’t have a hebrew librarian until 2021-2023, so suggestions have to wait for a couple of years before being available” → a useful information for patrons, especially the one who made the suggestion and have been informed of the receipt). As long as “Change sponsored?” is set on “Seeking developer”, anyone wanting to quote us for the development of such a feature or just ask for more information is welcome to write to us: <sigb(a)bulac.fr>. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 30

[Bug 23594] New: Batch modification for itemtypes on suggestions page
by bugzilla-daemon＠bugs.koha-community.org 18 May '20

18 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23594 Bug ID: 23594 Summary: Batch modification for itemtypes on suggestions page Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: severine.queune(a)bulac.fr QA Contact: testopia(a)bugs.koha-community.org The BULAC (http://www.bulac.fr/) would like to sponsor an enhancement to allow a batch modification of ‘suggestions.itemtype’ (depending on authorized values SUGGEST_FORMAT list) at the bottom of the page /cgi-bin/koha/suggestion/suggestion.pl, like it exists for suggestions.status et suggestions.reason datas. As long as “Change sponsored?” is set on “Seeking developer”, anyone wanting to quote us for the development of such a feature or just ask for more information is welcome to write to us: <sigb(a)bulac.fr>. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 50

[Bug 23591] New: Add a new "Suggestions details" tab on bibliographic record
by bugzilla-daemon＠bugs.koha-community.org 18 May '20

18 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23591 Bug ID: 23591 Summary: Add a new "Suggestions details" tab on bibliographic record Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: severine.queune(a)bulac.fr QA Contact: testopia(a)bugs.koha-community.org The BULAC (http://www.bulac.fr/) would like to sponsor 3 different enhancements to ease the links between suggestion and bibliographic record. On this ticket : creation of a new tab ‘Suggestion details’ on bibliographic record, displaying all the useful informations (dates, status, comments, branchocde, etc.) and a link to the suggestions module. This tab would be only be displayed when ‘suggestion’ syspref in ON, and when a suggestion exist for a record to keep nice and clear informations. We don’t know if it would be better to have a tab after the ‘Acquisition details’ or a lateral one (between ‘article requests’ and ‘Checkout history’ for exemple). As long as “Change sponsored?” is set on “Seeking developer”, anyone wanting to quote us for the development of such a feature or just ask for more information is welcome to write to us: <sigb(a)bulac.fr>. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 48

[Bug 22437] New: Subsequent authority merges in cron cause biblios to lose authority information
by bugzilla-daemon＠bugs.koha-community.org 18 May '20

18 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22437 Bug ID: 22437 Summary: Subsequent authority merges in cron cause biblios to lose authority information Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: pjamorim91(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Here's how to reproduce the problem: AuthorityMergeLimit syspref is default 50. Here's an example list of 3 authorities (A, B and C) that should be merged together - resulting in 1 authority - and the total count of biblios linked to each respective authority (similar to the interface you get when searching authorities): A 100 B 60 C 2 The good scenario: If you merge the authorities like this: First: C -> A Second: B -> A All is good, after the first merge (C -> A), A has 102 biblios. After second merge (B -> A), B no longer exists and A still has 102 - as expected, because the merge is scheduled to the cron. After forcing the cron koha-foreach --chdir --enabled /usr/share/koha/bin/cronjobs/merge_authorities.pl -b -v authority A now has 162 biblios, as expected. The bad scenario: The problem occurs if authorities are merged like this: First: C -> B Second: B -> A After the first merge (C -> B), B has 62 biblios. After the second merge (B -> A), B no longer exists and A still has 100 - as expected, because the merge is scheduled to the cron. However, after forcing the cron koha-foreach --chdir --enabled /usr/share/koha/bin/cronjobs/merge_authorities.pl -b -v authority A still has 100 biblios, and the 62 biblios that were previously linked to B have effectively lost the authority information they previously had. After some testing, I noticed that Koha will schedule an authority merge for the same authority (on itself), even when the biblios count doesn't surpass AuthorityMergeLimit, I'll explain: For the C -> B merge, the 2 biblios from C will be updated immediately in the application (because 2 < 50), but simultaneously Koha will schedule the cron merge B -> B. I think this happens because the merge.pl script first modifies the reference authority using ModAuthority (that calls the merge function), and then calls the merge function, can be seen here: https://github.com/Koha-Community/Koha/blob/18.11.x/authorities/merge.pl#L79 Which means that Koha will run the merge function, twice, for each authority merge made in the application. I think this is by design, because if B gets modified, Koha will have to update 60 biblios with the new authority information, updated subfields information etc, and this should be indeed postponed to the cron, hence the merge on itself B -> B caused by ModAuthority. However, because B -> A happened (deleting B) after C -> B and before the cron had the chance to run, by the time the cron has to run B -> B, B has already been deleted, cleaning the authority information from the 60 (or 62) biblio records. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 62

[Bug 25082] New: Unknown language code if 041 $a is linked to an authorized value list
by bugzilla-daemon＠bugs.koha-community.org 18 May '20

18 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25082 Bug ID: 25082 Summary: Unknown language code if 041 $a is linked to an authorized value list Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: MARC Bibliographic data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: pablo.bianchi(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org >From Bug 20364, comment 13: When 041 $a (Language code of text/sound track or separate title) is associated with the LANG authorized value list, then the detail view of the record (OPAC and Intranet) show an "Unknown language code", even if the value of the subfield is a valid language code. This text comes from MARC21Languages.xsl. This behavior was expected? Maybe MARC21Languages.xsl code → Language list should be just a fallback if the code is not present/translated on associated list (probably LANG). -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 44