On 07-Nov-2010, at 8:04 PM, Jonathan Rochkind wrote:
> I am not exaclty sure what Tim is doing, but for my purposes it's really
> really important for the OpenLibrary APIs to tell me what formats a book is
> available in (if there are scans, and the URL(s) to get there; if there is a
> in-browser reader, and the URL to get there, etc).
I agree.
How about extending the OL Books API to provide
"preview": "printdisabled"
when only daisy format is available and
"preview": "borrow"
when the book is only available to borrow?
> This is (or would be if it were simple) one of the most common use cases for
> OL, no?
>
> As far as dumps - - for my apps I generally prefer per-item APIs to dumps.
> But if I were using dumps, I would not want to have to take two dumps and
> merge them; it's enough software work already to regularly update and ingest
> one dump. If the second dump is just provided over email, rather than at a
> stable URL whose fetching can be automated, it is especially not useful.
> Data dumps to be useful on my end, my end needs a way to regularly update in
> an automated fashion, since a data dump is just a particular snapshot in
> time.
Some people prefer not to rely on third-party services in production and
maintain a copy of the data in their system. I think important to provide dumps
to enable bulk access to the data available through the API.
Anand
_______________________________________________
Ol-tech mailing list
[email protected]
http://mail.archive.org/cgi-bin/mailman/listinfo/ol-tech
To unsubscribe from this mailing list, send email to
[email protected]
