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...
@tricoteur No, but specifically only because I'm *not* storing or delivering book data—I'm using external services like Inventaire and OpenLibrary for that.
I should probably take a look at what schemas are available for other things though! If there's a widely used standard for what I *am* storing, then I would definitely like to use it!
The creative work > collection sounds like a useful version of "shelf".
And whether or not you use the schema, sometimes they have good concepts you can use on their own - like bookFormat.
Un petit site Web généraliste canadien
A small, generalist, Canadian site.