Summary: | Remove or optionally hide biblioitems.metadata warning on saved reports | ||
---|---|---|---|
Product: | Koha | Reporter: | Andrew Fuerste-Henry <andrew> |
Component: | Reports | Assignee: | Bugs List <koha-bugs> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | normal | ||
Priority: | P5 - low | CC: | jonathan.druart |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: | |||
Bug Depends on: | 17898 | ||
Bug Blocks: |
Description
Andrew Fuerste-Henry
2025-02-10 19:21:22 UTC
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? (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>> 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. |