Child pages
  • Collecting Usage Stats: A Proposal

This is a public wiki space. All contents are publicly accessible unless page restrictions are in place.

Skip to end of metadata
Go to start of metadata

Product Stakeholder Group and friends,

Please review the following proposal for collecting usage stats on the new Calisphere beta site and distributing them to content owners. Feel free to comment on this page (requires login/UCSF wiki account) or send any feedback and questions to

Your response is requested by May 22.

Thank you!



What stats system would we use?

We would use Google Analytics for tracking usage of objects on the new Calisphere beta site.


How would content owners’ stats reports be set up?

  • Each unit record in the Registry would have a field in which to input a Google Analytics Tracker ID. The UCLDC Collection Administrator for each campus would be responsible for inputing this Tracker ID. He/she could elect to apply the same Tracker ID to all of the units (resulting in a single Google Analytics report for all units at the campus) or could paste different Tracker IDs into the different units (resulting in a separate report for each unit).
  • In order to obtain a Tracker ID, the UCLDC Collection Administrator would create within Google Analytics either a new Account or a new Property that is linked to an existing Account. Either way, CDL would recommend a new Tracker ID is generated because this will result in a separate report for usage of the Calisphere beta site.


What data would be collected, and on which pages?

  • CDL does not plan to engineer any custom events for content owners’ usage reports, unless this is surfaced as a need. This means that the typical (but extensive!) suite of usage data from Google Analytics would be reported in the areas of Audience, Acquisition, and Behavior.
  • Data would be reported on each unit's digital objects, collection landing pages, and institution landing page.


What about filtering by collection?

  • Filtering by collection would be enabled within a given Google Analytics report.
  • Campuses/units would be able to decide how they want to see different collections represented in the report (for example, by collection number or name). There would be some kind of "collection ID" field on every collection record in the UCLDC Collection Registry. Here, the UCLDC Collection Administrator could input any unique identifier they want in order to see the collection in the stats report. For collections that have corresponding finding aids, by default the value in this field will be the collection number.


  • No labels