lock fields in patron records
A problem we have is that when Alma imports updated patron data from the University's Central Registry database -- via an integration profile -- it can overright values that should not be overwritten for certain groups of patrons.
What we require is the ability to lock fields in patron accounts so that they cannot be overwritten.
Alex Birchall
shared this idea
Hello All,
This idea has been closed as part of a cleanup process for ideas older than two years with fewer than 20 votes.
This cleanup process is necessary to streamline our idea management process and ensure that the most relevant and impactful ideas receive the attention they deserve. If you still feel strongly about this idea, you may submit it via the NERS process.
We value your feedback and encourage you to continue submitting and voting for ideas that you believe will enhance Alma.
Alma Product Team
-
Alex Birchall
commented
Hi Moshe,
User Group is one such user account field. We have users in certain manually assigned user groups and when these are updated from SIS, the user group is changed to what it was before.I should explain that the vast majority of our users are "External" -- they get created and updated by the feed daily SIS load.
We do have a script in place that should mean we do not often see records inappropriately updated, but it still happens occasionally.
Another field that we sometimes wish not to be overwritten is the expiry and purge date.
One solution might for staff to make these accounts Internal but then that would mean other data that we do want to sync with our SIS would not be updated.
Best regards
Alex
-
Can you elaborate on what type of fields should not be overwritten ? Are they initially imported from SIS but should not be later changes by the next SIS load ?
