Lucy Seale
My feedback
16 results found
-
15 votes
Lucy Seale supported this idea ·
-
79 votes
Lucy Seale supported this idea ·
-
39 votes
Lucy Seale supported this idea ·
-
74 votes
Thank you for your suggestion. The Rialto team is reviewing this idea to determine how it might fit into our future plans. We cannot provide a timeline for these ideas, but be sure to check back often and vote for the ideas you support to receive status and comment updates.
Best,
Heidi Whitehead
Rialto Product Manager
Lucy Seale supported this idea ·
-
192 votes
Lucy Seale supported this idea ·
-
96 votes
Lucy Seale supported this idea ·
-
76 votes
Lucy Seale supported this idea ·
-
107 votes
Lucy Seale supported this idea ·
-
171 votes
Lucy Seale supported this idea ·
-
62 votes
Lucy Seale supported this idea ·
-
73 votes
An error occurred while saving the comment Lucy Seale 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?
Lucy Seale supported this idea ·
-
107 votes
Lucy Seale supported this idea ·
-
85 votes
An error occurred while saving the comment Lucy Seale commented
I agree, this field is obviously important for users to be able to identify areas of responsibility for works. It seems very odd that it is not automatically included in the full record display.
Lucy Seale supported this idea ·
-
257 votes
Lucy Seale supported this idea ·
-
105 votes
Lucy Seale supported this idea ·
This would be so useful. I want to use the 'Change Holdings' job to run a normalization rule on a few hundred holdings records but I'm really wary about doing it because we can't export the original records as a backup in case anything went wrong. I know we can test on the sandbox on smaller numbers beforehand but it would still be very useful to have the originals as a backup for an overlaying import.