| 2 | Tasks & Deliverables | From Governance Charge -
A list of patron data cleanup activities and assignments that need to be accomplished prior to the initial data migration. A list of patron data issues which require harmonization decisions, to be made available to the Implementation Coordinators group.
| 15 min | Greg | Ex Libris Migration Guides & Tutorials From Governance Charge - A list of patron data cleanup activities and assignments that need to be accomplished prior to the initial data migration. All but 2campuses have provided copies of their documents; reminder to the remaining campuses to upload an anonymized copy as soon as possible. The final two sites confirmed that they posted documents late Friday after the agenda was posted.
A list of patron data issues which require harmonization decisions, to be made available to the Implementation Coordinators group. Question: Now that the decision has been made regarding separate institutional patron databases, should we consider any harmonization? At the June 1st meeting, the group wondered how direct borrowing will work in the consortia (e.g., a UCSD student goes to UCB to borrow a book directly) and if this dictated any harmonization. From 6/8 Minutes, Greg Ferguson inquired with Ex Libris if harmonization of any user fields was necessary and confirmed that there was none. Follow-up pertaining to direct borrowing; during the 6/8 discussion, an Alma site representative asked to confirm if we needed to have any level of harmonization as it relates to the user group in this scenario as it pertains to loan periods received at the owning library. Greg Ferguson confirmed the following with Ex Libris: Each UC campus (institution) will have a fulfillment network user group created in their local Alma instance for the purpose of direct borrowing. This fulfillment network user group will then automatically be assigned to the linked record created for direct borrowing (assuming they are not in a restricted user group at their home institution) when information is retrieved and shared to the institutional instance. As this relates to loan policies at the owning institution, we may have some options, but this discussion is more appropriate for the Fulfillment & ILL FG: Utilize the default fulfillment network user group for all other UC direct borrowing patrons, creating a single group of loan policies, differentiated by location and item type, regardless of level (i.e., undergraduate, graduate student, staff, or faculty). According to Ex Libris, this is a common practice in fulfillment networks. Utilize the default fulfillment network user group for all other UC direct borrowing patrons, then use job category when setting circulation policy. This requires that other UCs would need to include job category information (students, staff, faculty) in the user records, allowing each campus to then configure different fulfillment rules based on job category. Manually change the default fulfillment network user group in the linked user record to the local equivalent value. In theory, this would allow for the current practice (assuming we all currently follow this practice) of providing the same level of local privileges to the visiting patron at the owning campus library.
| | - All - 1a. Create local patron data audit and cleanup document and place anonymized “snapshot” copy in shared folder.
ACTION: Greg Ferguson will share the direct borrowing/linked patron/fulfillment network user group information with the Fulfillment & ILL FG chair |
| 3 | PCODE Revisit Redux | | 15 min | Greg | From 6/8 Minutes: 6/22 Update
| | |
| 45 | Homework | | | | | Team decision to hold our Patron Data meetings bi-weekly. We’ll leave the meeting on the calendar and cancel as-needed. | All - (ONGOING) Add questions for up stream Alma Sites |