https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37738 Caroline Cyr La Rose <caroline.cyr-la-rose@inlibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |caroline.cyr-la-rose@inlibr | |o.com --- Comment #1 from Caroline Cyr La Rose <caroline.cyr-la-rose@inlibro.com> --- Conversation on Mattermost with various ideas https://chat.koha-community.org/koha-community/pl/jc5b4dp9x3rsmxbtayson9wxrc -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37738 Heather <heather_hernandez@nps.gov> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |heather_hernandez@nps.gov --- Comment #2 from Heather <heather_hernandez@nps.gov> --- I would totally love this! Our default framework (the only we use) is very out of date--I just manually update them when I think to do it, with fields I know we'll use, etc., etc. It would be simple for me to take the time to compare my existing to the latest available, document what I've changed that I want to keep, import the latest framework and then modify as needed. If it were possible to protect tags and/or subfields upon overlay, that would be the dream!! -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37738 Lauren Denny <lauren_denny@sil.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lauren_denny@sil.org -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37738 Olli-Antti Kivilahti <olli-antti.kivilahti@hypernova.fi> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |Needs Signoff CC| |olli-antti.kivilahti@hypern | |ova.fi --- Comment #4 from Olli-Antti Kivilahti <olli-antti.kivilahti@hypernova.fi> --- Hi! I just a few days ago implemented a similar (or maybe the same) feture you just requested. We use this for our clients to first diff our marc frameworks (compare them side-by-side for differences) and synchronize the framework definitions. It would be utterly painful to deal with a dozen marc frameworks without tooling like this. See the attachment for the perldoc on how to use it and what features are available. I was thinking of making this a Koha-plugin, but since there is some desire for the feature, maybe it could get into the Koha-core even. Any funding/help would help us get there. See also the picture for how the diff currently looks like. It would be better as a HTML table. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37738 Olli-Antti Kivilahti <olli-antti.kivilahti@hypernova.fi> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #170746|0 |1 is obsolete| | --- Comment #6 from Olli-Antti Kivilahti <olli-antti.kivilahti@hypernova.fi> --- Created attachment 170754 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=170754&action=edit Bug 37738 - Framework update accessibility for existing installations See misc/maintenance/marc_framework_diff.pl --help -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37738 --- Comment #7 from Esther Melander <esther.melander@bywatersolutions.com> --- I do like the ability to compare frameworks and I think this should be incorporated. This does require terminal access to use it, which is perhaps not as accessible to the average user. It also doesn't alert the user through the staff interface a framework update is available. So while this is a good start, perhaps doesn't quite answer the primary question of accessibility. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37738 --- Comment #8 from Olli-Antti Kivilahti <olli-antti.kivilahti@hypernova.fi> --- (In reply to Esther Melander from comment #7)

I do like the ability to compare frameworks and I think this should be incorporated. This does require terminal access to use it, which is perhaps not as accessible to the average user. It also doesn't alert the user through the staff interface a framework update is available. So while this is a good start, perhaps doesn't quite answer the primary question of accessibility.

You are 100% correct. Could you specify a bit more in-depth, what you mean with a "MARC framework update"? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37738 David Cook <dcook@prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dcook@prosentient.com.au --- Comment #10 from David Cook <dcook@prosentient.com.au> --- This is a topic I've been interested in over the years. I reckon the way to do this is to have a "reference" framework that is automatically updated with Koha releases, and cannot be modified by web users. -- With this patch, if a lot of this code was moved into modules, then it would be easy to show the diff on the web or on the command line. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37738 Olli-Antti Kivilahti <olli-antti.kivilahti@hypernova.fi> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Signoff |In Discussion --- Comment #11 from Olli-Antti Kivilahti <olli-antti.kivilahti@hypernova.fi> --- (In reply to Caroline Cyr La Rose from comment #9)

(see for example bug 37114)

This clarifies a lot, thank you. (In reply to David Cook from comment #10)

I reckon the way to do this is to have a "reference" framework that is automatically updated with Koha releases, and cannot be modified by web users.

- How about making the default framework read-only? Well we already customize it for our clients with plugins and authorised_values and translations, so maybe not. - So maybe a new read-only -framework, titled MARC21LOC, as there are also national guidelines, such as Finnish guidelines for MARC21, and RDA-Fin. UNIMARC is needed too. This needs to be set per-system, maybe even per-record. A solution would be for the individual MARC FW to trace an origin read-only FW. - Also MARC21 authorities frameworks need to be synced (and hard-coded limits removed). - The Koha installation, as it is configured to trace a MARC-variant, and later can be changed from a syspref, needs to be told during updatedatabase.pl that new changes need to be incorporated to existing frameworks. I guess we could use DB triggers to enforce that change-log is created, even tho I personally dislike DB triggers as they put logic to the "wrong" place. A better approach is to define good Koha::MARCFramework APIs, which transparently deal with all these during CRUD-operations, embedded within SQL transactions that can be rolled back during errors. - Koha staff client mainpage.pl and a staff email notification should let the library know that there are changes that need to be synced to MARC FWs using the supplied GUI MARC FW diffing tool. - Some changes can be incorporated without user interaction, such as adding new fields/subfields, title/term renamings (I presume LOC wouldnt change the spirit of a field, but instead the letter of a field) Does this leave any situation where user interaction is needed? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37738 carthur@slolibrary.org <carthur@slolibrary.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |carthur@slolibrary.org -- You are receiving this mail because: You are watching all bug changes.