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

[Bug 15930] New: DataTables patron search defaulting to 'starts_with' and not getting correct parameters to parse multiple word searches
by bugzilla-daemon＠bugs.koha-community.org 25 Aug '16

25 Aug '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15930 Bug ID: 15930 Summary: DataTables patron search defaulting to 'starts_with' and not getting correct parameters to parse multiple word searches Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org So far I know this is affecting: request.pl svc/members.search When two terms are used to search e.g. 'Henry Acevedo' no results are returned The query in the system is searching for borrower.'surname' LIKE 'Henry Acevedo%' The searchtype parameter needs to e set to 'contain' -- You are receiving this mail because: You are watching all bug changes.

1 29

[Bug 16921] New: Authority Linking doesn't match to proper record
by bugzilla-daemon＠bugs.koha-community.org 25 Aug '16

25 Aug '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16921 Bug ID: 16921 Summary: Authority Linking doesn't match to proper record Change sponsored?: --- Product: Koha Version: 16.05 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: MARC Authority data support Assignee: gmcharlt(a)gmail.com Reporter: vanoudt(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 53394 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=53394&action=ed… New Linker Module: BestMatch We've had some trouble here linking our records to their proper authority records. The zebra search seems to be giving back results that match only on the first word. Copied from an email to the devel list: ----- ...I'm in the process of trying to relink all of our biblios to the right authority files. Somehow, they were an /incredible/ mess. I've created the authority records okay, but when trying to run link_bibs_to_authorities.pl, it links them to the wrong places. Investigating, it seems like zebra isn't giving the right search results back. I can confirm this in yaz-client using the query that is created by koha. Searching for "Bentley, Peter, Ed." returns 4 results, only two of which are close. Actually, the record I'm trying to match is "Bentley, Peter, (Ed.)" - the last option. Interestingly enough, if I search for "Bentley, 3432531531532513985735981<anything at all here>" it will also show me the same four results.So does searching for "Bentley 513513531513515151".But searching for "Bentleyr435435151551251" shows no results, as I would expect. ----- Not sure what's going on here - but in desperation, I wrote a new Linker Module. It's called the "BestMatch" linker. Basically, it gets all the authorities back from the search, and then searches through them all to find the one that matches perfectly. If there is no perfect match, it tries to find a match that differs only in whitespace/punctuation. The only problem - it is understandably very SLOW It's possible that I've completely missed the point here. But the BestMatch linker seems to be doing the job for us. Note: To do a successful match, the authority data was exported from bibliographic records using koha-auth, then imported into the authorities table, and then the link_bibs_to_authorities.pl script run with the BestMatch linker selected. -- You are receiving this mail because: You are watching all bug changes.

1 9

[Bug 7569] Add Google Transliteration tool to fields during cataloging and in advanced search in OPAC
by bugzilla-daemon＠bugs.koha-community.org 25 Aug '16

25 Aug '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7569 Indranil Das Gupta <indradg(a)l2c2.co.in> changed: What |Removed |Added ---------------------------------------------------------------------------- Change sponsored?|--- |Sponsored -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 7569] Add Google Transliteration tool to fields during cataloging and in advanced search in OPAC
by bugzilla-daemon＠bugs.koha-community.org 25 Aug '16

25 Aug '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7569 Indranil Das Gupta <indradg(a)l2c2.co.in> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |indradg(a)l2c2.co.in Assignee|ebin.joseph(a)osslabs.biz |indradg(a)l2c2.co.in --- Comment #1 from Indranil Das Gupta <indradg(a)l2c2.co.in> --- This bug has not been touched by the assignee (Ebin Joseph) in last 4+ years. The original reporter (Savitra Sirohi) too has moved on (he no longer works in library technology domain). Given that this is useful to Indian libraries, L2C2 Technologies will like to take over this bug and push out the patch. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 13952] Import and export of authority types
by bugzilla-daemon＠bugs.koha-community.org 25 Aug '16

25 Aug '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13952 --- Comment #21 from Aleisha Amohia <aleishaamohia(a)hotmail.com> --- Just to explain further: We worked out why Import wasn't working. The patch itself appears to be fine. When we try to Import and exported file, the database sees that authtypecode already exists and instead of importing into a new authority type, it simply updates the existing authority type with that authtypecode. This is why we see no error when it doesn't work - it still 'worked', just didn't do what we wanted it to do. This means we must change the file itself so that authtypecode matches the Code of our new authority type, however after spending way too long fiddling around, we realised that LibreOffice formatted the file weirdly after saving and caused errors in the file, so the Import didn't work properly. This is probably a separate bug, regarding the way the code handles incorrectly formatted files and the error message it shows. Changing the authtype code in Vim did not stuff up the formatting and meant we were able to Import correctly. So, the patch itself should work as long as all the speechmarks etc. are in the right places after you have changed the authtypecode to match your new authority type. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 13952] Import and export of authority types
by bugzilla-daemon＠bugs.koha-community.org 25 Aug '16

25 Aug '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13952 Aleisha Amohia <aleishaamohia(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #53066|0 |1 is obsolete| | --- Comment #20 from Aleisha Amohia <aleishaamohia(a)hotmail.com> --- Created attachment 54840 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=54840&action=ed… Bug 13952: Import and export authority types This patch amends C4::ImportExportFramework to work for authority types as well as MARC frameworks. New file: admin/import_export_authtype.pl Update: Ensuring we are passing the right column to the right tables. Update2: Making the error messages the same to be consistent with patch on Bug 15665 Update3: Fixing merge conflicts Update4: Fixing merge conflicts and removing tabs Update5: Getting rid of warns, making sure Import and Export of default authority will work To test: 1) Go to Admin -> Authority types 2) Confirm there are two new columns 'Export' and 'Import' in the table 3) Click 'Export' on an existing authority type and choose a file type, click 'Export' 4) Confirm that the authority type is exported as your chosen file type. Save the file 5) Create a new authority type 6) IMPORTANT STEP: Before you import, make sure that the authtypecode of the file you are going to import matches the Code of your new authority type. Use Vim or something similar to do a search and replace and change the codes in your file - do NOT use LibreOffice etc. because it tries to be too helpful and messes with the formatting of the file (this is what has broken the Import function in previous testing of this patch) 7) Import into your new authority type using the file you just exported (make sure you've done Step 6) 8) Confirm you are taken to auth_tag_structure.pl 9) Go back to Authority types 10) Click 'Import' next to any existing authority type and attempt to import a file that is not XML, CSV or ODS. Confirm that this fails and you are asked to import a file of the correct file type 11) Confirm Export and Import work for the Default authority type 12) Go to Admin -> MARC bibliographic framework 13) Confirm that the 'Export' and 'Import' functions still work here as well Sponsored-by: Catalyst IT -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 13952] Import and export of authority types
by bugzilla-daemon＠bugs.koha-community.org 25 Aug '16

25 Aug '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13952 Aleisha Amohia <aleishaamohia(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Failed QA |Needs Signoff -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 12586] Record matching rules - Required match checks doesn' t work with MARCXML
by bugzilla-daemon＠bugs.koha-community.org 25 Aug '16

25 Aug '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12586 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |katrin.fischer(a)bsz-bw.de --- Comment #13 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- Interesting read in this context - I wasn't aware of the database side check option before: http://bywatersolutions.com/2013/07/23/match-points-in-koha/ -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 4460] Amazon' s AssociateID tag not used in links so referred revenue lost
by bugzilla-daemon＠bugs.koha-community.org 25 Aug '16

25 Aug '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4460 --- Comment #25 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- I ended up way back... where no bug numbers and explanations exist. -- You are receiving this mail because: You are watching all bug changes. You are the QA Contact for the bug.

1 0

[Bug 4460] Amazon' s AssociateID tag not used in links so referred revenue lost
by bugzilla-daemon＠bugs.koha-community.org 25 Aug '16

25 Aug '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4460 --- Comment #24 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- It looks like Reed Wade removed the ref parameter in the first attempt to fix this bug: https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=10024 Wasn't able to find out when and why it was added. -- You are receiving this mail because: You are watching all bug changes. You are the QA Contact for the bug.

1 0