Se si passa alla fornitura su richiesta, in che modo ciò influirà sugli utenti correnti nel nostro sistema ILL?
Applies to
- Tipasa
Answer
You will need to perform two patron loads to keep existing patrons. The first patron load will add an ILL identifier but keep the current source system and user ID at source values. The second patron load will add the new source system and user ID at source values, and use the newly added ILLid as the match point.
The above recommendation also applies if you are switching authentication methods/SSO providers/IdPs and are using provision on demand for both.
Before you switch authentication methods, check the following:
- The values used to match existing patrons are case-sensitive. Use the ILLid and user ID at source values exactly as they appear in the existing patron records, including uppercase and lowercase letters
- Send both patron loads to the test directory first. In the test results, the number of New records should match the number of new patrons you expect. If the results show more New records than expected, those patrons will not be linked to their existing accounts, so resolve the difference before loading to production
- Wait until both patron loads have processed in production before switching to the new authentication method. You can confirm this in the Patron Summary Report
If patrons have already signed in and new accounts were created instead of linking to their existing accounts, delete the new accounts with a bulk delete file, then load the correct ILLid and new source system and user ID at source values to the existing accounts.
Additional information
- Caricamento dati utente delimitato da tabulazioni
- Regole di corrispondenza per i dati utente
- Is there a way to test patron loads?
- Authentication methods and patron data load
- Is there a way to populate the ILLId field at the time of account creation using provision on demand?
- Eliminazione globale di dati delimitati da tabulazioni
