https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31187 --- Comment #7 from Nick Clemens <nick@bywatersolutions.com> --- (In reply to Katrin Fischer from comment #5)
I feel strongly that this has started as a 'hack', because it kinda worked... and now we are in trouble.
This is how features develop :-) Covering it with tests and preventing breakages are a fair thing to do
I feel that making a behavior change dependent on a framework setting will always keep causing us trouble - it will always lead to bug reports about things being broken one way or the other for some, but others expecting it to work that way. And I see no easy way to fix this with comments or hints in framework/Koha-to-MARC mappings page
We have plugins and mappings that are defined in the frameworks that alter behavior. I don't think this is unexpected. Editing the frameworks can have consequences and users should be aware, but we do expect Koha to work differently when the frameworks are altered.
Could we imagine making this more solid somehow if people really need it? What's the use case? Can you still use CART/PROC or is this exclusive?
I agree with Andrew - a fully fledged feature would be great here. But I don't think that is a blocker to this patch set
I think a system preference would work better and allow us to tie in with the other features using this database field in terms of documentation/linking.
I am not against adding a syspref, but I am not sure what the switch would do here? I am strongly in favor of this moving forward, and a new feature/sypref being developed on a new bug report -- You are receiving this mail because: You are watching all bug changes.