40 Survey Results: Survey Questions and Responses
Ad hoc/as needed
All of the above, as well as ad hoc
Also upon request
Annually and as needed to answer questions
Annually for external reporting, for internal assessment--as needed
As needed (5 responses)
As needed for an individual program review
As needed for projects
As needed for projects and subscription decisions
As needed for sporadic reporting
As needed or required
Aside from our normal data collection for ARL, we do have assessments throughout the year
for weeding.
Biannually
Budget data collected weekly
Continuously
Currently as needed, hoping to develop regular schedule
Currently, as needed. Planning to be more systematic about data collection in the future.
Daily
Data collected as needed, e.g., to meet university deadlines
Data is mostly transactional (so is collected continuously) and is analyzed as required.
Depends highly on the nature of the data request/need most data annually, some an ad hoc basis.
Different data is collected at different intervals.
E-resources usage statistics: semi-annually
Frequency varies for different data types. Some (COUNTER usage data) is gathered regularly while
other data is gathered when needed for a project.
From daily to on demand, depending on assessment purpose
Interval depends on the data. Acquisitions and expenditure data is captured in an ongoing way and is
available to collection development librarians on demand, via a suite of MS Access report macros that
pull data from our instance of Voyager. We now get most of our COUNTER stats on e-resource usage
via ProQuest’s Intota these are delivered twice a year.
Irregularly, as needed
Live for some data and on a routine basis for other.
On demand (2 responses)
Presently collected on a rolling basis as we try to establish a regular data gathering and
analysis workflow.
Project specific (2 responses)
Semiannually, January &July
Ad hoc/as needed
All of the above, as well as ad hoc
Also upon request
Annually and as needed to answer questions
Annually for external reporting, for internal assessment--as needed
As needed (5 responses)
As needed for an individual program review
As needed for projects
As needed for projects and subscription decisions
As needed for sporadic reporting
As needed or required
Aside from our normal data collection for ARL, we do have assessments throughout the year
for weeding.
Biannually
Budget data collected weekly
Continuously
Currently as needed, hoping to develop regular schedule
Currently, as needed. Planning to be more systematic about data collection in the future.
Daily
Data collected as needed, e.g., to meet university deadlines
Data is mostly transactional (so is collected continuously) and is analyzed as required.
Depends highly on the nature of the data request/need most data annually, some an ad hoc basis.
Different data is collected at different intervals.
E-resources usage statistics: semi-annually
Frequency varies for different data types. Some (COUNTER usage data) is gathered regularly while
other data is gathered when needed for a project.
From daily to on demand, depending on assessment purpose
Interval depends on the data. Acquisitions and expenditure data is captured in an ongoing way and is
available to collection development librarians on demand, via a suite of MS Access report macros that
pull data from our instance of Voyager. We now get most of our COUNTER stats on e-resource usage
via ProQuest’s Intota these are delivered twice a year.
Irregularly, as needed
Live for some data and on a routine basis for other.
On demand (2 responses)
Presently collected on a rolling basis as we try to establish a regular data gathering and
analysis workflow.
Project specific (2 responses)
Semiannually, January &July
