[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 #381 from David Gustafsson <glasklas at gmail.com> ---
Hi again!

> It seems weird to have the pref off but the link to the admin page visible.

I have not made any active decision regarding this, it's been like this since
before I got involved and have never given it much thought. Don't have any
strong opinions either way. Elasticsearch settings seems to work the same way,
that is if SearchEngine is Zebra, you still have a "Search engine configuration
(Elasticsearch)" link in Administration with a "Elasticsearch is currently
disabled" notice at the top. So personally I would probably keep it as it is
just to avoid the extra work (even though should be pretty easy to change).

> > 6. How does it interface with the marc modification templates when batch
> > editing bibliographic records?
> 
> Investigating.. I have a feeling his patchset predates it and I missed this
> case ! :(

I don't have time to look at this today but can do on Monday.

> I know librarians can have weird needs but, should we really offer the
> "custom" preset? I am reading the tests right now and some combinations are
> doing funky stuffs. Maybe we could simplify the UI if we stick to the only 1
> "action" column with the predefined ones? (not considering this question a
> blocker, but I would be happy to get an answer).

I see no reason to remove this, I just don't see the harm of having the option
if there is some weird scenario where it could be useful. I don't see the
"custom" option as complicating the UI, it's just an extra choice in a
dropdown.

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