[Koha-bugs] [Bug 12477] We need better ways to manage MARC Frameworks

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

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

Bernardo Gonzalez Kriegel <bgkriegel at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bgkriegel at gmail.com

--- Comment #2 from Bernardo Gonzalez Kriegel <bgkriegel at gmail.com> ---
Created attachment 29316
  -->
http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=29316&action=edit
Field 650 as XML

(In reply to David Cook from comment #0)
> We need better ways to manage MARC frameworks for authority and
> bibliographic records (for new and existing instances).
Agreed

> 
> However, that puzzle can probably be solved in a few ways:
> 
> 1) Inform users that standard fields/subfields will be periodically
> added/updated in the frameworks; or
> 2) Create a "Refresh" type button next to each framework which puts the
> updating of frameworks into the hands of library staff

If the field/subfield is missing, adding it as 'hidden' does not affect 
present fw. And you can always preserve liblibrarian/libopac as they are...
except when they change, as in last update (Bug 12435, bib 347$f).

As in other updates I proposed, I never try to update existing fw, for
the problems that you commented.
And there is a bigger problem: translations

> We could actually just store this MARC-specific data in the YAML file, and
> then build the Default and other Custom frameworks based on a Perl script,
> which would probably be easier to maintain than the SQL that we maintain now.

If it's agreed to store fw in other format, I propose we use XML (example
attached). And the reason is translations.

We need a way to ease the translation of all configuration and sample data 
we have as SQL. I'm working intermittently on this, now I'm stuck with sample
notices, but have worked out most sql files as XML and a script to build sql
from them. And unless we propose another way, we need translated sql files at
web install time. It's not practical that each language other than english have
a lang dir commited to git.

I think that using YAML or XML is the same, in this case.

Talking again about frameworks, Bug 10963 is waiting for a review :)

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