I'm ready to begin building a databased-website that will provide cataloged details about the various gods, goddesses and pantheons.
I'm looking for the most efficient structure for cataloging them. Such as what data pieces / fields would be generic enough to be important for all deities yet not be majorly unused on the majority of the entries (and it needs to capture those deities who have different names among different cultures). I've read and own multiple books that cover this topic and they each tend to be primarily author-myopic, focusing on the mythologies / religions that the author considered most important while ignoring the countless other deities worshipped by groups of people. I also have seen (and bookmarked) multiple 'God Databases' and they, as well, seem to be stunted, and not allowing for growth.
Basically, any database architecture, metadata, cataloging recommendations would be greatly valued and appreciated.
For clarification purposes. I want to use this website / database for a set of specific purposes.
- Public Domain. Almost every site out there that tracks deities has these disclaimers that stop you from referencing their entries on the deities without some serious contractual agreements, others just say no. I want something that can be referenced by all, for all, and updateable by those who have a legitimate interest.
- OGP.me. I would like to be able to reference a god in a tweet or facebook post and have a decent image, title, etc. display just like when you post a reference to a blog post, or instagram image. In order to do this, the structure needs to be Open Graph ready. That's part of my goal.
- Fields. By 'field' I am trying to convey that I am looking for metadata properties, descriptors, etc. that are generic-enough to fit for most deities (and deity-like entities). Think "NAME" (as an example) all mythological entities have a name. Some have hundreds. NAME would be a field I could use. DISCIPLINE would be another. Don't be locked into "text field" concepts. I can offer multiple choice selections. That way, when entering Dionysus I could enter under DISCIPLINE several entries such as 'grape harvest', 'winemaking', 'wine', 'ritual madness', 'fertility', 'theatre' and 'religious ecstasy'. The end desire would be to be able to search for the word 'fertility' and Dionysus (as an example) would pull up.
- Technical Sidenote: For those more DB-savvy, I am NOT naming this object / table "DEITY" but rather "ENTITY" and I didn't include this information in the initial question to avoid confusion for those not familiar with DB structuring. I've worked with databases for more than 2 decades and I've learned that if you're not comfortable with creating tables, queries, and relationships then DB naming conventions will only confuse you.