Closed danmichaelo closed 9 years ago
In general I wish the API would use real data structures rather than the stringy structures. What happens when Ex Libris gets a contract with the "$$International Big Money Library"?
They would certainly love all the $$s ;)
"thumbnail" : [
"$$Tamazon_thumb",
"$$Tgoogle_thumb"
],
Breaking change: I changed the
alma_ids
fromto
to make it easier to consume. I should have realized in #13, but I'm still struggling to get my head around the API response format, which is really dense. Sorry about that. (A new version bump is probably not needed since the commit is only two days old and we're still on 0.x.)
Some background:
Our library is part of a network zone consortium, which is probably why I run into a few issues. If you're interested, I've put up an example response here: https://gist.github.com/danmichaelo/6d5611592e396945b7a2
In short,
delivery
looks like this (notice the$$I
s):and
control
like this:Since I'm setting
$library
to47BIBSYS_UBO
, I'm not interested in thesourcerecordid
(which is the NZ id), but the ID for47BIBSYS_UBO
(2113615280002204). So that's what my PR is about.I think the PR shouldn't break responses like the one in
brief-search-result-local-01.json
, but testing is needed :)