Programmatic sanity checking

[Trott]

Perhaps via grunt task? Basically enforce rules that a relational database might enforce such as:

• every entry must have certain required properties
• If this artist is tied to that album, then that album better think it's tied to this artist

[Trott]

Maybe we can store the data normalized/relationally and then programmatically (and grunt-task-ize it) create the denormalized version. Storing the data normalized would guarantee that relations that need to be reciprocal are in fact reciprocal. And in the course of denormalizing, the program could check that all required properties are there.

[Trott]

We should also check to make sure that both elements specified in a relation table actually exist.