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

[Bug 34950] New: ILS DI Availability is not accurate for items on holds shelf or in transit
by bugzilla-daemon＠bugs.koha-community.org 02 Feb '24

02 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34950 Bug ID: 34950 Summary: ILS DI Availability is not accurate for items on holds shelf or in transit Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: blawlor(a)clamsnet.org QA Contact: testopia(a)bugs.koha-community.org The ILS DI web service is a handy way for a third party system, such as a mobile app, to check for the availability of items for a given bib record in your system. If you make a call like https://{OPAC_DOMAIN}/cgi-bin/koha/ilsdi.pl?service=GetAvailability&id={BIB_ID}&id_type=bib the response shows the availabilitystatus of items that are on the holds shelf or in transit as 'available'. While these items may be technically available to be checked out, it's not ideal to send the message to patrons that these items are available because they may show up at the library to get the book and be disappointed :( It would be more accurate and informative if ILS DI could show availabilitystatus 'not available' with availabilitymsg indicating 'on hold shelf' or 'in transit' for these items. Alternatively it would be nice to have a REST API endpoint for item availability to easily get this info to third party developers. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 21

[Bug 25691] New: Debian packages point to /usr/share/doc/koha/README.Debian which does not exist
by bugzilla-daemon＠bugs.koha-community.org 02 Feb '24

02 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25691 Bug ID: 25691 Summary: Debian packages point to /usr/share/doc/koha/README.Debian which does not exist Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Packaging Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org CC: mirko(a)abunchofthings.net debian/changelog: * Add notes about README.Debian to package description and postinst output. debian/control: Please see /usr/share/doc/koha/README.Debian for instructions on how to debian/control.in: Please see /usr/share/doc/koha/README.Debian for instructions on how to debian/koha.postinst:Please see /usr/share/doc/koha/README.Debian for instructions on how to -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 19

[Bug 27298] New: Adjusting a Numbering Pattern will not show in receiving next issue
by bugzilla-daemon＠bugs.koha-community.org 01 Feb '24

01 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27298 Bug ID: 27298 Summary: Adjusting a Numbering Pattern will not show in receiving next issue 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: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com Publishers will sometimes change how their serials are numbered mid-year or a library may have their prediction pattern originally set up correctly, for whatever the reason, if a library edits an existing serial's prediction numbering pattern-the first expected issue after this change does not show the revised prediction. Steps: 1. Have a serial in which there is a numbering pattern and an issue has been received. For example, monthly magazine Vol. 25, No 3 2. Edit this existing subscription and alter the numbering pattern- to Vol 31 No.1. 3. Test this subscription and see Koha is accurately predicting the new numbering pattern of Vol 31 No. 1, Vol 31 No 2 etc. 4. Save subscription. 5. Attempt to receive that new issue, Vol 31, No.1 - see that Koha believes it is still receiving Vol 25, No 3. 6. Receive this issue, alter the enumeration for this issue. 7. Receive the next issue, and see Koha is successfully predicting the next issue Vol 31 No 2. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 25047] New: Tutorial for OPAC
by bugzilla-daemon＠bugs.koha-community.org 01 Feb '24

01 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25047 Bug ID: 25047 Summary: Tutorial for OPAC 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: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org Has anyone considered working on a guided tutorial through the OPAC for new users? I'm talking about the OPAC guiding a new user through the different things they can do, with balloons that point out different things. At any point it could be skipped, or restarted. It would be great if there were an admin option panel for what pieces of the tutorial, and in what order, they would like patrons guided through (in case there are some elements that the library don't use). And it would be great if each section of the tutorial could be linked, so if someone asked about how to do something, we could like them to the specific tutorial for what they are asking about. I also see the possibility of being able to customize the tutorials (the balloons), or adding others. IF libraries could create a new tutorial, and tell each balloon what to point at and what to say, that would be great. It probably means that it should give a list of available element IDs for each page that the balloon could point to. Something like that. The tutorials could also track if they have ever been played on that browser (probably through a cookie) and if a new tutorial is added that a user hasn't seen, they can be given the option to go through it or skip it. This system could also be used for for information, similar to news, but for a specific section. For example, during the COVID-19 library closures, we could have used one of these balloons on the hold page to indicate that we are accepting hold requests, but holds are not being filled at this time. -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 32752] New: Add new serial issue status: "At bindery", "Bound",
by bugzilla-daemon＠bugs.koha-community.org 01 Feb '24

01 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32752 Bug ID: 32752 Summary: Add new serial issue status: "At bindery", "Bound", 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: michaela.sieber(a)kit.edu Some libraries don't create items for their serial subscription issues or only create items for their bound volumes of serial issues. For these libraries, but also others, it would be really nice if the list of available serial issue status could be extend to cover some other common use cases: * At bindery: the issue is temporarily not available because it's at the bookbinder's for treatment, usually getting bound into a volume with other issues. * Bound: this would be when the issues have been bound and can now be checked out as a volume together with other issues of i.e. the same year * Circulating: this would be during the time the issue is circulating through the routing list. A lot of library print the routing list and attach it to the issue, then the item is given from one person to the next person on the list, ususally within the library or institution. Open for better suggestions regarding status names :) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 45

[Bug 30728] New: Allow real-time holds queue opt-out
by bugzilla-daemon＠bugs.koha-community.org 01 Feb '24

01 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30728 Bug ID: 30728 Summary: Allow real-time holds queue opt-out Change sponsored?: --- Product: Koha Version: unspecified 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: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Somehow, the patchset got an initially developed piece that made it optional lost. Probably my fault on some submission. We need to add that back. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 36

[Bug 17755] New: Move C4::Members::AttributeTypes to Koha::* namespace
by bugzilla-daemon＠bugs.koha-community.org 31 Jan '24

31 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17755 Bug ID: 17755 Summary: Move C4::Members::AttributeTypes to Koha::* namespace Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 53

[Bug 23272] New: Koha::AuthorisedValue should use Koha::Object::Limit::Library
by bugzilla-daemon＠bugs.koha-community.org 31 Jan '24

31 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23272 Bug ID: 23272 Summary: Koha::AuthorisedValue should use Koha::Object::Limit::Library 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: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Koha::Patron::Attribute::Type should be used as example. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 30

[Bug 28366] New: Add batch patron modification to patron search results
by bugzilla-daemon＠bugs.koha-community.org 31 Jan '24

31 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28366 Bug ID: 28366 Summary: Add batch patron modification to patron search results Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com I think it would be useful to be able to pass checked patron search results to batch patron modification without going through the step of adding them to a list. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 18

[Bug 31969] New: Options for cleanup_database.pl to remove finished jobs from the background job queue
by bugzilla-daemon＠bugs.koha-community.org 30 Jan '24

30 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31969 Bug ID: 31969 Summary: Options for cleanup_database.pl to remove finished jobs from the background job queue Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: bjorn.nylen(a)ub.lu.se QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The background jobs queue will need purging of finished jobs. Bug 31629 focuses on the elastic indexing jobs but the table will fill up with other types of jobs -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 38