[Bug 39082] New: Remove or optionally hide biblioitems.metadata warning on saved reports
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39082 Bug ID: 39082 Summary: Remove or optionally hide biblioitems.metadata warning on saved reports Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Reports Assignee: koha-bugs@lists.koha-community.org Reporter: andrew@bywatersolutions.com QA Contact: testopia@bugs.koha-community.org Depends on: 17898 Back in 2017, bug 17196 moved MARC data from biblioitems.marcxml to biblio_metadata.metadata and bug 17898 added an alert and Update button on any report that Koha flagged as seeming obsolete. Bug 19638 tried to lower the number of false positives on that alert. Currently, the alert appears on any report where the saved sql includes "biblioitems" and "marcxml." This still results in false positives when one queries a field like import_records.marcxml in a report that also references biblioitems. Are we far enough our from bug 17196 to remove this warning? Or give an easy syspref or similar with which to disable it? Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17898 [Bug 17898] Add a way to automatically convert SQL reports -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39082 Jonathan Druart <jonathan.druart@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jonathan.druart@gmail.com --- Comment #1 from Jonathan Druart <jonathan.druart@gmail.com> --- Could you provide us with some examples of false positives? Maybe we can refine the regex and don't report the alert if we catch import_records? Would that be enough? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39082 --- Comment #2 from Andrew Fuerste-Henry <andrew@bywatersolutions.com> --- (In reply to Jonathan Druart from comment #1)
Could you provide us with some examples of false positives? Maybe we can refine the regex and don't report the alert if we catch import_records? Would that be enough?
I ran into this on a report to compare values in a staged MARC batch to the values in the records to which they matched or which they created: SELECT ib.title as import_title, coalesce(ib.isbn,ib.issn) as import_isbn_issn, SUBSTRING(ExtractValue(import_records.marcxml,'//leader'),7,1) as import_leader_06, extractvalue(import_records.marcxml,'//controlfield[@tag="007"]') as import_007, b.biblionumber, b.title, b.subtitle, b.author, b.frameworkcode, coalesce(biblioitems.isbn,biblioitems.issn) as record_isbn_issn, SUBSTRING(ExtractValue(metadata,'//leader'),7,1) AS leader_06, extractvalue(metadata,'//controlfield[@tag="007"]') as 007_tags FROM import_batches LEFT JOIN import_records using (import_batch_id) left join import_biblios ib using (import_record_id) LEFT JOIN biblio b ON (ib.matched_biblionumber = b.biblionumber) LEFT JOIN biblio_metadata USING (biblionumber) LEFT JOIN biblioitems USING (biblionumber) WHERE import_batch_id= <<Import batch id>> -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39082 --- Comment #3 from Andrew Fuerste-Henry <andrew@bywatersolutions.com> --- I'm open to tightening up the regex rather than hiding the warning, but I'm somewhat stumped as to how to accomplish it given the flexibility of sql syntax. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
participants (1)
-
bugzilla-daemon@bugs.koha-community.org