LibriVox Forum

ScottLawton wrote: ↑November 19th, 2019, 4:27 pm I doubt there's a built-in filter. It's easy enough to do directly from your code: just catch the http redirect.

That's basically what I did. Catch the redirect and see if the location header contains "project-not-available"

ScottLawton wrote: ↑November 19th, 2019, 4:09 pm

danielius wrote: ↑November 19th, 2019, 1:11 pm How come https://librivox.org/rss/12349 redirects you to forums ?

AFAIK: that ID was reserved as a placeholder for a specific book which isn't yet finished, so redirects to the relevant forum thread.

Why does the API return un-finished books? Is there a way to filter them out?

not an API expert but shouldn't outsiders only be interested in completed projects? The 2 5 digit ones are not marked complete Is there a way to find out if a book is completed? In my process I am getting just the IDs and then going out and getting metadata, so not sure how to filter out non-comple...

I think I have a work around any way. I am separating getting the known IDs from getting the metadata for the IDs. I keep track of when I save the IDs I get from LV and just run a job that a couple of times a day I ask LV for just IDs (and language since I only care about English in my case) for any...

I thought to get the num_sections and using that to decide which way to parse it, but found out there are 5 books that report that they have 0 sections. 3 of them (12687, 12911, 66) actually do have no sections and they return the array instead of the map. There are 2 (76 and 473) that report they h...

Regarding the extended=1 bug with the API, I have stumbled on another piece of data about the bug. As others have pointed out setting extended=1 in the call can cause the books returned to be returned in a map with the number of sections as the key which can cause collisions with multiple books. Wha...

So the API has the since parameter to specify only getting updates since a given date. The thing that always bugged me about the API is that it doesn't actually contain that field (date_catalog) in its returned data. If it contained that field it would make getting updates easier and more foolproof....

Having trouble figuring out how to use the new API to give me new books since the last time I checked. With the old API you had to page backwards until you got to a book you had already seen. It was a pain, but worked. I figured that the books were in order by when they were completed, but that does...

So what's the story with the new API? It has not been up in months. Has the idea been scrapped or what?

New API does not appear to be working. No matter what I try I get status 0, Unknown method.

I was working on a project where I was pulling from the catalog shortly before the "event" with the catalog. Had to shelve it for a while and am now trying to pick it up again, but it appears there are still issues with the catalog. Most notably for me is that rssurl is not being populated...

Using the web API for the latest items in the catalog (http://librivox.org/newcatalog/latestworks.xml?offset=0&limit=50) has the book "A Parting Gift" (book 5503) as the first entry. This is not a new entry and I know it has been in the catalog for at least a few weeks (when I started ...

The publication dates for chapters in the RSS feeds for books are backwards in that the first chapter has a publication time of 1 second after the second chapter and so forth. If you sort the items by publication date in the RSS feed you get them in reverse order. Some podcatchers (doggcatcher for A...