August 2019 - Koha-bugs - lists.koha-community.org

[Bug 21958] New: _check_valid_auth_link checks too many subfields
by bugzilla-daemon＠bugs.koha-community.org 05 Mar '23

05 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21958 Bug ID: 21958 Summary: _check_valid_auth_link checks too many subfields Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org In the sub we call C4::AuthoritiesMarc::GetAuthorizedHeading on the auth record for the field we use all subfields a-z - these are not all valid authorized heading fields To recreate - add a 700 field with $i - link it to an authority with the $i Run the linker in a way that it ends up checking the validity of this link, it will be rejected as not matching This can lead to multiple duplicate authorities being created depending upon settings -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 41

[Bug 16488] New: UNIMARC to MARC21 xslt to be used in z39.50 import sources
by bugzilla-daemon＠bugs.koha-community.org 04 Mar '23

04 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16488 Bug ID: 16488 Summary: UNIMARC to MARC21 xslt to be used in z39.50 import sources Change sponsored?: --- Product: Koha Version: 3.20 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Z39.50 / SRU / OpenSearch Servers Assignee: gmcharlt(a)gmail.com Reporter: theod(a)lib.auth.gr QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl It would be very helpful to have at least a 'basic' xsl template to be able to convert UNIMARC data to USMARC when trying to search and import data from UNIMARC z39.50 sources. It seems that there is a generic xslt available for UNIMARC to MARC conversion (https://github.com/edsd/biblio-metadata/blob/master/UNIMARC2MARC21.xsl) but it obviously needs a few changes to work with Koha. -- You are receiving this mail because: You are watching all bug changes.

1 30

[Bug 21361] New: Attributes appear in different order on batch patrons modifications
by bugzilla-daemon＠bugs.koha-community.org 03 Mar '23

03 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21361 Bug ID: 21361 Summary: Attributes appear in different order on batch patrons modifications Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: severine.queune(a)bulac.fr QA Contact: testopia(a)bugs.koha-community.org Created attachment 78954 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=78954&action=ed… Attribute display for the first batch modification When different patrons attributes exist, their order is different for each new batch modifictation on page /cgi-bin/koha/tools/modborrowers.pl See the 2 screenshots attached. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 17699] New: DateTime durations are not correctly subtracted
by bugzilla-daemon＠bugs.koha-community.org 01 Mar '23

01 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17699 Bug ID: 17699 Summary: DateTime durations are not correctly subtracted Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: normal 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 Depends on: 16911 >From DateTime::Duration pod: """ For positive durations, the "end_of_month" parameter defaults to wrap. For negative durations, the default is "limit". This should match how most people "intuitively" expect datetime math to work. """ Today we are Nov 30, that means $today->subtract( months => 1 ) will return Oct 31, when we usually expect Oct 30 in tests Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16911 [Bug 16911] Koha::Patrons - Move ExtendMemberSubscriptionTo to ->renew_account -- You are receiving this mail because: You are watching all bug changes.

1 48

[Bug 22417] New: Delegate background jobs execution
by bugzilla-daemon＠bugs.koha-community.org 28 Feb '23

28 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22417 Bug ID: 22417 Summary: Delegate background jobs execution 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 Target Milestone: --- This is related to: Bug 15032 - [Plack] Scripts that fork (like stage-marc-import.pl) don't work as expected Bug 1993 - Task Scheduler Needs Re-write And many others. The goal here would be to remove the background execution in real time we are doing right now and delegate the jobs to an external service (handling several workers, load balancing, etc.) -- You are receiving this mail because: You are watching all bug changes.

1 422

[Bug 18002] New: Add functionality to create a vendor and budget in the onboarding tool
by bugzilla-daemon＠bugs.koha-community.org 28 Feb '23

28 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18002 Bug ID: 18002 Summary: Add functionality to create a vendor and budget in the onboarding tool Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Installation and upgrade (web-based installer) Assignee: alexbuckley(a)catalyst.net.nz Reporter: alexbuckley(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Depends on: 17855 Add two additional interfaces to the onboarding tool to allow the user to create a vendor and budget before logging into Koha for the first time, thereby allowing users to get acquisition requirements set up. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17855 [Bug 17855] Updated Koha web installer and new onboarding tool feature to guide users through setting up Koha -- You are receiving this mail because: You are watching all bug changes.

1 96

[Bug 21263] New: Pickup library not set correctly when using Default holds policy by item type
by bugzilla-daemon＠bugs.koha-community.org 28 Feb '23

28 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21263 Bug ID: 21263 Summary: Pickup library not set correctly when using Default holds policy by item type Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Not sure if this is a bug or just me misunderstanding the options - Make sure OPACAllowUserToChooseBranch is set to don't allow - Make sure you have two branches A and B - Have one item whose homebranch is B - Have one user whose homebranch is A - Make sure the circulation rules allow the user to reserve the item's item type 1. Go to Administration > Circulation and fines rules 2. Create a Default holds policy by item type for that item type - Item type = item's item type - Hold policy = From any library - Hold pickup library branch = item's home library - Return policy = item returns home 3. Go to the OPAC and log in with the user's credentials 4. Search for the item 5. Click on "Place hold" 6. Confirm hold 7. In the user's file on the OPAC and check the reservation's pickup library What I understand : - Hold policy = From any library: Users from any library can reserve this item type - Hold pickup library branch = item's home library: the pickup library must be the item's homebranch (in this case, B) - Return policy = item returns home: upon return, the items is transferred to its homebranch Therefore, the pickup library in the case above should be B, but it is automatically set to A. P.S. note that I have item-level_itypes set to specific item, and Item level holds set to don't allow. I feel like in this case it should maybe fall back to the record-level item type? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13

[Bug 17550] New: Display additional patron data in patron suggestion form
by bugzilla-daemon＠bugs.koha-community.org 26 Feb '23

26 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17550 Bug ID: 17550 Summary: Display additional patron data in patron suggestion form 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: theod(a)lib.auth.gr QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When in Home › Circulation › Checkouts and the librarian wants to select a patron to perform a checkout upon, the suggestions currently display only the following patron data: Surname, Firstname (CardNumber) Address City Zipcode Country It would be nice if patron INITIALS were also displayed, like this: Surname, Firstname INITIALS (CardNumber) Address City Zipcode Country The reason is that multiple patrons may have the same Surname and Firstname and in order to distinguish them the librarians feel better to ask the patron for their initials rather than asking for the address (btw in our installation we use Father's name in place of initials, but this doesn't alter the use case) Further more, to better distinguish the various names and to make the Surname and Firstname 'stand out', I suggest converting them to bold, while making the initials italic. For all these changes the patch (in matter of code lines) is trivial: a few lines in two files. You may also find two screenshots of the current and the proposed functionality (the screenshots were taken from a Koha 3.20.x server but the change is applicable to recent versions also and the patch is created using the current master) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22

[Bug 18495] New: Creating a subgroup within report doesn' t add report to that group
by bugzilla-daemon＠bugs.koha-community.org 24 Feb '23

24 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18495 Bug ID: 18495 Summary: Creating a subgroup within report doesn't add report to that group Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Reports Assignee: gmcharlt(a)gmail.com Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org You can create a subgroup while editing/creating a report, but it doesn't add the report to that group. I didn't test if this is the case with the report group. -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 17987] New: Changing PatronSelfRegistrationDefaultCategory to a dropdown menu syspref
by bugzilla-daemon＠bugs.koha-community.org 23 Feb '23

23 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17987 Bug ID: 17987 Summary: Changing PatronSelfRegistrationDefaultCategory to a dropdown menu syspref Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleishaamohia(a)hotmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Rather than a free text syspref where a user can easily put in a category that doesn't exist. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12