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

[Bug 34030] New: Print slips in a batch from the preservation module
by bugzilla-daemon＠bugs.koha-community.org 08 May '24

08 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34030 Bug ID: 34030 Summary: Print slips in a batch from the preservation module Change sponsored?: Sponsored Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Tools Assignee: jonathan.druart+koha(a)gmail.com Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 33547 Bug 33547 add a 'print slip' button to print the info for a given item, but it would be great to have a 'print slips' action button that could be clicked after we have selected a bunch of items and that would print all slips on the same document. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33547 [Bug 33547] Print slips from the preservation module -- You are receiving this mail because: You are watching all bug changes.

1 34

[Bug 25324] New: After editing an authority record with CatalogModuleRelink on, relinking appears to happen before the edited record is saved
by bugzilla-daemon＠bugs.koha-community.org 07 May '24

07 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25324 Bug ID: 25324 Summary: After editing an authority record with CatalogModuleRelink on, relinking appears to happen before the edited record is saved Change sponsored?: --- Product: Koha Version: master 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: phil(a)chetcolibrary.org QA Contact: testopia(a)bugs.koha-community.org The actual behavior these contrived steps imitate is using AutoCreateAuthorities and CatalogModuleRelink, using LinkerModule: First Match so that in case of duplicate authorities the linker will choose the first, oldest, lowest authid, and then buying one book by an author before he dies, cataloged with Name, Birthyear-, and then buying another after he dies, cataloged with Name, Birthyear-Deathyear. 1. Set AutoCreateAuthorities, BiblioAddsAuthorities, CatalogModuleRelink, and LinkerModule: First Match 2. Create a personal name authority record with 100 1# $aBrzezinski, Zbigniew,$d1928- (imitating one you imported before 2017) 3. In any existing bib record, add a 700 linked to that authority record, just so it has a linked bib 3. Cataloging, new from Z39.50, search for Brzezinski, Zbigniew as author, import and save any record with the 100 field having his $d as 1928-2017. 4. Since your report of newly created authority records shows Brzezinski, Zbigniew, 1928-2017 when you know you already owned something he wrote, go to Authorities and search for Brzezinski. You need to update your previously imported record (well, the fake of one you created), so Edit the one without a 2017, Replace record via Z39.50, find the 1928-2017 record and import and save it. 5. Search again for Brzezinski. Expected results: Because you created the one that was originally 1928- first, before the one autocreated as 1928-2017 from your imported bib record, and you set First Match as your LinkerModule, you should expect that when you edit the first record in a way that causes the two records to become duplicates, that relinking would link both bib records to the first match. Actual results: Both bib records are linked to the second match, the autocreated one, rather than to the original, looking very much like the bib record without -2017 was updated and both bib records were relinked before the authority record you turned into a match actually was a match. As a result, rather than just being able to delete a now-unused autocreated record, you have to merge it to your newly edited record. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 36107] New: Port default DUEDGST and PREDUEDGST notices to Template Toolkit
by bugzilla-daemon＠bugs.koha-community.org 07 May '24

07 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36107 Bug ID: 36107 Summary: Port default DUEDGST and PREDUEDGST notices to Template Toolkit Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Keywords: roadmap_24_05 Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: emily.lamancusa(a)montgomerycountymd.gov QA Contact: testopia(a)bugs.koha-community.org Blocks: 15278 The following notices need to be updated to use Template Toolkit syntax: DUEDGST (email) DUEDGST (sms) PREDUEDGST (email) PREDUEDGST (sms) These will be a bit trickier, as they make use of <<items.content>>. The default information in <<items.content>> is the due date, title, author, and barcode of the item. Since this bug is limited to changing the default notice text, and won't affect existing installations, we could be okay to simply replicate that information with Template Toolkit variables for now. We will need to decide what to do about <<items.content>> if/when we deprecate hungry alligator syntax in the long run, though. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15278 [Bug 15278] [Omnibus] Port default slips and notices from bespoke syntax to Template Toolkit -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 36504] New: Run report should have an option to only send the attachment
by bugzilla-daemon＠bugs.koha-community.org 06 May '24

06 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36504 Bug ID: 36504 Summary: Run report should have an option to only send the attachment Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Currently, if runreport sends results via email, they are included in the body when also supplied as an attachment. Some libraries would like to receive only the attachment, to make the email less cluttered for large reports. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 17763] New: Exact ponctuation and words order is needed for matching results for author and title in adv. search
by bugzilla-daemon＠bugs.koha-community.org 03 May '24

03 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17763 Bug ID: 17763 Summary: Exact ponctuation and words order is needed for matching results for author and title in adv. search Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: Linux Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: alexandre.breton(a)ccsr.qc.ca QA Contact: testopia(a)bugs.koha-community.org When we use in advanced search, the exact ponctuation ("," and "-") and words order (name, first name) is required to find the good author. Also, when we search by customer, we must put an "-" in the customer name to find the good one. Some people want a more flexible way to find the good author or the good customer in theirs orders. There is a patch or a fix of any kind to do this without ",", "-" and the specific word order ? I searched but find nothing related (maybe I miss something...) Thanks, -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 19763] New: Improve the close budget screen
by bugzilla-daemon＠bugs.koha-community.org 03 May '24

03 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19763 Bug ID: 19763 Summary: Improve the close budget screen 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When closing a budget the message once orders are resolved is: There are no unreceived orders for this budget. Back Perhaps a message that the budget is ready to be closed, or a link to make the budget inactive and locked would be helpful to the user. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 20488] New: Manual renewal due date ignore closed day in calendar
by bugzilla-daemon＠bugs.koha-community.org 03 May '24

03 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20488 Bug ID: 20488 Summary: Manual renewal due date ignore closed day in calendar Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: marjorie.barry-vila(a)collecto.ca QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Hi, When choosing a renewal date manually, calendar is not taken into account. If the chosen day is a closed day, due date will still be positioned on that date. A warning should appear or due date should be on the next open date in the calendar. Regards, Marjorie -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 23366] New: Add html option on subscription additional field
by bugzilla-daemon＠bugs.koha-community.org 03 May '24

03 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23366 Bug ID: 23366 Summary: Add html option on subscription additional field Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: marjorie.barry-vila(a)collecto.ca QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com Created attachment 91765 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=91765&action=ed… additinal_field Hi, It would be nice to be able to add html code on subscription additional field. currently, the html code registered in a field is not fully taken into account when modifying a subscription. Once the <a href ... code is entered, it is no longer possible to modify it. See image attached. Regards Marjorie -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 22188] New: Use publication date as numbering pattern
by bugzilla-daemon＠bugs.koha-community.org 03 May '24

03 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22188 Bug ID: 22188 Summary: Use publication date as numbering pattern Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com Target Milestone: --- Brimbank Libraries Australia would like to be able to use the publication date of a serial as the issue number. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 62

[Bug 36705] New: The 'Add new concern' button for catalog concerns is hidden away
by bugzilla-daemon＠bugs.koha-community.org 03 May '24

03 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36705 Bug ID: 36705 Summary: The 'Add new concern' button for catalog concerns is hidden away Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface 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 The ability to report catalog concerns from the staff client is hidden away under the 'New' button of the record. We could expose a link from the 'Concerns' tab when in focus at the bottom of the page and perhaps make the feature more discoverable by moving/replicating the button outside of the 'New' menu somewhere too? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5