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

[Bug 11844] Additional fields for order lines
by bugzilla-daemon＠bugs.koha-community.org 03 Apr '23

03 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11844 Biblibre Sandboxes <sandboxes(a)biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #146504|0 |1 is obsolete| | --- Comment #77 from Biblibre Sandboxes <sandboxes(a)biblibre.com> --- Created attachment 149086 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=149086&action=e… Bug 11844: (follow-up) Add standard note to database update Signed-off-by: Katrin Fischer <katrin.fischer(a)bsz-bw.de> Signed-off-by: Michaela Sieber <michaela.sieber(a)kit.edu> -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 11844] Additional fields for order lines
by bugzilla-daemon＠bugs.koha-community.org 03 Apr '23

03 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11844 Biblibre Sandboxes <sandboxes(a)biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #146503|0 |1 is obsolete| | --- Comment #76 from Biblibre Sandboxes <sandboxes(a)biblibre.com> --- Created attachment 149085 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=149085&action=e… Bug 11844: (follow-up) Fix terminology: biblio should be bibliographic record This is about the note displaying after an additional field that is linked to a MARC field. Signed-off-by: Katrin Fischer <katrin.fischer(a)bsz-bw.de> Signed-off-by: Michaela Sieber <michaela.sieber(a)kit.edu> -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 11844] Additional fields for order lines
by bugzilla-daemon＠bugs.koha-community.org 03 Apr '23

03 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11844 Biblibre Sandboxes <sandboxes(a)biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #146502|0 |1 is obsolete| | --- Comment #75 from Biblibre Sandboxes <sandboxes(a)biblibre.com> --- Created attachment 149084 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=149084&action=e… Bug 11844: [DO NOT PUSH] Schema changes Signed-off-by: Katrin Fischer <katrin.fischer(a)bsz-bw.de> Signed-off-by: Michaela Sieber <michaela.sieber(a)kit.edu> -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 11844] Additional fields for order lines
by bugzilla-daemon＠bugs.koha-community.org 03 Apr '23

03 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11844 Biblibre Sandboxes <sandboxes(a)biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #146501|0 |1 is obsolete| | --- Comment #74 from Biblibre Sandboxes <sandboxes(a)biblibre.com> --- Created attachment 149083 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=149083&action=e… Bug 11844: Fix QA issues (POD, TT filters, file exec flag) Signed-off-by: Katrin Fischer <katrin.fischer(a)bsz-bw.de> Signed-off-by: Michaela Sieber <michaela.sieber(a)kit.edu> -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 11844] Additional fields for order lines
by bugzilla-daemon＠bugs.koha-community.org 03 Apr '23

03 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11844 Biblibre Sandboxes <sandboxes(a)biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #146500|0 |1 is obsolete| | --- Comment #73 from Biblibre Sandboxes <sandboxes(a)biblibre.com> --- Created attachment 149082 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=149082&action=e… Bug 11844: Take into account itemtypes, branches, and cn_source MARC subfields can be linked to "authorised values" that are not real authorised values: itemtypes, branches, and cn_source. Those were not taken into account. This patch fixes that Test plan: 1. Create additional fields for order lines with a MARC subfield that is linked to one of those "fake" authorised values list 2. Follow the same steps as in the main test plan Signed-off-by: Katrin Fischer <katrin.fischer(a)bsz-bw.de> Signed-off-by: Michaela Sieber <michaela.sieber(a)kit.edu> -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 11844] Additional fields for order lines
by bugzilla-daemon＠bugs.koha-community.org 03 Apr '23

03 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11844 Biblibre Sandboxes <sandboxes(a)biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #146497|0 |1 is obsolete| | --- Comment #72 from Biblibre Sandboxes <sandboxes(a)biblibre.com> --- Created attachment 149081 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=149081&action=e… Bug 11844: Use additional fields for order lines This patch allows to create additional fields for order lines. Once created, these fields can be filled during order line creation or modification. If additional field is linked to a MARC field, there are two possible scenario: - MARC field mode = get: The field cannot be modified and its value is retrieved from the bibliographic record (current behaviour) - MARC field mode = set: The field can be modified and its value is saved to the bibliographic record (new behaviour) If additional field is linked to an authorised value category, then authorised values are used. If not directly linked to an authorised value category, but linked to a MARC field, a search for an AV category is made on MARC default framework. This patch doesn't display additional fields value anywhere (except in order line creation/modification). Future patches will do that. Test plan: 1/ Go to Acquisitions home 2/ In the left menu, click on "Add order line fields" 3/ Click on "New field" button 4/ Give the field a name (unique), no AV category and no MARC field. 5/ Save. 6/ Create 5 other fields: a/ no AV category, a MARC field not linked to AV category, MARC field mode = get b/ no AV category, a MARC field not linked to AV category, MARC field mode = set c/ no AV category, a MARC field linked to AV category, MARC field mode = get d/ no AV category, a MARC field linked to AV category, MARC field mode = set e/ an AV category, no MARC field 7/ Create everything you need to be able to create order lines (supplier, basket, ...) 8/ Create an order line. At bottom of the page, you should see your additional fields, with authorised values dropdrown list for fields (c), (d) and (e). Fields (a) and (c) should be disabled. 9/ Fill these fields with some data and save order line 10/ check that data was correctly saved into biblio for fields (b) and (d), but not for (a) and (c) 11/ modify the same order line, check that values you've filled are correctly retrieved and that values for (a) and (c) were correctly retrieved from the bibliographic record 12/ modify all values, save, and check biblio once again Signed-off-by: Harold Dramer <harold.dramer(a)nyls.edu> Signed-off-by: Katrin Fischer <katrin.fischer(a)bsz-bw.de> Signed-off-by: Michaela Sieber <michaela.sieber(a)kit.edu> -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 23616] New: Private repeatable note field needed in Serials Subscription Record
by bugzilla-daemon＠bugs.koha-community.org 01 Apr '23

01 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23616 Bug ID: 23616 Summary: Private repeatable note field needed in Serials Subscription Record Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: niamh.walker-headon(a)it-tallaght.ie QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com It is useful to have a record of emails and dates of correspondence in the note field of a journal record in KOHA serials subscriptions. We want to keep this type of note for staff view only while still having the option of a public note also. Staff need to see at a glance what and when action is taken when a claim is escalated. When a missing journal eventually arrives and is marked arrived?, Currently, the notes in the note field must be deleted, as they will show on the OPAC. So the record of what happened is lost in KOHA serials. It would be useful to have a repeatable private note field as well as the public one. See: Electrical Times: https://librarysearch.it-tallaght.ie//cgi-bin/koha/opac-detail.pl?biblionum… ? On this record, See the note for July 2018. It is far easier to see what is happening when the notes are in KOHA serials than stored elsewhere. Serials - Record: Serials administrators need a repeatable private note field, for administration of the subscription and claiming processes. This field would be attached to the subscription field and would not display on the opac. Serials therefore needs two note fields in subscriptions. One for public display and a separate repeatable one for non-public display only. This change would also mean that we can change the status of an issue to “missing (not received)” and be able to explain this status further, such as “not published” or “combined with December issue” in the public note, while still being able to use the non public note for recording details in relation to correspondence and actions relating to claiming the missing issue. These notes are kept to observe patterns in failure to supply, issues with delivery, non-publication etc., so that staff know who was contacted when regarding issues about issues. Processing of serials claims would be more accurate and efficient. This simple change would allow the serials workflow to stay within the serials module making it more streamlined and efficient.Staff feel that this data does not belong on the marc record. Loss of information re business relationship and contractual efficiency with supplier. We currently use this note field to record any problems/correspondence in relation to subscriptions. It enables us to spot patterns in non-supply. On arrival of an issue we must then delete the notes from this field or they will show to the public. The history of correspondence/problems will now be lost. These notes can be useful for tracking ongoing/previous problems. Having to ensure that notes are deleted before displaying publicly allows for possible human error. As far as I can see, this is not the same issue as bues 11492 and 23416, but related -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 13976] Sorting search results by popularity is alphabetical
by bugzilla-daemon＠bugs.koha-community.org 01 Apr '23

01 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13976 --- Comment #29 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- Really happy to see this one fixed :) -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 13325] Add logs for budgets and funds
by bugzilla-daemon＠bugs.koha-community.org 01 Apr '23

01 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13325 Michaela Sieber <michaela.sieber(a)kit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |michaela.sieber(a)kit.edu -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 23567] New: Printable QR links
by bugzilla-daemon＠bugs.koha-community.org 01 Apr '23

01 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23567 Bug ID: 23567 Summary: Printable QR links Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Label/patron card printing Assignee: cnighswonger(a)foundations.edu Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org Suppose there were a tool that would allow you to process items, much like you would for spine labels, but instead printed custom messages along with a QR code to useful things. For example, you might select a "Comment QR label". You would enter a generic message like "Tell us what you thought of this book." Labels would print for each item with this message, and the QR code beneath, and you would affix this label inside the back of the book. When the patron is done reading the book, they scan the code, and it takes them straight to the comment form in the OPAC (after signing in, if required) for that book, and they can fill out a comment right on their device. Other options, instead of comments, might include rating, tagging, or bragging about the book in a specific social media. For example, they scan the QR code and it would go to Facebook and start a post with a link to the book in the OPAC. -- You are receiving this mail because: You are watching all bug changes.

1 7