Bug 31953 - Add read only "default" versions of notices that would be used if no other version of a notice is defined
Summary: Add read only "default" versions of notices that would be used if no other ve...
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Notices (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-10-24 15:27 UTC by Kyle M Hall
Modified: 2022-10-24 15:53 UTC (History)
0 users

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kyle M Hall 2022-10-24 15:27:41 UTC
Right now we have "undeletable" system notices. However, these notices can be modified and there is no easy way to get back to the original version. If we made these versions also "read-only" it would make undoing mistakes much easier for librarians, as they would just have to delete the custom version of the notice.

When saving an "edited" version of these notices, it would actually make a copy with the branchcode set appropriately. The new order for selecting a notice would be branchcode specific, then no branchcode, then the "read-only" version.
Comment 1 Katrin Fischer 2022-10-24 15:53:33 UTC
I am not sure about this one tbh. 

* We already get complaints about the list of notices being confusing. This could add to the confusion of "which notice is actually used". 
* Translations: New notices are often added in English only and our default notices are mostly not very nice. I think the idea for read-only doesn't work so well in a multi-language environment.
* Our default notices are often not very nice and inconsistent. I would often not want to use them as a default.