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

[Bug 30018] New: Title statment punctuation
by bugzilla-daemon＠bugs.koha-community.org 23 Aug '23

23 Aug '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30018 Bug ID: 30018 Summary: Title statment punctuation Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: paliotti(a)mdp.edu.ar QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Hi, perhaps i don´t understand koha punctuation "rules". The question is: I put leader position 18 to "c" (ISBD without punctuation) because we are cataloguing in RDA without punctuation and this is the correct position for us. 245$a = Title 245$b = subtitle Intranet and Opac interfaces shows me "Title(space)subtitle" when the expected view must be "Title : subtitle". Is there any parameter or way for a correct fields format? Thks -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 32723] New: chopPunctuation in xslt issues
by bugzilla-daemon＠bugs.koha-community.org 23 Aug '23

23 Aug '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32723 Bug ID: 32723 Summary: chopPunctuation in xslt issues Change sponsored?: --- Product: Koha Version: 21.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: bernard.scaife(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Create catalogue record Enter an author (100a) as: Scaife, B. M. Save View in OPAC or intranet full detail record chopPunctuation will present it in the full detail of the OPAC and staff client as Scaife, B. M should be Scaife, B. M. Can this be fixed in such cases and if not, can there be a system preference to allow the user to switch off chopPunctuation altogether? It breaks compatibility with RDA cataloguing according to a customer. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 23928] New: Move saved reports JavaScript into separate file
by bugzilla-daemon＠bugs.koha-community.org 23 Aug '23

23 Aug '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23928 Bug ID: 23928 Summary: Move saved reports JavaScript into separate file Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: testopia(a)bugs.koha-community.org Coding guideline JS1 (https://wiki.koha-community.org/wiki/Coding_Guidelines#JS1:_Embedding_JavaS…) says "Whenever possible JavaScript should be placed in a separate file." I propose to move most of the JS embedded in reports/guided_reports_start.tt to a separate file. -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 31867] New: Add note to DefaultPatronSearchFields that searchable patron attributes are always included
by bugzilla-daemon＠bugs.koha-community.org 22 Aug '23

22 Aug '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31867 Bug ID: 31867 Summary: Add note to DefaultPatronSearchFields that searchable patron attributes are always included Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Keywords: Academy Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com There was some confusion recently about what 'searchable' meant for patron attributes. I think it would help if we added a note to the DefaultPatronSearchFields system preference description. Patron attributes marked searchable can always be searched for within the "Standard" search option. See also test plan on bug 30576 for reference. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 18940] New: Generate new account emails when importing patrons via tools
by bugzilla-daemon＠bugs.koha-community.org 21 Aug '23

21 Aug '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18940 Bug ID: 18940 Summary: Generate new account emails when importing patrons via tools 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Some institutions would like the ability to send account emails in bulk when importing new patrons (e.g. A school adding new patrons at the start of each term) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 29005] New: Add support for AutoEmailUser similar to AutoEmailOpacUser to patron imports
by bugzilla-daemon＠bugs.koha-community.org 21 Aug '23

21 Aug '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29005 Bug ID: 29005 Summary: Add support for AutoEmailUser similar to AutoEmailOpacUser to patron imports 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com It would be helpful to add automatic email to users on patron imports. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 46

[Bug 28499] New: Add support for no-UI / administrative plugins
by bugzilla-daemon＠bugs.koha-community.org 21 Aug '23

21 Aug '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28499 Bug ID: 28499 Summary: Add support for no-UI / administrative plugins Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Plugin architecture Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org It would be helpful for support to have the ability to add plugins that configure/affect the syste, but are not accessible by the users (cannot be removed, edited, etc) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 33755] New: Profile used is not saved when importing records
by bugzilla-daemon＠bugs.koha-community.org 18 Aug '23

18 Aug '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33755 Bug ID: 33755 Summary: Profile used is not saved when importing records Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisette.scheer(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Before 22.11 if you selected a profile when staging marc records for import, when you went to see staged records it would show which profile was used both in the table and in the batch details. Post 22.11, if you select a profile, it saves the selections but doesn't save which profile was used. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 33140] New: Use facet label value in mouseover title attribute of facet removal link
by bugzilla-daemon＠bugs.koha-community.org 18 Aug '23

18 Aug '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33140 Bug ID: 33140 Summary: Use facet label value in mouseover title attribute of facet removal link Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: andreas.jonsson(a)kreablo.se QA Contact: testopia(a)bugs.koha-community.org The mouseover text for the remove link displays the link value of the facet rather than its label. (In koha-tmpl/intranet-tmpl/prog/en/includes/facets.inc and koha-tmpl/opac-tmpl/bootstrap/en/includes/opac-facets.inc b/koha-tmpl/opac-tmpl/bootstrap/en/includes/opac-facets.inc). Logically, it is always the label value that should be displayed to the user so this should also be used for the title attribute. For instance for a custom boolean valued facet one do not want to see the text "remove the facet true" when hovering on the link. (See bug 33139.) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 31667] New: Merge 'tip' and 'hint' classes
by bugzilla-daemon＠bugs.koha-community.org 18 Aug '23

18 Aug '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31667 Bug ID: 31667 Summary: Merge 'tip' and 'hint' classes Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org 'tip' and 'hint' are classes for a CSS with grey color. Looks like 'hint' is way more used that 'tip' (mainly used for header search boxes). I think we should replace 'tip' with 'hint' to have only one class for this usage. And maybe add a coding guide line. -- You are receiving this mail because: You are watching all bug changes.

1 19