Upgrade internal XSLT processor
Copied from https://ideas.exlibrisgroup.com/forums/308179-rosetta/suggestions/31088020-upgrade-internal-xslt-processor
Currently ALMA seems to accept only XSLT 1.0 syntax for XSLT custom letter configuration files. This means we are deprived of the many goodies of XSLT 2.0 and 3.0:
- strong typing and XSD types
- XPATH 2.0 sequences
- XSL functions
- range variables
- regular expression matching and grouping
- URL encoding and decoding
- better value comparison
EXSLT 1.0 is not supported either, so whenever I try to do something more intelligent that some simple markup and string replacing, I hit the limits of XSLT 1.0. Trying to make decisions in your XSLT based on element values without regular expressions is a big PITA - if possible at all - and leads to huge XSLTs that nobody can read afterwards, not even the author.
And don't get me started on the nice things that XSLT 3.0 provides like JSON, attribute and text value templates, dynamic evaluation, packages and tons of extra/enhanced XPATH 3.0 functions.
As of Nov 2022, it is possible in Alma to use functions in XSL version 3 or lower for letters configuration. See https://knowledge.exlibrisgroup.com/Alma/Release_Notes/2022/Alma_2022_Release_Notes?mon=202211BASE
-
Oberdan Luiz May commented
I just discovered that now when trying to use a simple replace. My last vote goes to this.
-
Knut A Bøckman commented
Thanks for bringing this up. It got my last two votes
-
Patricia Farnan commented
Great idea. I have no spare vote :(
-
Peta Hopkins commented
+1 (no votes left)