Matching rules for patron data
Matching order
This is the order in which data elements are matched when patron data is loaded initially and on an ongoing basis. The matching process stops after the first match is found. If no match is found, a new record is created.
Matching order | Data from institution's authentication system | Matched against in WorldShare Circulation | Note |
---|---|---|---|
1 | sourceSystem/idAtSource | sourceSystem/idAtSource | Cycles through one by one if there are multiple. |
2 | idAtSource | barcode | Cycles through all idAtSource values if there are multiple. |
3 | idAtSource | ILL identifier | Cycles through all idAtSource if there are multiple. |
4 | barcode | barcode | |
5 | ILL identifier | ILL identifier | |
6 | ILL identifier | barcode |
The current matching path would be 1, 2, 4 above for WorldShare Circulation users only. Steps 3, 5 and 6 are used if the matching is for both WorldShare Circulation and Tipasa or Tipasa users only.
View data in the WorldShare Admin module
Library staff with the Admin role can view data by going to Admin > Account info. The idAtSource data will display in the Source System field and sourceSystem will display in the User ID at Source field.
WorldShare authentication
WorldShare authentication is the default authentication option when not using third-party authentication. For more information, contact your OCLC Implementation Manager or OCLC Support .
Data from institution's authentication system | Matched against in WorldShare Circulation |
---|---|
Barcode (patron ID from institution) | Barcode table |
Third-party authentication
Third-party authentication means that institutions are using their own authentication systems for WorldShare Circulation (for example, a campus personnel system).
LDAP and CAS authentication
Matching order | Data from institution's authentication systems | Matched against in WorldShare Circulation | Note |
---|---|---|---|
1 |
|
|
Matching operates on both fields. If only one of the fields in a combination matches, the match fails. If there are multiple idAtSource/sourceSystem combinations per patron, matching is attempted on all combinations. |
2 | idAtSource (LDAP/CAS username) | Barcode table | |
3 | Barcode (patron ID from institution) | Barcode table |
Shibboleth/ADFS
Matching order | Data from institution's authentication systems | Matched against in WorldShare Circulation | Note |
---|---|---|---|
1 |
|
|
Matching operates on both fields. If only one of the fields in a combination matches, the match fails.
If there are multiple idAtSource/sourceSystem combinations per patron, matching is attempted on all combinations. |
2 | idAtSource (username from campus system) | Barcode table | |
3 | Barcode (patron ID from institution) | Barcode table |
When a match is found
After a match has been found, you can view updates and reports for information about your patron data.
Ongoing patron load updates
Patron file processing reports