https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39860
--- Comment #82 from Lucas Gass (lukeg) <[email protected]> --- (In reply to Mathieu Saby from comment #81) > I did not read all the comments but I am not sure to understand the purpose > of this bug. > In my library we wanted to display some new fields in our records, and to > hide others, and we just made changes to the XSLT files. It's very easy to > do, especially with the help of an LLM. Why add a new way to manage the > display of records? Mathieu, thanks for having a look here! Using custom XSLT is not a sustainable solution for us. First of all, it is not something that can be done by most library staff. Writing XSLT is a technical bar for many. Template Toolkit is much easier and is something that many librarians are already familiar with from notices and slips. Custom XSLT also must be rebased against changes to the XSLT that happen in community. This can take a lot of time OR you end up with XSLT files that are far behind the community versions. So the purpose of this bug, and the reason to add a new way to manage record display, is to provide a tool that librarians can use to modify there record display in a sustainable way. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
