...
Deadlines
- ACRL: February 28, 20192020
- IPEDS (Academic Libraries section): April 1022, 20192020
Recommended Practices for Consistent Reporting from All Campuses
- Run Library Collections (lines 40-44) reports on July 1, or as soon after as practical
NOTE: The original 4xb eResource reports intended to be run in the NZ will not work due to a persistent problem with the 'Available for Group' members dimension. A fix is not expected until Q3 2020. "Alternate NZ reports" have been included in the "Run in IZ" folder for the 40b, 42b & 43b queries. These utilize the "Portfolio Details for Consortia" measures which allow reporting on the NZ from the IZ. Be sure this feature is active in your IZ: Analytics Objects: Analytics Member Settings > analytics_network_inventory_available_for_my_institution = true.
- Regardless of when reports are generated, run Library Collections reports as a "snapshot" of the collection on that day
- There is no simple way to filter out items/portfolios added after July 1 and add back items/portfolios withdrawn after July 1; it's especially problematic for portfolios where there's a fair amount of addition/deletion activity at any time
- Count document delivery, ILL, and pay-per-view expenses in Line 22 (e.g. Reprints Desk, Get It Now)
- ILL costs that can't be separated from the cost of the ILL software should be counted along with Bibliographic Utility costs in Line 25
- Count DDA Short Term Loan (STL) expenses in Line 22
- Count DDA triggered purchases in Line 20 (and 20a for ebooks)
- Include ECC resources in Library Collections counts
- Gather and load your own usage reports (manually or using SUSHI) for all resources, including ECC and other SDLC resources
- Usage will NOT be centrally loaded to Alma to avoid duplication, as vendors do not distinguish the license source when reporting usage on their entire platform
- When reporting BR2 usage for platforms such as Ebook Central that count every pageview, add a comment that data from these platforms is included in the total
...