annise wrote: ↑February 3rd, 2025, 2:28 am
Can we ask why you feel you need this and what you are planning to do with it ?
I've uploaded all the data into graph database and I'm using it and its query language to get interesting insights, stats, even to find books and readers to listen to. Obviously, it's not full without author->section relationship and therefore I can't reliably search for recordings by an author (because recordings from compilations wouldn't be included).
I don't need an API itself, I just need the data. If LV was publishing dumps, I wouldn't have touched an API once.
annise wrote: ↑February 3rd, 2025, 2:28 am
we don't use our scarce volunteer expertise for every idea people come up with.
Since with current version of an API you can get all authors, all books, all sections and all relationships between these entities except for author->section, probably this last bit will end up in an API sooner or later. I don't see how it's less useful than author of a book or reader of a section.
annise wrote: ↑February 3rd, 2025, 2:28 am
Our Catalogue is PD and you can use it legally any way you want I know
If I'm not mistaken Catalogue is available in two forms: HTML pages and API. API doesn't have this info, and downloading/parsing thousands of HTML pages is not a choice for me. So, I will have to wait. Maybe I will come up with something in PHP
as
redrun proposed.
Below is the schema of DB I've got so far; I wonder if anyone will find it interesting.
Schema chart (Image, Github)