François Renaville
My feedback
21 results found
-
30 votes
Hello,
We will reach out to the provider and ask for the metadata for this collection.
Thanks,
Tamar Ganor
Content Product ManagerFrançois Renaville supported this idea · -
313 votes
We’re looking at adding an indication in the Manage In Process Items next to a request where there are more digitization requests for the same item in the queue. A row action will allow the staff to complete the current active request and activate the next.
An error occurred while saving the comment -
275 votes
We are considering incorporating the idea and effect both templates and rules editing permission
An error occurred while saving the comment François Renaville commentedThanks, Itai. This would meet our expectations here.
I agree with Maaike's comment.
Best,François
An error occurred while saving the comment François Renaville commentedAgreed!
François Renaville supported this idea · -
299 votes
An error occurred while saving the comment François Renaville commentedAgreed.
François Renaville supported this idea · -
21 votesFrançois Renaville supported this idea ·
-
218 votes
Dear all, since this idea combines various very different enhancement requests for Alma's normalization rules infrastructure, we are unable to add these to our roadmap at this time. This may change as we get more information on prioritization and needs. In the meantime, we suggest opening dedicated ideas for specific enhancements you would like to promote.
An error occurred while saving the comment François Renaville commentedI have once by mistake overwritten an XML Normalization Rule (copy-paste in the wrong rule). No possibility to come back to the previous version. Luckily, the support was able to find it back. Otherwise, it would have taken me hours to analyze the source data again and rewrite the whole rule... I wish there would be a "View versions" with a Restore possibility.
François Renaville supported this idea · -
32 votesFrançois Renaville supported this idea ·
-
313 votes
An error occurred while saving the comment François Renaville commentedThis would be a great new feature!
François Renaville supported this idea · -
39 votesFrançois Renaville supported this idea ·
-
114 votesFrançois Renaville supported this idea ·
-
53 votesFrançois Renaville supported this idea ·
-
84 votesFrançois Renaville shared this idea ·
-
80 votesFrançois Renaville supported this idea ·
-
269 votes
Hi,
Of course ! We will add a job that will be able to run on a set of user records and purge them, using standard validations (such as no existing loans, fees).
Thanks !
An error occurred while saving the comment François Renaville commentedAgreed. Alternatively, it would also be helpful to have the Purge User job in the list of Scheduled Jobs. This would make things so easy for libraries concerned by the GDPR
-
181 votesFrançois Renaville supported this idea ·
-
206 votes
Hi,
Makes sense ! Currently, the user information that is displayed in the user Ajax search results (e.g. patrons services WB) is hardcoded.
A mapping table, similar to the one that configures the user pop up, will control the fields that show in this list. The mapping table will enable the same fields that the user pop up allows, and allow setting the order of the fields.
Thanks,
François Renaville supported this idea · -
18 votes
An error occurred while saving the comment François Renaville commentedSome similarities with another idea "Less Scan In operations" https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/14907846-less-scan-in-operations
François Renaville supported this idea · -
39 votesFrançois Renaville supported this idea ·
-
82 votesFrançois Renaville supported this idea ·
-
93 votesFrançois Renaville supported this idea ·
Any ETA maybe for this accepted idea? Thanks.
François