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

[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 24905] New: log4perl.conf.in missing entries for the z39.50 server
by bugzilla-daemon＠bugs.koha-community.org 18 May '20

18 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24905 Bug ID: 24905 Summary: log4perl.conf.in missing entries for the z39.50 server Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Packaging Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: mirko(a)abunchofthings.net Bug 13937 introduced new log4perl.conf changes, but missed to tweak the packages' log4perl.conf.in template. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 26

[Bug 24204] New: Talking Tech i-tiva is now illion Digital Tech Solutions
by bugzilla-daemon＠bugs.koha-community.org 16 May '20

16 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24204 Bug ID: 24204 Summary: Talking Tech i-tiva is now illion Digital Tech Solutions Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org The third-party service Tallking Tech i-tiva was acquired by illion Digital Tech Solutions in 2018 (https://www.linkedin.com/company/talkingtech/?originalSubdomain=nz) Updates are required to reflect this. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 24701] New: Add column configuration to course_items_table in the OPAC
by bugzilla-daemon＠bugs.koha-community.org 16 May '20

16 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24701 Bug ID: 24701 Summary: Add column configuration to course_items_table in the OPAC Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: lisetteslatah(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org from Bug 23547 Katrin Fischer 2019-09-05 16:00:44 UTC It would be nice if it was easy to hide columns from the course reserves table in the OPAC (example: hide the Link column because it doesn't contain full text links reliably). Bug 23547 adds the ability to configure columns for course_reserves_table on the OPAC. It would be helpful to also add configuration for course_items_table in the OPAC. Lisette -- You are receiving this mail because: You are watching all bug changes.

1 20

[Bug 24530] New: Show a number in title notes just as in the other tabs
by bugzilla-daemon＠bugs.koha-community.org 16 May '20

16 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24530 Bug ID: 24530 Summary: Show a number in title notes just as in the other tabs Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org Although we do not show an empty title notes tab [see bug 10349], the number of notes might still be interesting just as we do for other tabs on the detail page like holdings, subscriptions, comments, etc. Intuitively, you are also inclined to think that there are no notes when you see a number after holdings and no number after descriptions etc. -- You are receiving this mail because: You are watching all bug changes.

1 29

[Bug 20648] New: Attribute option "Display in check-out" should be rename
by bugzilla-daemon＠bugs.koha-community.org 16 May '20

16 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20648 Bug ID: 20648 Summary: Attribute option "Display in check-out" should be rename Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: severine.queune(a)bulac.fr QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Attributes checked "Display in check-out" are now displayed on side panel of all tabs in patron account thanks to Bug 12159. The description "Display in check-out: Check to show this attribute in patron check-out" on the "Attribute menu" should be modifiy now. --> "Display in patron's brief information" ? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 20

[Bug 21921] New: Add date publication year to biblio Z39.50 search form
by bugzilla-daemon＠bugs.koha-community.org 16 May '20

16 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21921 Bug ID: 21921 Summary: Add date publication year to biblio Z39.50 search form Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Z39.50 / SRU / OpenSearch Servers Assignee: koha-bugs(a)lists.koha-community.org Reporter: black23(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 23

[Bug 24576] New: `StoreLastBorrower` preference is in the wrong tab and is confusing
by bugzilla-daemon＠bugs.koha-community.org 16 May '20

16 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24576 Bug ID: 24576 Summary: `StoreLastBorrower` preference is in the wrong tab and is confusing Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration 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 As far as I can make out, the `StoreLastBorrower` preference is available to allow staff to track down who may have returned an item last when said item is found to be damaged or lost even when privacy policy or patron privacy settings are set to anonymize checkout history. As such, I feel this setting would be better placed under the `Circulation`, `Logs` or `Staff client` tabs with a clearer explanation for it's use. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14