Example story: As a librarian, I would like help building my collection by seeing what is being used by students and faculty. Example story: As a subject librarian, I would like to see what resources in my subject area are heavily used at peer institutions but are not in my institution’s collection. This use case is essentially a business analytics tool that would help libraries make best use of collection building activities and funds. This would be useful at both institutional or cross-institutional levels.
Potential Demonstrations
prototype: http://hlslwebtest.law.harvard.edu/analytics-dash/sketches/final
A. In institutional and/or consortial tool's UI, return search results organized by subject class and sub-class and scaled usage score
Data Sources
- MARC bibliographic and holdings records
- LoC classification outline (650,000 records)
- Usage data (expressed as a scaled score) and including whichever of the following might be available at the local institution (see Use Case 5.1: Research guided by community usage)
Ontology Requirements
- Ability to represent sharable usage data
Engineering Work
- Prototyped at http://hlslwebtest.law.harvard.edu/analytics-dash/sketches/final/
- LoC classification classes and sub-classes need to be expressed in all-inclusive top-down hieararchy
- LoC class numbers need to be assigned to each resource -- either natively by cataloger or algorithmically
- Need a way for the librarian user to specify the scope of “their collection”
Who will do what?
- Harvard -- the Haystacks uses the LC call number classification data, unlike Stacklife itself. This data is already available through an API (although this does not run off of Linked Data)
