https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36805
--- Comment #11 from Katrin Fischer <[email protected]> --- (In reply to David Cook from comment #10) > (In reply to Katrin Fischer from comment #7) > > I could solve that via XSLT knowing in advance, maybe that's the easier way > > out of this. > > What do you mean by this? > > I've been doing XSLT magic lately so I might be able to help you out there... We use our own XSLT files for the detail page. My XSLT foo is OK for moving the invisible tag containing the 001 info into them for our specific use case. I am a bit weary of making those changes because it's used to integrate with a third party software, but it will just need some preparation/communication in the end. So taking our use case out of consideration - how can we communicate to libraries to adjust their settings after an update? Can we store the current settings somehow so they see what needs to be updated? ... Could we even attempt to parse the links and create the new structure? Probably to hard with SQL, but with Perl it might work? -- 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/
