Page History

Problem Statement

Setting up Individual User Accounts for Metadb Users

CUL Staff are seeing patron data throughout the system when they use their FOLIO accounts. If it is acceptable for staff to see patron data because each user has his/her own user account for FOLIO, would it work to set up individual user accounts again for Metadb?The Metadb reporting database serve as a platform for generating reports for library staff on data from all functional areas of FOLIO. The Metadb software extracts, transforms, and loads data from the FOLIO application server continuously to the reporting database through its process of data synchronization. 

Current Loans are already purged of patron data, but Historical Loans are not

...

Current and Historical Request data to be purged

-request data is not attached to fines, fees, or loans

-Request anonymization cannot currently be configured in FOLIO ;  Settings (as current loans can) 

-need to purge requester_id from folio_circulation.request__t when status is Closed, and not delete rows on this table for any other status as they pertain to request in process

-need to to purge requester_id from folio_circulation.request_t_ when status is Closed, and not delete rows on this table for any other status

-how does this impact My Account on catalog, where I can look at my current requests? Data coming from FOLIO, not Metadb

as they pertain to request in process

-solution under consideration: - script will be run manually initially, then library systems will run it as a chron job on Jenkins

...

Cornell University Library Data Privacy 

Policies pertaining to data privacy for Cornell Library patrons are described here:

• Commitment to Privacy: https://www.library.cornell.edu/about/commitment-to-privacy/

Cornell University Data Privacy Policy 

...