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

[Bug 33789] New: Issue information is missing when adding a credit
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '23

12 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33789 Bug ID: 33789 Summary: Issue information is missing when adding a credit Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org add_credit does not pass any issue information when the credit is related to an issue. It would be handy if it did. To recreate: 1. Make sure MarkLostItemsAsReturned is set so a lost item will stay on a patrons account after being marked as lost. 2. Check an item out to a patron, make sure it has a replacementprice 3. Mark the item as lost. 4. Now check the item in. 5. Go to the patrons account -> transaction tab. You should see 2 accountlines related to the item. 6. For the account type 'Lost item' you will see issue infomation ( check out date, due date, checkouted out from, etc ) 7. For the account type 'Lost item fee refund' there is no issue information. It would be helpful for librarians if they could see this information in both places. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 33314] New: Link to bibliographic record incomplete in default TICKET_NOTIFY notice
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '23

12 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33314 Bug ID: 33314 Summary: Link to bibliographic record incomplete in default TICKET_NOTIFY notice Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org When reporting a catalog concern, an email is sent to the cataloging team with a link to the bibliographic record in question. However, this link seems to be incomplete. (Might be linked to bug 33313, but I think the source of the problem is different...) To reproduce: 1. Make sure staffClientBaseURL is filled correctly 2. Enable CatalogConcerns 3. Enter an email address in CatalogerEmails 4. Go to a bibliographic record in the staff interface 5. Click New > New catalog concern 6. Fill out the form and click Submit 7. Check the message_queue table for the message --> In the message, the link base to the record is empty a href="/cgi-bin/koha/catalogue/detail.pl?biblionumber=61" Unfortunately, it's not as easy as changing the pref name to staffClientBaseURL because the line in the notice is [%- INCLUDE 'biblio-title.inc' biblio=ticket.biblio link = 1 -%]. So I'm guessing it's taking the baseURL somewhere else, but I don't know where. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 33313] New: TICKET_NOTIFY looking for IntranetBaseURL rather than staffClientBaseURL in default notice
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '23

12 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33313 Bug ID: 33313 Summary: TICKET_NOTIFY looking for IntranetBaseURL rather than staffClientBaseURL in default notice Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org While I think IntranetBaseURL is a better name for it, the system preference is still called staffClientBaseURL ;) To reproduce 1: 1. Go to Tools > Notices and slips 2. Look for TICKET_NOTIFY 3. Click 'Edit' next to TICKET_NOTIFY 4. Click 'Email' --> In the message body is this line a href='[%- Koha.Preference('IntranetBaseURL') -%]/cgi-bin/koha/cataloguing/concerns.pl To reproduce 2: 1. Make sure staffClientBaseURL is filled correctly 2. Enable CatalogConcerns 3. Enter an email address in CatalogerEmails 4. Go to a bibliographic record in the staff interface 5. Click New > New catalog concern 6. Fill out the form and click Submit 7. Check the message_queue table for the message --> In the message, the link base is empty <br><br>You can mark this concern as resolved from the concern management <a href='/cgi-bin/koha/cataloguing/concerns.pl'>page</a> -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 32

[Bug 12532] Redirect guarantee email to guarantor
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '23

12 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12532 Bug 12532 depends on bug 33223, which changed state. Bug 33223 Summary: Koha::Patron->notice_email_address isn't consistently used https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33223 What |Removed |Added ---------------------------------------------------------------------------- Status|Pushed to master |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 33981] New: Refer to the manual, not online search
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '23

12 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33981 Bug ID: 33981 Summary: Refer to the manual, not online search Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Installation and upgrade (web-based installer) 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 koha-tmpl/intranet-tmpl/prog/en/modules/installer/step2.tt line 49 looks like this: <p>Need help? For help with granting permissions, please search online for "[% dbms | $HtmlTags tag=>'code' %] manual grant permissions" It would better to refer new users to the manual, rather than to searching online, which could give all sorts of wrong and outdated information. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 31523] New: Show OverDrive results on the staff client results page
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '23

12 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31523 Bug ID: 31523 Summary: Show OverDrive results on the staff client results page Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org It would be great if we could see OverDrive results on the staff results page, similar to how we show them on the OPAC results page. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 31696] New: Allow staff to choose default sort order of column configurable tables
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '23

12 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31696 Bug ID: 31696 Summary: Allow staff to choose default sort order of column configurable tables 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: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org It would be pretty handy if staff could choose the default_sort_order of various tables in Koha. I often write jQuery to change the sort order and it would be nice if it could be done via administration. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 31734] New: Hooks for account, recall, indexing and more actions for holds.
by bugzilla-daemon＠bugs.koha-community.org 11 Jun '23

11 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31734 Bug ID: 31734 Summary: Hooks for account, recall, indexing and more actions for holds. Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Plugin architecture Assignee: koha-bugs(a)lists.koha-community.org Reporter: stefan.berndtsson(a)ub.gu.se QA Contact: testopia(a)bugs.koha-community.org This patch adds a few more hooks and extensions to an existing hook. The existing hook "after_hold_action" has been extended with the following actions: * "transfer" for when a Hold calls "set_transfer()". * "waiting" for when a Hold calls "set_waiting()". * "processing" for when a Hold calls "set_processing()". A new hook "after_account_action" is added with action "add_credit" for when credit is added via for example PAYMENT or WRITEOFF. This is consistent with when UpdateStats is called so that a plugin can be used to log the same kind of data as the normal statistics. Another new hook "after_recall_action" with action "add_recall" is also added. Also to stay consistent with the UpdateStats usage. Lastly a hook "before_index_action" with action "update" is added for the Elasticsearch::Indexer function "update_index()" so that the records being indexed can be modified before indexing. This allows for a plugin to add metadata to index or tweak or change it to provide better search results without changing the actual records (something that might be prohibited or discouraged due to centralised cataloging). Tests are provided in the patch. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 31716] New: Enlarge the size of the authorised_value column in authorised_values
by bugzilla-daemon＠bugs.koha-community.org 11 Jun '23

11 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31716 Bug ID: 31716 Summary: Enlarge the size of the authorised_value column in authorised_values 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Some libraries want to store URLs or longer values in the AVs to make entry easier. Currently there is an 80 character limit -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 25

[Bug 19111] New: Do not mess with kohafield in authority_subfield_structure
by bugzilla-daemon＠bugs.koha-community.org 11 Jun '23

11 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19111 Bug ID: 19111 Summary: Do not mess with kohafield in authority_subfield_structure 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 Please see also bug 10306 and dependencies. In Koha we are using kohafield in auth_subfield_structure only for the link between authid and 001, as well as authtypecode and 942a. We do not have any further "kohafield functionality" as on the biblio side for additional fields like title, author, etc. (There is no authority counterpart for transform marc to koha, etc.) Sub GetAuthMARCFromKohaField is only called a few times (once in AuthoritiesMarc.pm and twice in authorities.pl). In e.g. SearchAuthorities, GuessAuthid, AddAuthority, etc. 001 is hardcoded. This actually means that you should really NEVER change the "kohafield" mapping in the Subfield structure of Admin/Authority types for 001 and 942a. I would propose here to disable the kohafield for editing on the subfield structure form (just as on bug 19096), and at least add some comments to GetAuthMARCFromKohaField. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4