...
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.
...
Response (9/23/16): You will manually define SUSHI accounts per vendor. When you go live, a weekly job will be scheduled to harvest the files via SUSHI. Only new files received after the SUSHI account is added to the vendor account in Alma and the scheduled job is running will be uploaded. Any older files you wish to make available in Alma will need to be uploaded manually.
Response (9/26): SUHSI configurations will be retained at cutover
Response (10/14): Campuses using USTAT will have their COUNTER data migrated between October 10 and 22
- Migrating/re-establishing SUSHI configurations (e.g. from current USTAT instances to ALMA)
...
Response (9/23/16): You will manually define SUSHI accounts per vendor.
- Availability of COUNTER usage statistics during Test Phase and Beyond (June 2016 - May 2017)via Alma
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.
...
Response (ExL HQ email to Brandon, 10/14):
- Alma Analytics COUNTER should be active starting October 23 (and COUNTER data will be retained at cutover)
- USTAT Availability From 2016 Q3 to Go Live Date
...
- to Alma Cutover for COUNTER Data - now set for October 23
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.
...
Response (9/26/16): SUSHI Configurations will be retained from testload to "Go Live," but and COUNTER data will not be retained. will be retained at cutover (ExL HQ email to Brandon, 10/14)
...
- Campuses should move from USTAT to Alma Analytics on October 23
- existing Existing COUNTER data will be migrated from USTAT (October 10-22)
- COUNTER data on Alma Analytics will be migrated from USTAT (October 10-22)
- COUNTER data on Alma Analytics will be retained at cutover
- retained at cutover
- Migration of USTAT Data - COUNTER Data
Response (10/18): ALL COUNTER Data existing on USTAT (as of 10/10) should be migrated to Alma (by 10/23)
- Migration of USTAT Data - SUSHI Accounts
Response (10/18): SUSHI account information from USTAT is not migrated. Please do not create SUSHI accounts in Alma until after the UStat data has been migrated.
- Migration of USTAT Data - matching with vendor records in Alma
To which vendor record in Alma will SUSHI accounts migrated from USTAT be attached?
Response (10/18): Incoming USTAT data is not matched on a vendor record. Incoming data Ustat will be retrievable/reportable in Alma Analytics.
Will we need to create vendor records for publishers who supply us with usage data but otherwise we have no direct relationship with?
Response (10/18): There is no specific “vendor” from the COUNTER report so it does not matter at all whether or not it appears in Alma. If you look at the usage data subject area of Alma you will see that there is no “vendor”. There is a “platform” and “publisher” but no “vendor”. The COUNTER report can be uploaded as “associated” with any vendor, and this is irrelevant as far as how it is filtered and displayed in Alma Analytics.
- Migration of USTAT Data - Cost Information
Response (10/18): Cost information added to UStat is not migrated.
- ALMA support for COUNTER reports
...
Follow-up (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). Specifically would like to get a sense of when the very valuable JR5 reports will be included.
Response (9/23/16):
Already available in ALMA as of August 2, 2016: DB1, BR1, BR2, JR1, JR1a, PR1
Planned (Stage 1 - "coming months"): JR2, JR5, DB2, BR3, MR1,
Planned (Stage 2 - 2017): JR1 GOA, BR4, BR5
Details found in Acquisitions/COUNTER powerpoint (August 2, 2016), Slides 7 and 9
- Alma Analytics COUNTER/SUSHI Features
Missing data indicator? Alma Analytics as the same "missing data" indicators as USTAT
- Support for loading non-COUNTER compliant usage data
...
Meeting password: uYFjvqQ2
. Calstate institutions to add usage data roles to relevant staff accounts and configure SUSHI accounts. These will be retained at cutover.