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

[Bug 17314] New: REST API: Add API route to create, list and delete a purchase suggestion
by bugzilla-daemon＠bugs.koha-community.org 11 Nov '21

11 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17314 Bug ID: 17314 Summary: REST API: Add API route to create, list and delete a purchase suggestion Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: mail(a)jkozlovsky.cz QA Contact: testopia(a)bugs.koha-community.org It would be nice to have an API for creating a purchase suggestion. It would be used for instance in VuFind. Proposed implementation: To create: POST /suggestions/{borrowernumber} Incoming data: { title (required) author copyrightdate isbn publishercode collectiontitle place itemtype patronreason note negcap } Outcoming data: 200 OK / 403 Forbidden / 409 Conflict (when already exists the proposal) { error status } To list: GET /suggestions/{borrowernumber} Outcoming data: list of suggestions To delete: DELETE /suggestions/{borrowernumber}/{suggestion_id} Outcoming data: 204 No Content (successful deletion) / 403 Forbidden / 404 Not Found -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 135

[Bug 16467] New: Discharge requests pending count should appear on patrons home page
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '21

10 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16467 Bug ID: 16467 Summary: Discharge requests pending count should appear on patrons home page 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: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Currently the "Discharge requests pending" count appears only on the staff client home page. Like the count of patrons requesting modification, the discharge request count should also appear on the patrons home page (members-home.pl). -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 20310] New: Article requests: Can we redirect article records without items to host record?
by bugzilla-daemon＠bugs.koha-community.org 09 Nov '21

09 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20310 Bug ID: 20310 Summary: Article requests: Can we redirect article records without items to host record? 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: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org If I have a biblio record (without items) for article XXX in serial Y and I included a MARC21 773 host record that includes title, page info and host record number, it would be very helpful if the OPAC form would redirect me to the serial Y host record and I could select the correct item over there. (Can we prefill the page info or even preselect the item?) Probably we should assume here that the ART records have the 'Record only' rule and the SER records have 'Item only' rule, and the record number is referring to the local catalogue (check the marc org code?). -- You are receiving this mail because: You are watching all bug changes.

1 95

[Bug 20168] New: update to bootstrap v4
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '21

02 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20168 Bug ID: 20168 Summary: update to bootstrap v4 Change sponsored?: --- Product: Koha Version: 17.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: elias.dehler(a)thulb.uni-jena.de QA Contact: testopia(a)bugs.koha-community.org I'm currently working on updating the bootstrap template to bootstrap v4. This requires to update jQuery as well. My work is based on the current 17.11.02 koha release. I'm trying to keep the design as close to the current design as possible. At the moment i have nothing to show of my current process but as soon as everything plays nice i will post a link to my repository. The goal is to get a template based on the current version of bootstrap. -- You are receiving this mail because: You are watching all bug changes.

1 78

[Bug 19206] New: How should we sort 19xx when order is pubdate?
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '21

02 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19206 Bug ID: 19206 Summary: How should we sort 19xx when order is pubdate? 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: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org On bug 11046 I proposed to sort e.g. 19xx with 1900. This relates to the kohafield copyrightdate used to sort lists and in reports. For search results, the sort on publication date depends on pubdate as indexed by Zebra. If we add uncertain years like 19xx or better 19uu in the MARC21 008, they will be sorted after 1999 (current situation). We could add a "fix_008" in rebuild_zebra (just as a few other fixes already there) and replace 19uu by 1900 when indexing in order to get 19xx sorted with 1900. What do you think ? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 19297] New: Standardize "can place hold" calculations
by bugzilla-daemon＠bugs.koha-community.org 29 Oct '21

29 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19297 Bug ID: 19297 Summary: Standardize "can place hold" calculations Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org There are several places where we need to know if a hold can be placed on a bibliographic record, or an item. And we also have several way of calculate it... Sometimes it is buggy, sometimes we calculate the information for nothing, sometimes it is done correctly. We need to make this calculation uniform in order to be consistent and always display the same and correct information everywhere. -- You are receiving this mail because: You are watching all bug changes.

1 10

[Bug 19821] New: Run tests on a separate database
by bugzilla-daemon＠bugs.koha-community.org 29 Oct '21

29 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19821 Bug ID: 19821 Summary: Run tests on a separate database Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Test Suite Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Running the tests on the same database as the one used for dev has some drawbacks: - Everybody has different data, so we cannot make any assumptions about data in tests and it can make tests fail for non-obvious reasons. - Tests have to clean up every change to the database using SQL transactions, so we cannot write testable code that use transactions (AFAIK) - Transactions in tests happen to be committed sometimes, resulting in garbage data added to the dev database I'll send a patch that allows to run tests in a separate database in order to address these issues. -- You are receiving this mail because: You are watching all bug changes.

1 106

[Bug 20277] New: Link to host item doesn't work in analytical records if 773$a is present
by bugzilla-daemon＠bugs.koha-community.org 26 Oct '21

26 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20277 Bug ID: 20277 Summary: Link to host item doesn't work in analytical records if 773$a is present Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: verolencinas(a)yahoo.com.ar QA Contact: testopia(a)bugs.koha-community.org A lot of analytical records are made for serials. And for most of them the title is their primary access point. The OPAC and intranet link in the analytical record to the host item works well in these cases. But if you have a 1XX field in your host item, this information goes in your 773$a subfield but the OPAC and intranet link in the analytical record to the host item includes 773$a and 773$t data but searches only in the title index. In this situation you can't retrieve the host item record. Test: - Create an analytical record for a (host)record with a 1XX field. - Use the link in the analytical ("In" note) to retrieve the host record in the intranet client and the OPAC. -- You are receiving this mail because: You are watching all bug changes.

1 19

[Bug 16446] New: Allow librarians to add borrowers to lists by borrowernumber or cardnumber
by bugzilla-daemon＠bugs.koha-community.org 22 Oct '21

22 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16446 Bug ID: 16446 Summary: Allow librarians to add borrowers to lists by borrowernumber or cardnumber Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Lists Assignee: gmcharlt(a)gmail.com Reporter: liz(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl It would be nice to be able to add borrowers to lists based on a supplied list of cardnumbers or borrowernumbers (that they could get from a report, for example). -- You are receiving this mail because: You are watching all bug changes.

1 19

[Bug 18501] New: Automatic refunds need protection from failure
by bugzilla-daemon＠bugs.koha-community.org 19 Oct '21

19 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18501 Bug ID: 18501 Summary: Automatic refunds need protection from failure Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com I am told that the auto refund feature can fail if the status is edited in the item edit screen. There should be some protection in place to keep this from failing so easily and quietly. Possible solutions might be: 1) Prevent status from being edited if a fee has been charged for that item. 2) A warning and confirmation of action when the status is being edited and there is a fee involved. 3) An authorized override for such a change. 4) A note in the patron account lines indicating status was change and an auto refund will not be possible. 5) The ability to auto refund, even after the status has been altered. I am marking this as a bug, because I cannot see how the current behavior could be a desired function. Failure is not an option. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 138