[Koha-bugs] [Bug 5528] Analytical records support

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

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

--- Comment #8 from Ian Walls <ian.walls at bywatersolutions.com> 2011-10-06 20:46:06 UTC ---
I have pulled down the analy-3.6 branch from the
git://kohadev.osslabs.biz/analy_3.6.git branch, and squashed it into a commit
based on today's copy of master.  Here is the list of issues I've discovered so
far:

1. merge conflicts on updatedatabase.pl and kohaversion.pl.  The patches set
versioning themselves, instead of waiting on DB rev assignment by RM.  Easy fix
2. Appears to be based on 3.4.1 instead of master... a 3.04.001.000 DB rev
exists and needs removing.
3. Minor merge issue on addbiblio.tt with bugfix 6576; easy fix
4. Includes a full set of German templates in /koha-tt; will need to bulk
remove those from the commit, since translation is handled by other mechanisms.
5. Legacy cataloguing/linkitem.tmpl file needs removing (there is a .tt
version)

All the above are minor and easy to clean.  But I've got some bigger concerns:

This development manually pulls in MARC21 and UNIMARC fields/subfields
throughout it's code; there is no utilisation of the Frameworks to determine
field semantics.  One side effect:  we wind up ignoring NORMARC completely! 
Another is that we're limited to a single relationship type (Host Item Entry)
and it's forcibly tied to the existing MARC representation.

Not using the Frameworks seems to stem from not having a database table with
which to connect the frameworks with.  Creating such a table is a little more
complex, since multiple MARC fields could map into the same table structure,
just with a different 'type' value.  Perhaps specifying it as
"table:type.field", and modifying the code to strip the ":type" part out (one
line in C4::Biblio::TransformKohaToMarcOneField might do it).

-- 
Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA Contact for the bug.