CAUL Advisory Committees

Closing the Loop: Evaluating Your Key Scholarly Communication Programs and Services

Feed: News | Association of Research Libraries® | ARL®
Posted on: Thursday, 22 May 2014 3:00 PM
Subject: Closing the Loop: Evaluating Your Key Scholarly Communication Programs and Services

seattle-skylineAugust 7, 2014, in Seattle, image © Chris TarnawskiMany libraries have been operating scholarly communication programs or providing scholarly communication services for several years. We have identified what is important to our communities. We have thought strategically about what services we might best offer. We have discussed how we might organize ourselves to deliver those services. How can we maximize the impact of the scholarly communication programs and services we offer? How do we know we’ve achieved our intended outcomes for our target audiences? What tools can help us begin to measure those outcomes?

View article…

This email, including any attachment, is intended solely for the use of the intended recipient. It is confidential and may contain personal information or be subject to legal professional privilege. If you are not the intended recipient any use, disclosure, reproduction or storage of it is unauthorised. If you have received this email in error, please advise the sender via return email and delete it from your system immediately. Victoria University does not warrant that this email is free from viruses or defects and accepts no liability for any damage caused by such viruses or defects.

Advertisements

Filed under: Quality & Assessment, Research

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: