[Koha-bugs] [Bug 14957] Write protecting MARC fields based on source of import

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

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14957

--- Comment #155 from Katrin Fischer <katrin.fischer at bsz-bw.de> ---
Hi David,

1) Documentation

https://gitlab.com/gnucifer/koha-manual/commit/593c5da008dbc4b074cac9dee167cce9a6dfc250#c5e2c75dc923f21c5b95185b2f350df00fec661f

Thanks a lot, this documentation is SO helpful. We really couldn't have
continued without as the feature is quite complex.

2) GUI - Terminology and translatability

One thing that bothers me is that the GUI is a big 'rough'. I'd much prefer if
it was using better terms/descriptions like in the help instead of 'codes'. 

bachmod = Bach record modification
intranet = Cataloging module (unles it inlcudes batchmod?)
batchimport = Staged MARC import
etc.
batchmarcimport = Cronjob batchmarcimport.pl

(I hope I got them right)

Experience tells that those are likely to get translated strangely or might not
be translatable at all. 

3) Over-granularity?

Another thing that bothers me is a bit is the granularity. Being able to limit
to specific patrons seems a little overkill? Especially since the interface
expects borrowernumbers to be entered? (borrower = patron)

Is there a use case for this?

4) marc_merge_rules_modules

I am still quite suspicious of this one. We should not add descriptions to the
database ever (translatability) - and this currently won't work for new
installations. Can you please consider moving the modules to the templates
instead and checking if this table is really needed as is? Or explain to me?

At the moment the patch set doesn't apply. - I am really interested in the
feature, just feel right now that it's an old development that still needs a
bit of love.

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