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

[Bug 9762] Log circulation overrides
by bugzilla-daemon＠bugs.koha-community.org 08 Apr '24

08 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9762 Matthias Le Gac <matthias.le-gac(a)inlibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #164068|0 |1 is obsolete| | --- Comment #23 from Matthias Le Gac <matthias.le-gac(a)inlibro.com> --- Created attachment 164508 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=164508&action=e… Bug 9762: Log circulation overrides This patch allows you to save commands that have been overridden by someone. The patch has been updated but is not yet completed. Tests 10, 13, 14, and 17 are still not functional. Tests 15 and 16 need to be fixed as they do not display the barcode. All other tests should be functional. To test: --After each step, a message will be displayed in the action_logs table and in Tools > Log viewer -- Circulation -- Checking out 1) Check out an item that is age-restricted (AgeRestrictionOverride syspref) 2) Check out an item that has a “not for loan” status (AllowNotForLoanOverride syspref) 3) Check out an item that has a “lost” status (IssueLostItem syspref) 4) Check out an item to a patron who has reached the checkout limit (AllowTooManyOverride syspref) 5) Check out an item to a patron who is not allowed to borrow this item type 6) Check out an item to a patron who has unpaid fines (AllFinesNeedOverride and/or AllowFineOverride + noissuescharge sysprefs) 7) Check out an item on hold for someone else 8) Check out an item on hold ready for pickup by someone else 9) Check out an item already checked out to someone else (AutoReturnCheckedOutItems syspref) 10) Check out to a patron who has restrictions Circulation -- Checking in 11) Ignore a hold upon check in 12) Ignore a hold and transfer upon check in Circulation – Renewing 13) Renew an item on hold for someone else (AllowRenewalOnHoldOverride syspref) 14) Renew an item that has reached the maximum number of renewals (AllowRenewalLimitOverride syspref) Holds 15) Place a hold for a patron who is not allowed to place this item type on hold (AllowHoldPolicyOverride syspref) 16) Place a hold for a patron who has reached the maximum number of holds 17) Place an item-level hold when rules dictate that this is not allowed (In circulation rules put "On shelf holds allowed" to "If any unavailable") Current status: Needs Signoff -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 23668] New: Information on syntax for patron attributes
by bugzilla-daemon＠bugs.koha-community.org 08 Apr '24

08 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23668 Bug ID: 23668 Summary: Information on syntax for patron attributes Change sponsored?: --- Product: Koha Version: 19.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: anke.bruns(a)gwdg.de QA Contact: testopia(a)bugs.koha-community.org In the manual at https://koha-community.org/manual//19.05/en/html/tools.html#patron-import-l… the syntax for multiple patron attributes which, to complicate things, consist of multiple words separated by blanks isn't described correctly. It says: <citation> "Note If loading patron attributes, the ‘patron_attributes’ field should contain a comma-separated list of attribute types and values. The attribute type code and a colon should precede each value. For example: “INSTID:12345,BASEBALL:Cubs” This field must be wrapped in quotes if multiple values are defined. Since values can contain spaces, additional doubled-quotes may be required: “INSTID:12345,BASEBALL:Cubs,””BASEBALL:White Sox”” " </citation> After trying this, and all other possible combinations of attributes and quotes I could come up with, I found that import only works if the attributes are entered in the most simple way, namely in single quotes. The blanks can be which, for the above example, would read: “INSTID:12345,BASEBALL:Cubs,BASEBALL:White Sox” I didn't test exactly this combination of attributes, but with similar ones it worked. If this can be confirmed, maybe the manual can be updated accordingly? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 10

[Bug 36544] New: Add option to choose a delimiter for patron import
by bugzilla-daemon＠bugs.koha-community.org 08 Apr '24

08 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36544 Bug ID: 36544 Summary: Add option to choose a delimiter for patron import 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: philip.orr(a)lmscloud.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com By default the patron import tool (accessed by going to Tools -> Import Patrons) uses commas to separate fields. This is fine in most cases, but there is one problem: If you have patron attributes enabled and are importing patrons with values in the patron attribute fields, it could happen that the value of a patron attribute field to be imported contains a comma. For instance, your patron attribute field could be "Names of family members" and the value could be "John Doe, Jane Doe". In that case the attribute will not be imported correctly due to the comma and the patron import could also fail. In this case it would be good to have the choice to use a different delimiter. To replicate: - First to set up a new patron attribute type called "FAMILY": - navigate to Administration -> Patron Attribute Types - Click on "New patron attribute type" - Patron attribute type code: "FAMILY", description "Names of family members" - save - Then create a .csv file with the following content: cardnumber,surname,branchcode,categorycode,patron_attributes 123123123,Testuser,MPL,S,FAMILY:John Doe,Jane Doe - Go to Tools -> Import patrons - Import your file - Under Feedback, it will contain: "attribute string : FAMILY:John Doe " - Everything after the comma is missing The help text next to patron import suggests using double quotes wrapped around patron attribute field values that contain commas, but that didn't work for me either. If you want to replicate that, do everything as above but in your .csv file use the following content: cardnumber,surname,branchcode,categorycode,patron_attributes 123123123,Testuser,MPL,S,"FAMILY:John Doe,Jane Doe" Should then fail to be imported due to an unexpected format. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 22709] New: Add hooks to notify plugins of biblio and item changes
by bugzilla-daemon＠bugs.koha-community.org 08 Apr '24

08 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22709 Bug ID: 22709 Summary: Add hooks to notify plugins of biblio and item changes 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 Target Milestone: --- We should have a way to make *Biblio *Item methods trigger actions on plugins. Maybe if we have a message queue, then enqueue messages for registered plugins (i.e. to avoid synchronous calls). -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 42

[Bug 22569] New: Stock rotation: need transfer reports
by bugzilla-daemon＠bugs.koha-community.org 08 Apr '24

08 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22569 Bug ID: 22569 Summary: Stock rotation: need transfer reports Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Target Milestone: --- The cronjob provides a report email tot he branch, however, there is no way on the staff client to view current items needing checked in/advanced at the current branch. Perhaps a 'transfers to send' report like 'transfers to receive' -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 148

[Bug 33945] New: Add ability to delay the loading of the current checkouts table on the checkouts page
by bugzilla-daemon＠bugs.koha-community.org 08 Apr '24

08 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33945 Bug ID: 33945 Summary: Add ability to delay the loading of the current checkouts table on the checkouts page Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com If a librarian has opted to load the checkouts table automatically on the checkouts page, it will trigger a call to svc/checkouts. If a librarian is checkout out 10 items to a patron, that means svc/checkouts is called uselessly 9 times, with only the 10th time being used to display the checkouts table. It would be useful to add a delay such that the table only load if the page has been display for a given number of seconds. That way the continuous scanning does not trigger useless svc/checkouts calls, but the librarian also does not need to click the load checkouts button manually. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 32

[Bug 28678] New: OPAC description for SUGGEST_FORMAT authorized values not taken into account
by bugzilla-daemon＠bugs.koha-community.org 06 Apr '24

06 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28678 Bug ID: 28678 Summary: OPAC description for SUGGEST_FORMAT authorized values not taken into account 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: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com I don't know if this problem is limited to SUGGEST_FORMAT or if it applies to other AV categories as well. To replicate: 1) Go to Administration > Authorized values > SUGGEST_FORMAT 2) Edit one of the values and change only the Description, not the Description (OPAC), e.g. Authorized value : BOOK Description : Booooooook Description (OPAC) : Book 3) Go to OPAC and log in 4) In your account, go to You purchase suggestions 5) Create a new purchase suggestion 6) Note that in the Item type drop-down menu, the label for Book is actually Booooooook I would expect the Description (OPAC) to be used here, and only if Description (OPAC) is empty, then Description would be used. (In case you're wondering the use case, while it is not possible right now to make one value the default as in bug 20682, I usually advise my clients to put numbers in front of the labels to force the alphabetical order in the order they want. For example, 1. Book; 2. DVD; 3. Audiobook; etc. It would be nice if we could have the numbers in the Description and no numbers in Description (OPAC), that way patrons don't see the numbers.) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 36538] New: Unable to Stage MARC records import
by bugzilla-daemon＠bugs.koha-community.org 06 Apr '24

06 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36538 Bug ID: 36538 Summary: Unable to Stage MARC records import Change sponsored?: --- Product: Koha Version: 23.11 Hardware: All OS: Linux Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: j.greene(a)svdpkc.org QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Created attachment 164490 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=164490&action=e… background_jobs Built the server this week and the import fails. Re-built the Koha server today and the import still fails. Trying to run Stage MARC records for import and all import fails no matter what files I use. I use my own files and it fails. Then when I export files from "https://koha.adminkuhn.ch/" and try to import it into my server ... it fails. Yet, when I import my files onto "https://koha.adminkuhn.ch/" ... it works. Thoughts? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 33650] New: Auto sort MARC tags in numeric order when saving the record
by bugzilla-daemon＠bugs.koha-community.org 05 Apr '24

05 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33650 Bug ID: 33650 Summary: Auto sort MARC tags in numeric order when saving the record Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: iming(a)rosewoodfarm.com.au QA Contact: testopia(a)bugs.koha-community.org Sometimes during cataloguing we may not have entered the tags in the correct numeric order. For example: 520 _ _ $... 500 _ _ $... 504 _ _ $... So it will be nice that when saving the record, MARC tags can be auto sort into the correct numeric order, like: 500 _ _ $... 504 _ _ $... 520 _ _ $... Currently, you can correct this issue by saving the record in basic editing mode. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 36539] New: class missing from spans on Available status in detail.pl
by bugzilla-daemon＠bugs.koha-community.org 05 Apr '24

05 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36539 Bug ID: 36539 Summary: class missing from spans on Available status in detail.pl Change sponsored?: --- Product: Koha Version: 23.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface 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 The Available status used to have a span with a class of available. That class is now missing. The rest of the statuses still have their class. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0