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

[Bug 25962] New: In Advanced Editor mandatory subfields are not enforced if tag is not mandatory
by bugzilla-daemon＠bugs.koha-community.org 10 Oct '24

10 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25962 Bug ID: 25962 Summary: In Advanced Editor mandatory subfields are not enforced if tag is not mandatory Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl To recreate: - set your framework so the 100$a is mandatory but the 100 as a whole is not - open a new record in the advanced editor - save the record without a 100$a - edit framework to make the 100 mandatory as well as the 100$a - open a new record - try to save without a 100$a, get an error It doesn't break anything to have to mark the tag required as well as the subfield, but it's more work and it's confusingly different from how we enforce these in the regular editor. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 25246] New: Add script to export bib data to EBSCO EDS
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '24

08 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25246 Bug ID: 25246 Summary: Add script to export bib data to EBSCO EDS Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: david.roberts(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org We (PTFS-Europe) have been using this script to export catalogue data to EBSCO EDS for many of our customers for a long time now, and it would be very useful if it could be incorporated into the core code. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 25

[Bug 19768] New: Possibility to chose "Note" tab in OpacSerialDefaultTab
by bugzilla-daemon＠bugs.koha-community.org 03 Oct '24

03 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19768 Bug ID: 19768 Summary: Possibility to chose "Note" tab in OpacSerialDefaultTab Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Lists Assignee: koha-bugs(a)lists.koha-community.org Reporter: patrick.robitaille(a)collecto.ca QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Hi, It would be interesting to have the possib=ility to chose the note tab for the systeme preference OpacSerialDefaultTab. At the moment, we can only select subscriptions tab, holdings tab and serial collections tab in this preference. It would be nice to have the possibiliy to chose an another tab like notes tab. Patrick. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 25

[Bug 25812] New: Display overdue fines for the document on SIP checkin
by bugzilla-daemon＠bugs.koha-community.org 03 Oct '24

03 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25812 Bug ID: 25812 Summary: Display overdue fines for the document on SIP checkin Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: matthias.meusburger(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com Display overdue fines for the document on SIP checkin Test plan: - Using SIP, checkin an item that has one or several overdue fines. - Check that the following message is displayed (AF field): "You owe {correctly formatted price} for this document." -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 26

[Bug 16881] New: Apply KohaTable and ColVis plugin on MARCdetail' s items table
by bugzilla-daemon＠bugs.koha-community.org 02 Oct '24

02 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16881 Bug ID: 16881 Summary: Apply KohaTable and ColVis plugin on MARCdetail's items table Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: alex.arnaud(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Allows to choose columns to display on items table in the MARCdetail page (cgi-bin/koha/catalogue/MARCdetail.pl). Also, the columns displayed are saved for each users in database. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 30

[Bug 19590] New: doc of Clean Patron Records tool wrong about deletion scope + anonymization syspref
by bugzilla-daemon＠bugs.koha-community.org 01 Oct '24

01 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19590 Bug ID: 19590 Summary: doc of Clean Patron Records tool wrong about deletion scope + anonymization syspref Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: victor.grousset(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Hi, I think I've found a documentation issue in the "Clean Patron Records" tool. Both the in-app + online doc [1] mention that: «patrons with outstanding fines or items checked out not saved» (the rest of the doc confirms that we are talking about removal) → wrong, see [2][3] «The anonymization will fail quietly if AnonymousPatron preference does not contain a valid value.» → wrong, according to the UI itself «The AnonymousPatron system preference is not defined. You can use this feature anyway but NULL will be used to update the checkout history.» Are these two findings correct? [1] https://koha-community.org/manual/17.05/html/03_tools.html#patrons-anonymiz… [2] excludes patrons with checked out item https://github.com/Koha-Community/Koha/blob/master/C4/Members.pm#L1040 [3] excludes patrons with unpaid fines https://github.com/Koha-Community/Koha/blob/master/tools/cleanborrowers.pl#… -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 17330] New: Initiate batch item edit of items from cart (new feature? )
by bugzilla-daemon＠bugs.koha-community.org 01 Oct '24

01 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17330 Bug ID: 17330 Summary: Initiate batch item edit of items from cart (new feature?) 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: viktor.sarge(a)regionhalland.se QA Contact: testopia(a)bugs.koha-community.org On 16.05.03 I can initiate batch record edit from the cart, but not items edit. I realize that it's the records that are saved and not items, but /cgi-bin/koha/tools/batchMod.pl already have a checkbox for choosing which items to modify. How about showing all items for all the records chosen and you could just chose which ones to work with? I do feel that there is a possibility of people messing things up from not thinking about the difference between the saved records and the items for that record that might live in different locations. But when someone puked on a whole shelf it's a quick way to search all records on a particular shelf and marking the items as damaged. What say ye? (To be really helpful it would be good if you could check/uncheck all items based on for example location etc. of course) -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 16898] New: Show patron restriction details on OPAC user page
by bugzilla-daemon＠bugs.koha-community.org 01 Oct '24

01 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16898 Bug ID: 16898 Summary: Show patron restriction details on OPAC user page 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: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org Right now if you have multiple restrictions on your account, the details of those restrictions are all string together in the message which displays in the OPAC. We should display details for each separate restriction. -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 26716] New: Allow specifying where to insert new fields in MARC Modification Templates
by bugzilla-daemon＠bugs.koha-community.org 27 Sep '24

27 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26716 Bug ID: 26716 Summary: Allow specifying where to insert new fields in MARC Modification Templates 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: phil(a)chetcolibrary.org QA Contact: testopia(a)bugs.koha-community.org Currently newly-added fields are stuffed at the end of the record, after 999. Bug 24480 is changing that to insert them in numerical order. However, as the methods on MARC::Record illustrate, there are two other ways that people want to insert fields: grouped by hundreds, so that instead of adding a new 502 after any existing 502s you add it after every existing 5xx field, or, before or after a specific other field. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 25905] New: REST API: create endpoint for importing OAI-PMH records from external OAI-PMH clients
by bugzilla-daemon＠bugs.koha-community.org 26 Sep '24

26 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25905 Bug ID: 25905 Summary: REST API: create endpoint for importing OAI-PMH records from external OAI-PMH clients Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au Following on from previous work on #10662 and koha-plugin-oaipmh-import, I'm now thinking that it would be best to have a REST API endpoint for importing OAI-PMH records in the Koha mainstream. This would give libraries assurance that the core OAI-PMH ingest functionality will be in the main codebase and get Koha community support. For now, I'm still planning to keep my planned OAI-PMH harvester/client as a plugin/third-party dependency, but completion of this work will allow Koha libraries to use any OAI-PMH harvester they choose to ingest records into Koha. This could be with a Perl cronjob using HTTP::OAI, or it could be a Golang daemon, or whatever. Lots of possibilities. Anyway, I've got a lot of this work done already in koha-plugin-oaipmh-import, so I'll look at re-organising it to fit into Koha proper. It'll be in my own time, so I don't have a timeline for it, but it is on my TODO list. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 23