NASIG 2011: Reporting on Collections

Speakers: Sandy Hurd, Tina Feick, & John Smith

Development begins with internal discussion, a business case, and a plan for how the data will be harvested. And discussion may need to include the vendors who house or supply the data, like your ILS or ERM.

Product development on the vendor side can be prompted by several things, including specific needs, competition, and items in an RFP. When customers ask for reports, they need to determine if it is a one-time thing, something that can be created by enhancing what they already have, or something they aren’t doing yet. There may be standards, but collaborative data is still custom development between two entities, every time.

Have you peeked under the rug? The report is only as good as the data you have. How much cleanup are you willing to do? How can your vendor help? Before creating reports, think about what you have to solve and what you wish you could solve, statistics you need, the time available to generate them, and whether or not you can do it yourself.

There are traditional reporting tools like spreadsheets, and increasingly there are specialized data storage and analysis tools. We are looking at trends, transactional data, and projections, and we need this information on demand and more frequently than in the past. And the data needs to be interoperable. (Dani Roach is quietly shouting, “CORE! CORE!”) Ideally, we would be able to load relevant data from our ERMS, acquisitions modules, and other systems.

One use of the data can be to see who is using what, so properly coded patron records are important. The data can also be essential for justifying the redistribution of resources. People may not like what they hear, but at least you have the data to back it up.

The spreadsheets are not the reports. They are the data.

VLACRL Spring 2011: Clay Shirky, Fantasy Football, and the Future of Library Collections

As we shift to a demand-driven collection development approach, we will better be able to provide content at the point of need.

Speaker: Greg Raschke

Raschke started off with several assumptions about the future of library collections. These should not be a surprise to anyone who’s been paying attention: The economics of our collections is not sustainable – the cost and spend has gone up over the years, but there is a ceiling to funding, so we need to lower the costs of the entire system. We’re at a tipping point where just in case no longer delivers at the point of need. We must change the way we collect, and it will be hard, but not impossible.

The old system of supply-side collection development assumes that we’re working with limited resources (i.e. print materials), so we have to buy everything just in case someone needs it 10 years down the road when the book/journal/whatever is out of print. As a result, we judge the quality of a collection by its size, rather than by its relevance to the users. All of this contributes to an inelastic demand for journals and speculative buying.

The new system of demand-driven collections views them as drivers of research and teaching. It’s not really a new concept so much as a new workflow. There’s less tolerance in investing in a low-use collection, so there is an increase in the importance of use data and modifying what we collect based on that use data. The risks of not evolving and failing to innovate can be seen in the fate of the newspapers, many of whom held onto the old systems for too long and are dying or becoming irrelevant as a result.

Demand-driven collection development can create a tension between the philosophy of librarians as custodians of scholarship and librarians as enablers of a digital environment for scholars. Some think that this type of collection development may result in lower unit costs, but the reality is that unless the traditions of tenure and promotion change, the costs of publishing scholarly works will not go down. One of the challenging/difficult aspects of demand-driven collection development is that we won’t be getting new funds to do it – we must free funds from other areas in order to invest in these new methods (i.e. local digital production and patron-driven acquisitions).

The rewards of adapting are well worth it. The more our constituencies use the library and its resources, the more vital we become. Look at your data, and then bet on the numbers. Put resources into enabling a digital environment for your scholars.

Demand-driven collection development is not just patron-driven acquisitions! It’s about becoming an advanced analyst and increasing the precision in collection development. For NCSU‘s journal review, they look at downloads, impact factors, publications by NCSU authors, publications that cite NCSU authors, and gather feedback from the community. These bibliometrics are processed through a variety of formulas to standardize them for comparison and to identify outliers.

For print resources, they pulled circulation and bibliographic information out of their ILS and dropped it into SAS to assess the use of these materials over time. It was eye-opening to see what subject areas saw circulation greater than one over 10 years from the year they were added to the collection and those that saw no circulations. As a result, they were able to identify funds that could go towards supporting other areas of the collection, and they modified the scopes of their approval profiles. [A stacked graph showing the use of their collection, such as print circulation, ejournals/books downloads, reserves, and ILL has been one of their most popular promotional tools.]

As we shift to a demand-driven collection development approach, we will better be able to provide content at the point of need. This includes incorporating more than just our local collections (i.e. adding HathiTrust and other free resources to our catalog). Look to fund patron-driven acquisitions that occur both in the ebook purchasing models and through ILL requests. Integrate electronic profiling with your approval plans so that you are not just looking at purchasing print. Consider ebook packages to lower the unit costs, and use short-term loans for ebooks as an alternative to ILL. Get content to users in the mode they want to consume it. Do less speculative buying, and move money into new areas. It is imperative that libraries/librarians collaborate with each other in digital curation, digital collections, and collective bargaining for purchases.

There are challenges, of course. You will encounter the CAVE people. Data-driven and user-driven approaches can punish niche areas, disciplinary variation, and resources without data. The applications and devices we use to interact with digital content are highly personalized, which is a challenge for standardizing access.

I asked Raschke to explain how he evaluates resources that don’t have use data, and he says he’s more likely to stop buying them. For some resources, he can look at proxy logs and whether they are being cited by authors at his institution, but otherwise there isn’t enough data beyond user feedback.