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

[Bug 19361] New: Linking an authorised value category to a field in a framework can lose data
by bugzilla-daemon＠bugs.koha-community.org 28 Jul '23

28 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19361 Bug ID: 19361 Summary: Linking an authorised value category to a field in a framework can lose data Change sponsored?: --- Product: Koha Version: 16.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: liz(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl If you link an authorised value to a framework after you have done data entry on the same field, editing the record with the new authorised value drop down, and not filling it in will lose the data in the field. To reproduce: choose a free entry MARC field and add a record with some data in that field. create an authorised value category and link it to that field in a framework edit your record with the authorised value link now defined, do not select an authorised value from the field, and save it note that the data for that field is now gone. I have only heard this reported on 16.05, but it very well may be in Master. It would pay to check. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 51

[Bug 30430] New: UNIMARC XSLT : displaying field B_214
by bugzilla-daemon＠bugs.koha-community.org 28 Jul '23

28 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30430 Bug ID: 30430 Summary: UNIMARC XSLT : displaying field B_214 Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: fpichenot(a)ville-roubaix.fr QA Contact: testopia(a)bugs.koha-community.org We need to update XSLT files to display new UNIMARC B_214 field. See https://cdn.ifla.org/wp-content/uploads/files/assets/uca/unimarc_updates/BI… -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 37

[Bug 30767] New: Terminology: Do not forget that the issue has not been checked in yet.
by bugzilla-daemon＠bugs.koha-community.org 28 Jul '23

28 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30767 Bug ID: 30767 Summary: Terminology: Do not forget that the issue has not been checked in yet. Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Keywords: Academy Severity: trivial Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Issue should be checkout: koha-tmpl/intranet-tmpl/prog/en/modules/tools/preview_letter.tt:14 Do not forget that the issue has not been checked in yet. -- You are receiving this mail because: You are watching all bug changes.

1 13

[Bug 28362] New: Add 'Preferred language' to self-registration form
by bugzilla-daemon＠bugs.koha-community.org 28 Jul '23

28 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28362 Bug ID: 28362 Summary: Add 'Preferred language' to self-registration form Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: severine.queune(a)bulac.fr QA Contact: testopia(a)bugs.koha-community.org 'Preferred language' for notifications is currently not present on the self-registration form. It could be be great if we could add it to let borrowers choose their language upon registration. -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 30055] New: Rewrite patron searches to make them use the REST API routes
by bugzilla-daemon＠bugs.koha-community.org 28 Jul '23

28 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30055 Bug ID: 30055 Summary: Rewrite patron searches to make them use the REST API routes Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Patrons Assignee: jonathan.druart+koha(a)gmail.com Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com -- You are receiving this mail because: You are watching all bug changes.

1 257

[Bug 17787] New: Suppressed items seems so still be included in number of search results
by bugzilla-daemon＠bugs.koha-community.org 28 Jul '23

28 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17787 Bug ID: 17787 Summary: Suppressed items seems so still be included in number of search results 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: viktor.sarge(a)regionhalland.se QA Contact: testopia(a)bugs.koha-community.org We have a use case where like 99% of the collection is hidden and only a few selected items are displayed in the opac (by showing their covers up front on the main page). When going to the detail page and clicking the link for an author that has a long list of records (but only one visible in the opac) I might get indication of 63 hits in the search results and a the links to pages 1,2,3 etc for search results. Only problem is that there is actually only one result since the rest are suppressed. My guess is that the code calculating the number of hits and creating links to the pages of search results is not talking to the suppression system. I could not find any open bugs about this. Perhaps because our use of suppression is a bit of a edge case(?) I ended up "solving" the problem by removing the links on author etc. since we don't use search anyhow. I'll likely not research the issue further, but I felt I should at least report it and keep an eye out. All input is welcome. -- You are receiving this mail because: You are watching all bug changes.

1 29

[Bug 19192] New: Update default DUEDGST and PREDUEDGST notices
by bugzilla-daemon＠bugs.koha-community.org 26 Jul '23

26 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19192 Bug ID: 19192 Summary: Update default DUEDGST and PREDUEDGST notices Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The current default digest notices are DUEDGST You have <<count>> items due PREDUEDGST You have <<count>> items due soon These are not terribly useful defaults -- the whole reason for having digest notices is to display item detail for items which are due or coming due. I suggest the following instead: DUEDGST Dear <<borrowers.firstname>> <<borrowers.surname>>, You have <<count>> items due: <<items.content>> PREDUEDGST Dear <<borrowers.firstname>> <<borrowers.surname>>, You have <<count>> items due soon: <<items.content>> -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 29248] New: Manual 21.05 - 'position' missing in syspref UNIMARCAuthorityField100
by bugzilla-daemon＠bugs.koha-community.org 26 Jul '23

26 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29248 Bug ID: 29248 Summary: Manual 21.05 - 'position' missing in syspref UNIMARCAuthorityField100 Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: e.betemps(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Hi, Translating syspref in this manual, I think some positions are missing Emplacements : ../../source/authoritiespreferences.rst:189 Asks: Use the following text for the contents of UNIMARC authority field 100 position ??? (fixed length data elements). have a nice day, Manu. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 26228] New: Update gulpfile to work with Node.js v12
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '23

25 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26228 Bug ID: 26228 Summary: Update gulpfile to work with Node.js v12 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Node.js v8 has gone EOL on december 2019. We need to shift the required version to v12, but we rely on old gulp and friends that need to be updated. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 19

[Bug 29489] New: <<branches.branchname>> in RENEWAL notice subject field
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '23

25 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29489 Bug ID: 29489 Summary: <<branches.branchname>> in RENEWAL notice subject field Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: george(a)nekls.org QA Contact: testopia(a)bugs.koha-community.org Using <<branches.branchname>> returns the library name when used in the subject field for a notice template with one apparent exception. If an item is renewed from the OPAC the RENEWAL notice is sent with the subject "<<branches.branchname>>" We are set up so that an item renewal via the OPAC should get recorded statistically as a renewal by the branch the item was checked out at. It would be nice if <<branches.branchname>> filled in the branch name of the library where the item was checked out rather than "branches.branchcode" -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1