v1.0.0latest·742 records·0 files·793.3 KB
Aug 5, 20261
README

UMass Amherst ScholarWorks usage

Views for ScholarWorks and for every container in it.

Why this is separate from the catalogue

Different permission surface, different refresh rate. The catalogue is fully public and changes when someone deposits. Usage is partly public, changes continuously, and carries a hole that the catalogue does not:

Report Anonymous
Site views, month series, countries, cities Yes
Community and collection views, month series, geography Yes, all 731 of them
Site-wide top ten items Yes, exactly ten
Per-item views 401
Per-item and per-bitstream downloads 401

Keeping usage in its own collection puts that boundary in the data model instead of a footnote. A consumer can see that item-level numbers are missing, rather than reading a zero and believing it.

What this means for a top-items view

Erin asked to expand past the top 250 in the Atmire report. Anonymously that is not possible in the direction of more items: DSpace gives ten and stops. It is possible in the other direction, across containers, and that is what this collection carries. All 153 communities and 578 collections are ranked by views, with geography for each.

A full item ranking needs either a credentialed harvest against the same endpoints or the Atmire export from the admin UI. Neither is blocked; both need someone at UMass.

Do not sum container views

Views nest. A collection's views are also counted in its parent community, so adding the 731 containers together roughly triples the real figure. The site total DSpace reports is 139,969, while Civil and Environmental Engineering alone reports 63,015 across its descendants. Rank containers against each other, or read one at a time; do not total them.

Record types

Type Count Notes
SiteUsage 1 Repository total, month series, geography, and the access note.
ContainerUsage 731 One per community and collection. container matches the record id in umass/scholarworks-items.
TopItem 10 The site-wide ranking DSpace volunteers.

Run

pnpm scrape umass/scholarworks-usage   # 731 containers, about 3 minutes
pnpm push umass/scholarworks-usage --env dev