...
Detailed response to some specific questions: PDF distributed by Patrick (6/29/16)
Initial questions
- Whether/how to migrate current and historical usage data stored in USTAT into ALMA Analytics
Response (3/28/16) via Brandon: Any usage data or SUSHI configurations setup in the test instance will be overwritten during the final load in Spring 2017. Ex LIbris is currently planning to merge/bring UStat into ALMA, but has not yet addressed what that means for data currently hosted within UStat.
Follow-up-up (re-posted on Basecamp 9/14/16): Any progress or clarification on whether current USTAT data (and/or configurations) can/will be automatically loaded into ALMA? Or best practices for migrating usage data prior to go live date? (Or can we assume we will need to download USTAT data ourselves and manually upload it into Alma.)
...
Ex Libris Response (3/28/16): Any SUSHI configurations setup in the test instance will be overwritten during the final load in Spring 2017
Follow-up-up (re-posted on Basecamp 9/14/16): Any progress on whether current SUSHI configurations (e.g. from USTAT) can/will be loaded into ALMA automatically, or will we need to re-enter each account manually?
...
Response (3/30/16) via Brandon: I will ask ExL to update us on their plans in as much detail as they can currently provide as well as address what functionality will be present in our test instances.
- USTAT Availability From 2016 Q3 to Go Live Date
Response (3/28/16) via Brandon: Ex Libris announced in Feb 2016 that the ALMA roadmap for 2016 Q3 includes uploading and SUSHI retrieval of COUNTER usage data moving from UStat to ALMA. As part of this transition, UStat will no longer be available to ALMA customers.
Follow-up (re-posted on Basecamp 9/14/16): We are waiting to learn whether a potential cutover from USTAT to Alma in 2016 Q3 applies to CSU libraries since we will only have a test instance of ALMA at that time. (E.g., will CSU libraries continue to use USTAT instead of Alma Analytics for COUNTER Data through June 2017).
- ALMA support for COUNTER reports
...
Response (6/8/16) via email: “In the initial stages support for PR1 and JR1a will be added. At a later stage additional types will also be supported. This is in addition to the existing JR1, DB1, BR1 and BR2.”
Follow-up (re-posted on Basecamp 9/14/16): Specifically would like to get a sense of when the very valuable JR5 reports will be included.
...
Response (6/28/16) via Patrick: The library loads the COUNTER report data.
Follow-up : (re-posted on Basecamp 9/14/16): Does this mean there will be no support for non-COUNTER data
...
Response (6/29/16) via Brandon: Ex Libris does not plan to offer a data loading service as a free or paid service to Alma customers for several reasons (mostly financial) and would go so far to opine that they would probably not offer it to current SS/PQ customers for much longer based on their response to this question at the Exec meeting.
- Possible ProQuest Intota subscriptions
...
Response (6/29/16) via Brandon: Ex Libris does not plan to offer a data loading service as a free or paid service to Alma customers for several reasons (mostly financial) and would go so far to opine that they would probably not offer it to current SS/PQ customers for much longer based on their response to this question at the Exec meeting.
Desired Data Loading Functionality
...
Response: Yes, data can be uploaded and then deleted and then re-uploaded. Error report provided by system (JB: seems similar to USTAT error messages).
4. Duplication safeguards - if the same report is uploaded more than once, or duplicated by a SUSHI harvest, the stats are not duplicated within Analytics
Response: If a user tried to upload duplicate data they get a message: The following overlapping data was found. Note that this data will be deleted if you continue with the current download process. (JB: seems similar to USTAT messages).
...
5. Ability to download raw reports from Analytics for local use
...
Comment: examples are not exactly what we wanted to know, but answers to #7 cover some of it
...
6. Ability to upload reports to Analytics
...
Response: Yes, this is possible. You can also view the specific reports in the Alma interface and in the case of “trouble shooting” it is recommended to use the Alma interface. (screenshot in PDF)
8. Authority title matching to reduce duplicate listings and ensure statistics are properly associated with titles held on multiple platforms; ability to manually match titles where automated matching has been unsuccessful
...
Comment from NDM: withhold judgement on title authority matching until I see how it actually works in Alma--what they have set up does appear more sophisticated than the current Intota method
...
9. Ensure that ISSNs are consistently loaded in with 8 characters and include leading zeros.
Comment from NDM: ExL didn't answer this. I believe the question might be clarified in terms of how ExL handles different ISSN and ISBN formats. e.g., "0000-0020" vs. "00000020" or "978-0-03-029305-4" vs. "9780030293054." First, will Alma recognize that these pairs are the same ISSN or ISBN? Second, can it handle the leading zeroes, especially in non-hyphenated formats? e.g. when presented with "00000020," will it be able to see it as "0000-0020" or will it instead parse it as "20" because of the non-standard presentation? It should, of course, be the responsibility of the platforms/publishers to produce COUNTER reports that actually adhere to the standard, but it would be good to know how much flexibility is being built into Alma to recognize and handle the most common errors.
Follow-up
...
Reporting Functions
...
(re-posted on Basecamp 9/14/16):
In regards to COUNTER data, can Alma handle importing standard numbers (ISBNs, ISSNS) that are not in the “standard” format. (E.g. with or without hyphens and/or recognize leading zeros)?
For example, one publisher may list an ISSN as "0000-0020", another as "00000020" – and similarly for ISBNs, one may list it as "978-0-03-029305-4" and another. "9780030293054."
a. First, will Alma recognize that these pairs are the same ISSN or ISBN?
b. Second, can it handle the leading zeroes, especially in non-hyphenated formats? e.g. when presented with "00000020," will it be able to see it as "0000-0020" or will it instead parse it as "20" because of the non-standard presentation?
(While it should be the responsibility of the platforms/publishers to produce COUNTER reports that are consistent with the standard, but it would be good to know how much flexibility is being built into Alma to recognize and handle the most common errors.)
Reporting Functions
- Incorporate data from Books in Print, Resources for College Libraries, and Ulrich's
Response: On the roadmap - Intota assessment can include usage for Open Access journals, or on open access articles inside non-open access journals.
Response: Alma can get usage for data which comes from COUNTER reports. Alma can also get usage from the Alma Link resolver.
Comment - NDM: Were we asking about JR1 GOA reports? If so, that would be the best way to clarify this question. Since Carol also wants to know when JR5 will be supported, I think what we really need is:
Follow-up (re-posted on Basecamp 9/14/16): Can we get a list of ALL the reports in the COUNTER Code of Practice, both mandatory and optional, with the development status for each (i.e. implemented, expected Q_, on the roadmap).
Follow-up (re-posted on Basecamp 9/14/16): Do we know if JR1 GOA reports (open access materials) will be supported? If so, will open access (JR1 GOA) usage be automatically filtered from the standard JR1 data, or will they overlap? - Overlap analysis: journals, ebooks and streaming as currently on the Intota development timeline. Including functionality to check against external collections and unowned packages
Response: Overlap analysis can be done already. It can be done on collections owned by the library (portfolios in multiple collections) and it can be done in Alma analytics.
In Q4 2016 it will be possible to check overlap with portfolios / collections in institution and in Community Zone.
It is also possible in Alma and in Alma analytics to create reports on “duplicate titles” (titles with inventory both physical and electronic). - Ability to include/exclude platform & access fees from cost per use reports
Response: The price is taken from the invoice lines of the POL and cannot be selectively removed.
See https://knowledge.exlibrisgroup.com/Alma/Product_Materials/Overview_Materials/Presentations_and_Documents
Analytics - Overview of calculation of the cost per use in the Cost Usage subject area with DB and JR1.pptx
Analytics - Overview of Usage Data subject area.pptx - Intota’s planned proportional pricing enhancements to provide more accurate title costs across a package
Response: The Alma method of determining cost per use is very exact and precise.
See https://knowledge.exlibrisgroup.com/Alma/Product_Materials/Overview_Materials/Presentations_and_Documents
Analytics - Overview of calculation of the cost per use in the Cost Usage subject area with DB and JR1.pptx
Comment- NDM: Two things are not addressed here: Carol's question re how Alma handles journals outside the package (is their usage lumped in? what about their subscription costs? can they be excluded?) and this question of proportional pricing. I'm not quite sure I understand the proportional pricing part myself, though I imagine it is to do with the way journal packages can include journals that cost $250 and journals that cost $25,000, and they get treated the same way in cost/use. We might want to clarify exactly what the desired functionality would be here. Regarding the exclusion of non-package titles, this can be done with a filter in Alma Analytics now, but I have no idea how their associated costs are handled (I can't test because we didn't migrate acq data).
Follow-up (posted on Basecamp 9/14/16): The COUNTER BR 2 reports seem to simply lump all types of sections into one field. Does Alma currently (or are there any plans in the future) to identify different types of sections reported in the BR2 counter reports, e.g., with filtering?
Follow-up (posted on Basecamp 9/14/16): Cost per useIt looks like we can filter out “non-package” journal titles in standard Alma Analytics reports now. Do these filters work with the cost-per-use reports (where could we filter out non-package titles from cost per use calculations)?
Does Alma have any mechanism for handling proportional pricing in package or cost per use analysis? (E.g. – a journal package may include a title that runs $250 and another that runs $1750 – any way to weight these types of proportional costs?)
Desired functions not currently in Intota and unknown with regard to Alma Analytics:
- "Out-of-the-box" reports corresponding to all collections questions for the major surveys
- Most of them are now available, but a few of the trickier ones like title count are not
Response: Alma analytics has a very vast, well used and proven set of OOB reports.
Comment - NDM: The OOB reports are good (and they are), but the specifically referenced report, Title Count, is not among them, and I don't see one posted by the Community, either. That said, we are capable of coming up with some of our own, to share among the CSU as well as other Alma customers.
- Most of them are now available, but a few of the trickier ones like title count are not
- Automated collection analyses to aid in decision making, including benchmarking. May be part of ExL’s KPI work.
Response: Overlap analysis (portfolios in collections) and duplicate titles (physical and electronic) we have. Benchmarking and KPIs are on the roadmap - Clearly identify BR2 (e-book usage) report "Section Type" (e.g. chapter, section, page, etc.)
Response: A report of display titles for BR2 with the “Book Success Section Requests” is available in the PDF
the PDF
Comment - JB: This appears they cannot identify the specific type of section being reported, but lump them all into the generic "section requests" category.
Comment - NDM: Looks like Analytics treats all BR2 data as generic "section requests."
Comment - JB: This appears they cannot identify the specific type of section being reported, but lump them all into the generic "section requests" categoryThis answers the question of how Analytics treats the data, but not our request to handle different section types differently or at least have a column that identifies section type and allows for filtering.
Comment - NDM: Looks like Analytics treats all BR2 data as generic "section requests."
This answers the question of how Analytics treats the data, but not our request to handle different section types differently or at least have a column that identifies section type and allows for filtering. Follow-up (posted on Basecamp 9/14/16): The COUNTER BR 2 reports seem to simply lump all types of sections into one field. Does Alma currently (or are there any plans in the future) to identify different types of sections reported in the BR2 counter reports, e.g., with filtering? - User-configurable adjuster for estimated average chapter length to allow better comparison between e-book platforms that report BR2 usage by page vs by chapter
- This would allow for more realistic "top performers" or cost-per-use reports across the collection
- As it currently stands, the usage stats from aggregators like PQ and EBSCO, as well as encyclopedias and similar reference titles, overwhelm and hide the usage from PDF-chapter-oriented platforms (JSTOR, MUSE, most publisher sites)
- Development plans include creating a place to store, manage and use data from non-bibliographic services (study room usage, lib instruction sessions, etc.) in various analyses.
Response: It is not possible to upload data directly to Alma analytics. The data comes to Alma Analytics via Alma. In the case of the usage data: COUNTER reports are loaded to Alma, then from Alma there is a daily ETL to Alma analytics.
Comment NDM: what we would like to know is whether it might be possible to manage non-bibliographic metrics through Alma. This seems like a complex idea, so I think we should clarify it for ourselves before asking again. For example, are we thinking this is something we'd want to manage through Booking? Perhaps some of these metrics would be better managed elsewhere; though I can see advantages to having consistency across campuses, Alma may not be the answer to everything.
...