May 2018 - Koha-bugs - lists.koha-community.org

[Bug 20313] New: Article requests: Can we do without the processing notice ?
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '19

03 Jun '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20313 Bug ID: 20313 Summary: Article requests: Can we do without the processing notice ? Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com For each article request we switch to processing status, Koha sends a mail to the patron. It does not tell much. The patron already received a mail that acknowledges his request; so why not send a mail only when the request has been completed? In other words: can we remove AR_PROCESSING ? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 20537] New: Warnings in overdue_notices.pl
by bugzilla-daemon＠bugs.koha-community.org 30 May '19

30 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20537 Bug ID: 20537 Summary: Warnings in overdue_notices.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz We've seen a warning from overdue_notices.pl: Use of uninitialized value in concatenation (.) or string at /usr/share/koha/bin/cronjobs/overdue_notices.pl line 575. I checked in our version and in master and think it happens for users withut a surname (organisations usually): 576 $borrowernumber = $data->{'borrowernumber'}; 577 my $borr = 578 $data->{'firstname'} . ', ' 579 . $data->{'surname'} . ' (' 580 . $borrowernumber . ')'; 581 $verbose Should we check here if firstname/surname are defined? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 19

[Bug 19520] New: Show more information about rotating collections
by bugzilla-daemon＠bugs.koha-community.org 30 May '19

30 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19520 Bug ID: 19520 Summary: Show more information about rotating collections Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: josef.moravec(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org On colections list and detail: - Number of items in collection - Number of transferred/untransferred items - Librarian who created the collection - Date of creation - Date of last transfer -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 19

[Bug 18939] New: Record matching rules didnot work by matching with callnumber
by bugzilla-daemon＠bugs.koha-community.org 30 May '19

30 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18939 Bug ID: 18939 Summary: Record matching rules didnot work by matching with callnumber Change sponsored?: --- Product: Koha Version: 16.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: importedbugs Assignee: koha-bugs(a)lists.koha-community.org Reporter: narapol(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org I try to migrate data from WISIS to koha. In record matching rules, I was created rule for matching with callnumber (tag 080$a). The result is "no matching found" , even though a match exists. If anyone met this issue before, please help me to fix. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 16276] New: When automatically suppressing expired borrowers, make sure they didn't log them selves recently
by bugzilla-daemon＠bugs.koha-community.org 30 May '19

30 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16276 Bug ID: 16276 Summary: When automatically suppressing expired borrowers, make sure they didn't log them selves recently Change sponsored?: Sponsored Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: nicolas.legrand(a)bulac.fr QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com We would like to automate the delation of expired patrons to comply to french laws regarding privacy. But we don't want to delate an expired patron which is still using the OPAC for bibliographical purpose, like managing lists. We would like to be able to say when the patron logged himself for the last time to permit this. Whith this parameter we would like to be able to use it from misc/cronjobs/delete_patrons.pl and also with the "Clean Patron Records" intranet page. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 77

[Bug 20485] New: Don't account for items timestamps when combining "dont_export_items=1" and "date" in export_records.pl
by bugzilla-daemon＠bugs.koha-community.org 30 May '19

30 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20485 Bug ID: 20485 Summary: Don't account for items timestamps when combining "dont_export_items=1" and "date" in export_records.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: glasklas(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz When combining "dont_export_items=1" and "date" it seams it would be safe and sane not to account for items timestamps in the date conditions, thus avoiding to include biblios that has not been modified but has modified/deleted items (which are included in the export anyway). -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 19

[Bug 20128] New: Permission for advanced editor
by bugzilla-daemon＠bugs.koha-community.org 30 May '19

30 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20128 Bug ID: 20128 Summary: Permission for advanced editor Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: kyle(a)bywatersolutions.com Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Work to be done: 1) Create a new permission, under the "cataloguing" module, that controls whether the professional cataloging editor is available. -- You are receiving this mail because: You are watching all bug changes.

1 38

[Bug 20762] New: "Duplicate patron record" alert empty fields
by bugzilla-daemon＠bugs.koha-community.org 30 May '19

30 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20762 Bug ID: 20762 Summary: "Duplicate patron record" alert empty fields Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons 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, kyle.m.hall(a)gmail.com The alert "Duplicate patron record?" we can get when adding a new patron empties different fields of the form : - all "Main address" fields - all "Alternate address" fields, except "Contact note" - all "Alternate contact" - all patrons attributes (and maybe others I didn't catch). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 15737] New: Patron userid lost during test for duplicate users
by bugzilla-daemon＠bugs.koha-community.org 30 May '19

30 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15737 Bug ID: 15737 Summary: Patron userid lost during test for duplicate users Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: david.roberts(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com If you create a new patron record and manually assign a unique cardnumber (userid in the borrowers table) and Koha identifies a possible duplicate record, clicking OK to create the user as a new user causes the manually-assigned userid to be replaced with the user's firstname.lastname. The manually entered userid should be remembered (as long as it is genuinely unique). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 19585] New: Inventory: working title 2
by bugzilla-daemon＠bugs.koha-community.org 29 May '19

29 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19585 Bug ID: 19585 Summary: Inventory: working title 2 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 23