Protecting fields from the SIS loader

Description

When importing user data via SIS, we leave certain fields empty (for example expiration date). The result is that the content of these fields is deleted from the user records.

We don't want the existing field to be changed. We would like to protect it from being modified by SIS.

Resolution

We are afraid that this is not always possible. It is documented here: https://developers.exlibrisgroup.com...ment/sis/synch

Quote: The synchronization is performed in a swap all mode. This means that all of the existing information is replaced. If a field does not exist in the input file, it is deleted from the existing user. The input file must therefore always include all of external user’s information, not only the updated fields. An exception to this rule are the (...) fields (User group, Job category, PIN number,User language, Campus and Resource Sharing library), which are not replaced if they have been updated manually or if they are empty in the incoming user record.

 

• Article last edited: 06-September-2016