R5.1 in the wild is… lively. In this session we’ll share what we’ve learned from harvesting thousands of real reports and integrations — the good, the quirky, and the “why is this JSON yelling at me?” bits. Our goal: help libraries, consortia, and publishers avoid common pitfalls and keep everyone’s data comparable and calm.
What we’ll cover
- Data availability: required vs. reality
A quick snapshot of who ships on time, who ships light on history, and where gaps appear — complete with a tidy chart summarizing late/incorrect/insufficient-data cases. - SUSHI in practice
How to clone credentials safely, publisher-specific quirks we’ve seen, and a reality check on endpoints, throttling, pagination, and date windows. - JSON “gotchas” we meet most
From mislabeled metrics and typos in field names to error payloads that don’t match the spec — plus clear examples of how to diagnose and fix them.
Why join
- Learn the fastest ways to keep R5 and R5.1 trend-safe and comparable.
- Grab practical checklists you can use with your vendors (or your own systems).
- Save hours of trial-and-error by learning from our… let’s call them oops-moments.
Bring your edge cases and war stories — we’ll make space for Q&A and compare notes together. This session is community-first and tool-agnostic; use whatever system you like, and take home fixes that work anywhere.
