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

[Bug 11299] Add a button to automatically link authority records in cataloguing (AJAX)
by bugzilla-daemon＠bugs.koha-community.org 21 Oct '20

21 Oct '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11299 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- QA Contact|nick(a)bywatersolutions.com |testopia(a)bugs.koha-communit | |y.org -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 10787] Linked Data/RDF Omnibus
by bugzilla-daemon＠bugs.koha-community.org 21 Oct '20

21 Oct '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10787 --- Comment #3 from David Cook <dcook(a)prosentient.com.au> --- An interesting thing to note about WikiData is that it stores all its data as "pages". So far, I think that we've thought about RDF/Linked Data in terms of bib records, but I am thinking that we should be more broad/generic than that. It's tough to know because we're not 100% sure how we want to use RDF with Koha yet. I imagine that David Nind might have some ideas. WorldCat and VIAF offer bib and authority data in RDF format. Maybe we do just want to focus on bibs and authorities, but maybe we also want items... maybe information about libraries... I'm not sure. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 10787] Linked Data/RDF Omnibus
by bugzilla-daemon＠bugs.koha-community.org 21 Oct '20

21 Oct '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10787 --- Comment #2 from David Cook <dcook(a)prosentient.com.au> --- It seems that WikiData use a SQL database to store their source metadata (as JSON blobs) and then use BlazeGraph to provide SPARQL access to that data, according to https://www.quora.com/Does-wikidata-store-data-as-RDF-Triples-If-yes-what-k…. I reckon that they're a good example to follow. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 20280] New: Authorised value categories list in bibliographic frameworks has 2 empty entries
by bugzilla-daemon＠bugs.koha-community.org 21 Oct '20

21 Oct '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20280 Bug ID: 20280 Summary: Authorised value categories list in bibliographic frameworks has 2 empty entries 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com To test: - Edit a subfield in any of your bibliographic frameworks - In the last section, take a look at the authorised value categories list - Confirm there are 2 empty entries Tested with sample data. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14

[Bug 26510] New: Transport Cost Matrix editor doesn't show all data when HoldsQueueSkipClosed is enabled.
by bugzilla-daemon＠bugs.koha-community.org 21 Oct '20

21 Oct '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26510 Bug ID: 26510 Summary: Transport Cost Matrix editor doesn't show all data when HoldsQueueSkipClosed is enabled. 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 HoldsQueueSkipClosed is enabled, and a library happens to be closed on the day you edit the transport cost matrix, all the values for that library will not show. Instead they will appear disabled, and if you were to edit the cell and save a new value in it, it will also 'disappear' when the page is reloaded. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 26231] New: bulkmarcimport.pl does not import authority if it already has a 001 field
by bugzilla-daemon＠bugs.koha-community.org 20 Oct '20

20 Oct '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26231 Bug ID: 26231 Summary: bulkmarcimport.pl does not import authority if it already has a 001 field Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: MARC Bibliographic record staging/import Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org I'm trying to import authorities which already have a 001 and bulkmarcimport.pl says that it's worked but it hasn't actually imported anything and no errors have been thrown. I'm using this command: koha-shell -c "perl /usr/share/koha/bin/migration_tools/bulkmarcimport.pl -file /home/dcook/auth.mrc -a -fk -d -v -l /tmp/auth.log" <instance> It appears to be because the value from the 001 is being passed to AddAuthority() which - instead of adding the authority - is trying to update an existing authority. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 10921] You can edit an order even when it is in a closed basket
by bugzilla-daemon＠bugs.koha-community.org 20 Oct '20

20 Oct '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10921 Victor Grousset/tuxayo <victor(a)tuxayo.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |victor(a)tuxayo.net --- Comment #11 from Victor Grousset/tuxayo <victor(a)tuxayo.net> --- Not backported to oldoldstable (19.05.x). Feel free to ask if it's needed. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 26049] New: Replace li with span class results_summary in UNIMARC intranet XSLT
by bugzilla-daemon＠bugs.koha-community.org 20 Oct '20

20 Oct '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26049 Bug ID: 26049 Summary: Replace li with span class results_summary in UNIMARC intranet XSLT Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org In all XSLT for record display, fields are created with <span class="results_summary> except in UNIMARC intranet where there is just <li>. -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 24598] New: Hold not reset properly if checked out to another patron
by bugzilla-daemon＠bugs.koha-community.org 20 Oct '20

20 Oct '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24598 Bug ID: 24598 Summary: Hold not reset properly if checked out to another patron Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Hold requests 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 When an item that has triggered a hold is in transit to a library, if the item is accidently shelved instead of scanned at the pickup library, and then checked out to another patron, the holds shows the item still in transit in the status, but says that it is waiting at the library, and the since date has vanished! To replicate: 1) Place an item on hold at Library A for Patron 1 at Library B. 2) Check in the item at Library A to trigger the hold transfer. 3) At Library B, check out the item to Patron 2 (click Yes). * Note that the hold still show in transit in the status. * Note that the Pickup library shows the item is waiting. * Note that the since date in the Pickup library is blank. What needs to happen: If an item is intercepted and checked out to a patron while in transit: * The transfer needs to be cancelled. * The hold needs to revert back to the top of the queue. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 23

[Bug 25273] New: Elasticsearch Authority matching is returning too many results
by bugzilla-daemon＠bugs.koha-community.org 20 Oct '20

20 Oct '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25273 Bug ID: 25273 Summary: Elasticsearch Authority matching is returning too many results Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Bug 24269 attempted to improve the authority matching process in ES, however, it does not accomplish the full extent of what is needed. Match-heading is used as the matching field for records, and I added C4::Heading to be used to generate the correct form including subfields, however, the subfields are still indexed at normally too. This is problematic as the index for a heading like: $aCats$vFiction$zVermont Is indexed into match-heading as: ["Cats","Cats genresubdiv Fiction geosubdiv Vermont","Vermont"] Thus if a record has a heading of: Vermont It returns the above record. We need to index for the linker into a field that only gets the correct search form for heading and no other data. I propose to do this by retrieving the fields set to be copied from Administration->Authority types and indexing them into a field that can be used only for matching/ -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 49