Hanoch Roniger
My feedback
7 results found
-
24 votes
Hello everyone,
I’d like to share our plans to introduce support for XSL (Extensible Stylesheet Language) normalization rules. This new feature is designed to handle complex normalization tasks and offers the flexibility of a full programming language, enabling advanced data manipulation. It will complement our existing normalization rules based on DROOLS, preserving all of its current capabilities.
Would the addition of this new type of normalization rule address the requirement outlined in this idea?
Hanoch Roniger
shared this idea
·
-
77 votesHanoch Roniger
supported this idea
·
-
218 votes
Hello everyone,
I’d like to share our plans to introduce support for XSL (Extensible Stylesheet Language) normalization rules. This new feature is designed for handling complex normalization tasks. It offers the flexibility of a full programming language, enabling advanced data manipulation. This will complement our existing normalization rules based on DROOLS, maintaining all of its current capabilities.
Would the addition of this new type of normalization rule meet the requirements outlined in this idea?
An error occurred while saving the comment An error occurred while saving the comment Hanoch Roniger
commented
The site did not allow us to post the suggestions directly, only via attachment.
This is a list of the requested functions (the file also contains explanations & examples)
1. Position sensitive functions
2. Popup function
3. Identify & remove duplicate fields
4. Position sensitive removeSubField function
5. Functionality for Booleans in if conditions
6. Let the changeField also control indicators
7. Add the possibility to delete specific repeatable subfields based on contents
8. Possibility to check "when" conditionals after manipulation of the fields
9. Possibility to add several subfields with one function
10. Add functionality to copyField based on position
11. Add functionality to copyControlField based on position
12. Add the possibility to check if contents are the same
13. Check string length
14. Let functions run on several fields
15. Add mathematical functions / variables
16. Function for merging all subfields to a single subfield
17. Use metadata from within the NR
(See also: https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/18865093-normalization-rules-adding-dates)
18. Possibility to exchange data between holdings and bibliographical records
19. Add possibility to add/remove characters based on hex/Unicode to bypass problems with problematic characters
20. Add "View versions" to NRHanoch Roniger
shared this idea
·
-
76 votes
Hello everyone,
I’d like to share our plans to introduce support for XSL (Extensible Stylesheet Language) normalization rules. This new feature is designed for handling complex normalization tasks. It offers the flexibility of a full programming language, enabling advanced data manipulation. This will complement our existing normalization rules based on DROOLS, maintaining all of its current capabilities.
Would the addition of this new type of normalization rule meet the requirements outlined in this idea?
Hanoch Roniger
shared this idea
·
-
113 votesHanoch Roniger
supported this idea
·
-
134 votesHanoch Roniger
supported this idea
·
-
183 votesHanoch Roniger
supported this idea
·
Please check (and support) the following suggestion:
https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/44068353-position-sensitive-nrs-normalization-rules-isb
It contains only #1, which is the most problematic to circumvent, especially when the field is repeatable
Since it only contains a single request, it might have a higher chance of being developed