Assessment:Analytics: Difference between revisions

From DLF Wiki
Created page with "The DLF Analytics Subcommittee is working to draft out how best to capture analytics about how digital library content is accessed. In December 2014, we began to draft a set..."
 
No edit summary
Line 1: Line 1:
The DLF Analytics Subcommittee  is working to draft out how best to capture analytics about how digital library content is accessed.
The DLF Analytics Subcommittee  is working to draft out how best to capture analytics about how digital library content is accessed.


In December 2014, we began to draft a set of high-level types of data we want to capture with analytics, such as:
In December 2014, we began to draft a set of '''high-level types of data''' we want to capture with analytics, such as:
* Referrals
* Referrals
* Search terms
* Search terms
Line 8: Line 8:
* Number of downloads
* Number of downloads


We also began to define a set of content types, as those may impact the capture of analytics.  Examples include:
We also began to define a set of '''content types''', as those may impact the capture of analytics.  Examples include:
* Institutional repositories
* Institutional repositories
* Licensed resources
* Licensed resources
Line 16: Line 16:
* Websites
* Websites


And we also realized that different audiences may need different information gathered.  Here's our first draft of potential audiences:
And we also realized that different audiences may need different information gathered.  Here's our first draft of '''potential audiences''':
* Administrators
* Administrators
* Content selectors
* Content selectors

Revision as of 14:14, 17 December 2014

The DLF Analytics Subcommittee is working to draft out how best to capture analytics about how digital library content is accessed.

In December 2014, we began to draft a set of high-level types of data we want to capture with analytics, such as:

  • Referrals
  • Search terms
  • Number of users
  • Number of accesses
  • Number of downloads

We also began to define a set of content types, as those may impact the capture of analytics. Examples include:

  • Institutional repositories
  • Licensed resources
  • Digitized unique content
  • Datasets
  • Finding aids
  • Websites

And we also realized that different audiences may need different information gathered. Here's our first draft of potential audiences:

  • Administrators
  • Content selectors
  • Metadata providers
  • System administrators

If you're interested in helping this subcommittee move forward, please join the [Digital Library Analytics Google Group] and speak up!