Posting challenges, usually time bound or on a particular topic or theme.
As is sadly typical during my A-Z Blog Challenge runs, I’m struggling in the middle. Ah well, it’s the weekend, time to catch up! In a recent post I said that now that I’ve got a sense of the column types and their configuration, it’s time to get specific about …
I was planning to show how various entities might be defined, using the attribute declarations described yesterday… but it’s been a rough week. Instead, I’ve been cleaning up some of my libraries, and found some features I hadn’t considered that I’d very much like to see in my graphical user …
Yes, taking the easy route on naming the “K Day” post. There’s enough thinking in this one I don’t feel bad about it. Yesterday I looked at the data types available in calibre for custom columns , and made a few notes about how I might handle column definition. Time …
In looking at the data models, I’ve focused mostly on ‘user-defined columns’ in the expectation that I’d use the same mechanism for ‘built-in columns’. Which raises the possibility of someone taking the library and bending it in strange ways, doing things I had no reason to think they would. If …
“I’ll just put together a little proof of concept application. Get some screenshots, that’ll look sexy.” Yeah. Yeah, I’ll do that. My background is in software development. I’ve been writing code for more than thirty years now, both for work and to support my hobbies (as in “make tools to …
‘Test your assumptions’ is an important step in any kind of analysis and design exercise. It appears calibre’s database design is not entirely the cause of poor performance at higher record volumes. Don’t get me wrong, the design and implementation of the database can certainly be tightened up… but I …
So far, I have What I haven’t talked about yet is what I’m going to do with the information once I’ve got it, how I’m going to present it and use it. Short answer? I think it’s going to look a lot like calibre… but there will be some differences. …
This post is mostly to capture the spurious thoughts that pop up while designing a data model. Specifically, things that could be captured and managed by this tool, that strictly speaking are not ‘media’. I’m sure more will come to mind as I go.
Yesterday I explored some data objects I expect to need in my media library. That’s a good start, but a relational database is not particularly useful until it has relationships. Thus, I’ll want an Entity Relationship (ER) Diagram showing how the different pieces are related. In this post I’ll also …
It seems almost certain that the data engine for this application is going to be a relational database. My analyses so far have concluded the data is pretty structured. Most applications I’ve worked on have had pretty specific requirements when it comes to their data. These have mostly been business …
