[Koha-bugs] [Bug 14645] New: Koha::RecordProcessor should deal with Koha::MetadataRecord objects

[bugzilla-daemon at bugs.koha-community.org]

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14645

            Bug ID: 14645
           Summary: Koha::RecordProcessor should deal with
                    Koha::MetadataRecord objects
 Change sponsored?: ---
           Product: Koha
           Version: master
          Hardware: All
                OS: All
            Status: NEW
          Severity: enhancement
          Priority: P5 - low
         Component: Architecture, internals, and plumbing
          Assignee: gmcharlt at gmail.com
          Reporter: tomascohen at gmail.com
        QA Contact: testopia at bugs.koha-community.org

Koha::RecordProcessor is designed to apply the right filters to records,
depending on the declared schema. This means that a Dummy filter named like
this:

   Koha::Filter::$schema::Dummy

is going to be applied to records, based on the $schema param. It is a smart
design, but in order to use this more broadly we need to remove the ambiguity
between the metadata schema (for example: MARC21, UNIMARC, DublinCore,
DarwinCore, MODS, etc) and the serialization format (for example USMARC/ISO,
XML, JSON, etc).

This will let us make better decisions on how to apply filters to records, and
also provide us with enhanced flexibility on writing filters, because MARC is
not enough information, you know? :-D

With that in mind, I proposed extending the Koha::MetadataRecord object (I even
included the record id, which could be retrieved from the search engine so less
useless processing) on bug 14639, and now propose we make Koha::RecordProcessor
work on Koha::MetadataRecord objects instead of just MARC::Record objects.

-- 
You are receiving this mail because:
You are watching all bug changes.