Skip to main content
  • Subscribe by RSS
  • Ex Libris Knowledge Center

    Anonymizing Analytics Report Details

    The anonymization described in this section (which is under "Analytics") differs from the anonymization described at Configuring Anonymization (which is under "Configuring Fulfillment").
    The anonymization described in this section (which is under "Analytics"):
    • Is non-transactional. It does not relate to transactions but rather to actual data. For example, the user details in the "Users" subject area is anonymized, as well as active (non-returned) loans (as shown in table below).
    • Cannot be configured by the institution. It must be configured by Ex Libris support.
    • Does not delete from the database. If the parameter (as configured by Ex Libris support) is changed, then the data appears again.
    The anonymization described in Configuring Anonymization (which is under "Configuring Fulfillment").
    • Is transactional and is for transactions of types:
      • Fines and fees
      • Loans
      • Resource sharing requests
      • Fulfillment requests
    • Works on completed transactions only (for example fines after fully paying and loans after return).
    • Can be configured by the institution.
    • Deletes the data from the database. Therefore, it is not reversible for anonymized transactions.
    Fields that contain identifying information of users can be anonymized when creating Analytics reports. Anonymizing this data enables you to make reports for statistics and trends without violating privacy concerns or local privacy-related laws. There is also an option to anonymize a limited number of fields. With this option, all user details fields are anonymized except the ones listed below. When you create a report, fields that usually contain identifying information for users are left blank.
    • You must contact Ex Libris Support to enable anonymized data in Analytics.
    • For institutions implementing a network zone, non-transactional anonymization can be done at the network zone level while still allowing the institution to see the data in analytics.
    • The User Group field is not anonymized and is available in Analytics for analysis. 
      Setting the should_anonymize_requests_immediately_when_complete Customer Parameter to true, and/or using the anonymization job, may result in the deletion of significant quantities of data from the database. Be sure you understand the implications of this setting before selecting it.

    If you request to anonymize a limited number of fields, all user details fields are anonymized except for the following:

    The following fields in the Users subject area:

    • User Details > First Name
    • User Details > Last Name
    • User Details > Primary Identifier
    • Email > Email

    The fields in the following dimensions:

    • Analytics Objects > Created by
    • Analytics Usage Tracking > User Details
    • Borrowing Requests > Assigned to
    • Course Reserves > Librarian
    • DARA > Assigned to
    • DARA > Modified by
    • E-Inventory > Electronic Collection PO Line Approver
    • E-Inventory > Portfolio PO Line Approver
    • Fines and Fees > Staff Operator Details
    • Fulfillment > Loan Operator Details
    • Fulfillment > Return Operator Details
    • Funds Expenditure > PO Line Approver
    • Lending Requests > Assigned to
    • Physical Items > PO Line Approver
    • Physical items > Receiving Operator
    • Purchase Requests > PO Line Approver
    • Purchase Requests > Purchase Request Approver
    • Purchase Requests > Purchase Request Assigned To
    • Purchase Requests > Purchase Request Creator
    • Purchase Requests > Purchase Request Modified By