NON-USTAT migration

This information is for campuses using the following methods to harvest and manage COUNTER usage statistics for their electronic resources:

Data migration:

360 Counter users should export the most recent copy of the DRS Request Form from 360 Counter
All campusesEXCEPT Cal Poly SLO and San Diego State can start setting up SUSHI in the appropriate Alma vendors now

SUSHI data harvested now will be wiped during cutover, but the harvests will run again after go-live
Expect to retrieve about 12 months of reports during the initial SUSHI harvest

SLO and San Diego should WAIT to configure SUSHI vendors due to the large number of Access Provider vendor records that will be added to Alma as part of 360 RM migration

Ex Libris originally stated they would migrate 3 years of data for 360 Counter users, but they have now firmly stated that this is untested and out of scope
Users of other non-USTAT services are likewise out of scope
360 Counter campuses will retain use of the service through December 31 (Fresno, Long Beach, San Diego) or October 1 (SLO)
Recommended actions:

Set up SUSHI in Alma, as described above
Make sure the SUSHI harvesting job is enabled (Monitor jobs > scheduled jobs) as part of the cutover process or immediately after go live
After the first SUSHI job runs after go live, check the job history and Missing Data tab to determine what reports were harvested
After the data has been published to Analytics, use Usage Data analyses to evaluate which platforms have data available, and which do not, and identify gaps
Once gaps have been identified, manually load the appropriate COUNTER-compliant reports into Alma