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

[Bug 737] Map of library in search system
by bugzilla-daemon＠bugs.koha-community.org 03 Apr '25

03 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=737 --- Comment #16 from David Cook <dcook(a)prosentient.com.au> --- (In reply to Christopher Brannon from comment #14) > We would then setup jQuery to create a link to each map. Built in would be > better. We have everything we need except the code to create the link to > the map. That is the tough part. I suppose it depends on how granular you want this to be. But I think either way you're probably going to need to pay someone for this one. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 737] Map of library in search system
by bugzilla-daemon＠bugs.koha-community.org 03 Apr '25

03 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=737 --- Comment #15 from David Cook <dcook(a)prosentient.com.au> --- (In reply to David Cook from comment #13) > I'll just add that StackMap have created an entire business around this very > topic, so it might be easier said than done. It looks like StackMap leverages the shelving location and the call number for a single branch library. I imagine you would need the branch code unless you had unique shelving locations for a multi-branch library. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 737] Map of library in search system
by bugzilla-daemon＠bugs.koha-community.org 02 Apr '25

02 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=737 --- Comment #14 from Christopher Brannon <cbrannon(a)cdalibrary.org> --- Thinking about my comment more, associating a map with a location would require a combination of branch and shelving location. So, let's say we upload a map of a shelving location in the Koha uploads. If we have an authorized value of shelving maps, we could indicate a shelving location code and the image file, and limit it to the specific branch. We would then setup jQuery to create a link to each map. Built in would be better. We have everything we need except the code to create the link to the map. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 737] Map of library in search system
by bugzilla-daemon＠bugs.koha-community.org 02 Apr '25

02 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=737 Owen Leonard <oleonard(a)myacpl.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P2 |P5 - low Assignee|oleonard(a)myacpl.org |koha-bugs(a)lists.koha-commun | |ity.org -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 15157] Cronjob to automatically restrict patrons with pending/unpaid charges
by bugzilla-daemon＠bugs.koha-community.org 02 Apr '25

02 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15157 Kyle M Hall (khall) <kyle(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |39532 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39532 [Bug 39532] Script debar_patrons_with_fines.pl creates repeat restrictions, uses wrong restriction type -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 39531] New: Option to retain search terms between searches in z39.50
by bugzilla-daemon＠bugs.koha-community.org 02 Apr '25

02 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39531 Bug ID: 39531 Summary: Option to retain search terms between searches in z39.50 Change sponsored?: --- Product: Koha Version: 24.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Z39.50 / SRU / OpenSearch Servers Assignee: koha-bugs(a)lists.koha-community.org Reporter: sbrown(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl If I perform a z39.50 search but don't get the results I need with my selected targets, my search terms are erased when I click 'Try another search' to try the search again with different targets. It would be helpful if search terms were retained by default, perhaps with a 'Clear search terms' button on the main z39.50 search screen for times when libraries do want to clear all terms. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 39529] New: Incorrect relationship subfield for unimarc when linking authorities with other authorities
by bugzilla-daemon＠bugs.koha-community.org 02 Apr '25

02 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39529 Bug ID: 39529 Summary: Incorrect relationship subfield for unimarc when linking authorities with other authorities Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: laurence.rault(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org At least from Koha 23.11, in UNIMARC database, when you choose an authority to link with another authority, and select one relationship in the auth_finder, the relation code is added in subfield w, as it is for MARC21. For UNIMARC it should be subfield 5 Test Plan : 0) [PREREQUISITES in order for the authority finder plugin to come up] a) database configured in UNIMARC b) In the SNC (or TOPIC_TERM) authority type c) View the MARC structure, click on 'Actions->Subfields' for tag 550; click on 'Edit subfields'. Select the subfield 'a' tab, then pick an auth type (it could be the same SNC or TOPIC_TERM) from the 'Thesaurus:' dropdown menu; click 'Save changes' at the top. d) In the 550 field, add the subfield w if it does not exists (only to be able to view the problem) 1) In the Staff client, go to Authorities, then click 'New Authority' and pick the 'SNC' (or TOPIC_TERM) authority type (or edit an existing auth). 2) When the authority editor comes up, go to tag 550 and expand it. 3) Click on the ellipsis (...) next to subfield $a. 4) When the authority finder comes up, search for an authority, pick a relator code from the 'Special relationship:' dropdown, and then click on the 'Choose' button for one of the authorities you found. 5) Notice that the code of the relationship is added in subfield w. It should be subfield 5. 5bis) After a suitable patch will be applied : Notice that the code of the relationship is added in subfield 5 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 28608] New: Creating a biblio record leads to item creation even if framework has no items field
by bugzilla-daemon＠bugs.koha-community.org 02 Apr '25

02 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28608 Bug ID: 28608 Summary: Creating a biblio record leads to item creation even if framework has no items field Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Some framework for biblio records have no items field (952 in MARC21, 995 in UNIMARC). Records can not have items for example a serial article. In this case creating a record should not lead to item creation. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 11904] Proposal for a uniform way to send messages to user interface
by bugzilla-daemon＠bugs.koha-community.org 02 Apr '25

02 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11904 Julian Maurice <julian.maurice(a)biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WONTFIX Status|In Discussion |RESOLVED --- Comment #60 from Julian Maurice <julian.maurice(a)biblibre.com> --- Closing this one before it reaches the "10 years of inactivity" milestone :) If something like that becomes wanted, patches would probably have to be rewritten from scratch anyway. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 39524] New: Bibliographic record created from local ERM title/KBart file contains only the title
by bugzilla-daemon＠bugs.koha-community.org 02 Apr '25

02 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39524 Bug ID: 39524 Summary: Bibliographic record created from local ERM title/KBart file contains only the title Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: ERM Assignee: jonathan.druart(a)gmail.com Reporter: januszop(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: jonathan.druart(a)gmail.com, jonathan.field(a)openfifth.co.uk, martin.renvoize(a)openfifth.co.uk, matt.blenkinsop(a)openfifth.co.uk, pedro.amorim(a)openfifth.co.uk According to the manuals page for ERM (https://koha-community.org/manual/24.11/en/html/erm.html#create-a-new-local…) a local bibliographic record with basic fields taken from ERM resource information (publication_title, print_identifier, online_identifier, date_first_issue_online, date_last_issue_online, num_first_vol_online, num_last_vol_online, title_url, first_author, coverage_depth, notes, publisher_name) could be created. However, it seems that a bibliographic record created either from a KBart file line, or from an ERM resource info entered by hand contains only the title (cf. Koha::ERM::EHoldings::Title->store). -- You are receiving this mail because: You are watching all bug changes.

1 1