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

[Bug 30536] New: Embeds should be defined in a single place
by bugzilla-daemon＠bugs.koha-community.org 09 Feb '23

09 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30536 Bug ID: 30536 Summary: Embeds should be defined in a single place 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: tomascohen(a)gmail.com CC: tomascohen(a)gmail.com Right now, our specs need two places: (1) path top level x-koha-embed entry (2) path header parameters definition for x-koha-embed as an enum The first one was the right one in the first place, but JSON::Validator didn't manage that correctly (reliably I'd say). So we used it as in (1). Bug 29810 added (2), which is great and correct, but our 'stash_embed' helper [1] called from Koha/REST/V1/Auth.pm is relying on (1) to build the allow-list for embeds. So we need to have both, and we should fix it. [1] Koha/REST/Plugin/Query.pm:237 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 55

[Bug 32902] New: Add ability to choose if items overlay if any record matches or only if the item is on the matched record
by bugzilla-daemon＠bugs.koha-community.org 08 Feb '23

08 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32902 Bug ID: 32902 Summary: Add ability to choose if items overlay if any record matches or only if the item is on the matched record 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Bug 32804 resolves an bug where an overlaid item could have its' biblionumber changed. Fixing this has the effect of enabling items to be updated even if the item is on a different record. This can be wanted or unwanted behavior depending on the situation. It would be good if the cataloger could choose which behavior is preferred on a per-batch bases. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 31669] New: Improve support for "cost" field
by bugzilla-daemon＠bugs.koha-community.org 08 Feb '23

08 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31669 Bug ID: 31669 Summary: Improve support for "cost" field Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew.isherwood(a)ptfs-europe.com An ILL request has a "cost" field associated with it. This is intended to be used to indicate the cost of a request as quoted by a supplier. Support for actually using this field is somewhat lacking. The current use is: - The BLDSS backend populates it upon request placement, the value is derived from the BLDSS request response - The "Edit request" screen displays the value, or N/A if not populated. This value is read-only and cannot be modified. What needs to be done: - Other ILL backends should add support for populating the "cost" field during request placement - Modify the "Edit request" template to allow the value to be modified. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 32544] New: borrowers.flags should not be an option in any BorrowerMandatory or BorrowerUnwanted sysprefs
by bugzilla-daemon＠bugs.koha-community.org 08 Feb '23

08 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32544 Bug ID: 32544 Summary: borrowers.flags should not be an option in any BorrowerMandatory or BorrowerUnwanted sysprefs Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrewfh(a)dubcolib.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Depends on: 32535 Borrowers.flags should not be an option in the following syspref menus: PatronSelfModificationMandatoryField, PatronSelfRegistrationBorrowerMandatoryField, BorrowerMandatoryField, PatronSelfModificationBorrowerUnwantedField, PatronSelfRegistrationBorrowerUnwantedField Because permissions aren't actually set via the borrower edit screens, these checkboxes have no real purpose or effect. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32535 [Bug 32535] BorrowerUnwatedField syspref should not include borrowers.flags -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 11

[Bug 32580] New: Background job cancel button broken, leads to bakcground_jobs.pl with a kc
by bugzilla-daemon＠bugs.koha-community.org 08 Feb '23

08 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32580 Bug ID: 32580 Summary: Background job cancel button broken, leads to bakcground_jobs.pl with a kc Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Keywords: regression Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: phil(a)chetcolibrary.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 30982 Regression from bug 30982 which typoed background_jobs.pl as bakcground_jobs.pl - if you try to cancel a background job, you get a 404 error. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30982 [Bug 30982] Use the REST API for background job list view -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 32226] New: Capitalization: Edit html content
by bugzilla-daemon＠bugs.koha-community.org 08 Feb '23

08 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32226 Bug ID: 32226 Summary: Capitalization: Edit html content Change sponsored?: --- Product: Koha Version: master 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 HTML is an abbreviation and should be capitalized: Edit html content koha-tmpl/intranet-tmpl/prog/en/modules/admin/branches.tt:259 -- You are receiving this mail because: You are watching all bug changes.

1 11

[Bug 32027] New: Terminology: change "librarian interface" to "staff interface" in additional contents tool
by bugzilla-daemon＠bugs.koha-community.org 08 Feb '23

08 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32027 Bug ID: 32027 Summary: Terminology: change "librarian interface" to "staff interface" in additional contents tool 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: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com According to the terminology list (https://wiki.koha-community.org/wiki/Terminology#S) "staff interface" is the preferred term to designate the staff interface. In a couple of places in the additional contents tool, "librarian interface" is used. 1. Go to Tools > News 2. Click "New entry" --> In the "Display location" drop-down menu, there is "Librarian and OPAC interfaces" and "Librarian interface" as choices 3. Create a news item with the display location set to "Librarian interface" and save --> In the table of all the news, "Librarian interface" is displayed as the location 4. Go to Tools > Pages 5. Click "New entry" --> In the "Display location" drop-down menu, there is "Librarian and OPAC interfaces" and "Librarian interface" as choices 6. Create a page with the display location set to "Librarian interface" and save --> In the table of all the pages, "Librarian interface" is displayed as the location --> "Librarian interface" is also displayed in the "Page URL" column -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 12

[Bug 31860] New: 952$h - Serial enumeration / chronology: use sentence case for label
by bugzilla-daemon＠bugs.koha-community.org 08 Feb '23

08 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31860 Bug ID: 31860 Summary: 952$h - Serial enumeration / chronology: use sentence case for label Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: MARC Bibliographic data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org The label for Serial enumeration / chronology (952$h) is displayed as "Serial Enumeration / chronology" - note the capital "E". For consistency, this should be displayed in sentence case wherever it is required in the staff interface and OPAC, including: - details view in the staff interface: MARC view, edit items table, add and edit item form - MARC view in the OPAC: holdings table Note: Libraries can update this themselves by updating $952$h for all the frameworks it is used in. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 24121] New: Item types icons not showing in intra search results if item-level_itypes syspref is set to biblio
by bugzilla-daemon＠bugs.koha-community.org 08 Feb '23

08 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24121 Bug ID: 24121 Summary: Item types icons not showing in intra search results if item-level_itypes syspref is set to biblio Change sponsored?: --- Product: Koha Version: 19.05 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: pjamorim91(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 27

[Bug 32907] New: Add a field for personal ID
by bugzilla-daemon＠bugs.koha-community.org 08 Feb '23

08 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32907 Bug ID: 32907 Summary: Add a field for personal ID 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: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com I know storing social security numbers are a big no-no in some countries, but in others it is perfectly fine and legal. At least libraries in Norway and Sweden expect an ILS to store and handle these numbers. They are not considered "top secret", but are used "everywhere" to identify people. In these countries it looks like a strange omission that "personal IDs" are not handled properly by the system, but have to be shoe-horned in as an extended patron attribute. This also makes it harder than necessary to write reports, sync data from external sources etc. I propose that we - add a database column like borrowers.personalid - add a syspref called something like UsePersonalID - set UsePersonalID to false as the default - make all display and handling of personalid dependent on UsePersonalID This way handling personal IDs will be opt-in only, and something that can be a choice for libraries that want/need to use it. Personal IDs could not only be social security numbers either, in an academic library it could be used for e.g. ORCIDs: https://orcid.org/ A further enhancement to this would be to use personalid for logins, as a third alternative to cardnumber and userid. This could also be governed by a syspref. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1