Allow patron load integration using v2 to implement override so internal elements are preserved
Under General Administration when setting up a user record integration using v2 of the user.xsd, there appears to be some missing functionality to bring it in line with the REST user APIs.
The suggestion is to add additional options to the synchronize method so that under Synchronization type where it currently only has 'Swap All' as the only radio button, you could toggle between this and 'Override' as per the User APIs. This would allow internal notes and other internal attributes to be preserved.
It might also be useful to add the list of fields via selection that the Override option would apply to.
Matthew Hooper
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
-
Esther Arens
commented
Just to clarify/confirm: According to a recent Alma-L thread ("API vs. file-based loads" on 2017-02-14) fields like notes and blocks are not protected from being overwritten when using API, SIS file load leaves them. Customers would like the latter option for updating users via API too.
Esther Arens
Assistant Systems Librarian
University of Leicester -
Hi,
Internal segments, such as notes and contact information, do not get removed by the SIS load. In addition, some fields on the General Information can also be updated by the library so that they don't get overridden by the SIS load. These include User Group, Campus, Title, Pin Number and Preferred Language.
Is that not your experience ?
Thanks,
Moshe Shechter
Alma Product Manager
