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

    Acquisitions - September 2017 Enhancements

    Manually Deleting COUNTER Data Files By File ID

    You can now manually delete uploaded COUNTER data files according to their file ID. This is helpful when usage data was migrated to Alma and appears (with its file ID) in Analytics. Another use case is when a vendor changes the platform name but continues to send usage data for the same period under two different platform names.
    Alma deletes the data using the new job Delete Usage Data. The job report lists the number of delete data entries. See Viewing Completed Jobs for more information about viewing job reports.
    delete_usage_data_job_report_ux.png
    Delete Usage Data Job Report

    Additional Acquisitions Enhancements

    • idea_exchange.png Idea Exchange: The role License Viewer was added. This role can view (but not edit) licenses.
    • idea_exchange.png Idea Exchange: You can now add users as administrators to a license. This is for informational purposes only. See Managing Licenses and Amendments.
    • You can now add multiple contact people to member institutions working with a Network Zone associated with a negotiation license. See Adding a Negotiation License.
    • You can now print a license or amendment. The letter used to print the license is the License Printout Letter; see Configuring Alma Letters. Printing an amendment includes only the Terms of Use of the Amendment, not its parent license. Printing a negotiation license includes the negotiation details. See Printing Licenses or Amendments.
    • The JR1 report now includes measures for Reporting Period HTML and Reporting Period PDF, in addition to Reporting Period Total. This change can be seen in Analytics and the Missing Data page (see Managing COUNTER-Compliant Usage Data).
    • BR4, BR5, and MR1 report types are now supported for SUSHI harvest or manual upload (see Managing COUNTER-Compliant Usage Data).
    • The parameter invoice_high_total_price defines when an invoice price is considered high. Invoices received above this price are assigned the assertion code High total price (see Configuring Invoice Review Rules). However, this parameter ignores the currency of the invoice. For example, if the value of the parameter is 2500, the assertion is triggered if the invoice is 2600 GBP or even 2600 JPY.
      If you set the new parameter invoice_high_total_use_currency to true, then the invoice's value is first converted to to the institution's default currency before it is compared to the value in invoice_high_total_price. In this case, 2600 GBP triggers the assertion but 2600 JPY (which is around 19 GBP) does not. See Configuring Other Settings.
    • On the Funds and Ledgers page, the Library facet was changed to Available For and the Owner facet was added.
    • A new tab, Analytics, was added to vendor information (the Vendor Analytics Report page). On this tab, you can view analytics information about the vendor. See Adding a Vendor and Vendor Account.
      vendor_analytics_ux.png
      Vendor Analytics Report Page
    • In the new UI, you can now click View vendor to view the licensor or licensing agent on the License Details page.
      license_details_with_view_vendor_highlighted_ux.png
      License Details Page
    • Was this article helpful?