Well, my wife is going out tonight, which means it's #Readlebee dev time! I probably won't stream it this time, but I should hopefully be able to finish shelves, shelf items, and maybe even get started on book references!
I'm excited to see how much I can get done!
Gah, I'm hitting a huge snag with shelf items because I haven't fully worked out book references yet. I may need to refactor the database again—I think I need more tables and a better way to think about the data structure... I was hoping I could keep the database relatively small/clever, but I'm seeing now that it won't really be possible with such a large project...
I have a headache from trying to figure it out right now... time for a break so I can process and mull over options.
Ok, my current idea for #Readlebee data structure is to split the unified "Status" table into two double-duty tables that store Ratings+Reviews and Updates+Progress. That way it'll be a little bit easier to manage than just trying to split from one table.
I still need to figure out what to do about books, though... I want to be able to target specific editions for reviews, but I don't want a ton of repetition in the database... using editions from Inventaire could work, but it's...
...not super easy to understand the difference between them sometimes... I'm debating just doing an empty field so you can just write "audiobook version" or "1953 paperback" or something like that , but that'll lead to even more confusion since there are many different audiobook versions etc... I'm not sure. I guess using Editions is the best way to go?
I just don't want to bog people down with having to choose an edition unless they want to, like how GoodReads does but without the giant db.
Did you look at schema.org for book?
Un petit site Web généraliste canadien
A small, generalist, Canadian site.