I am building a solution in which each Site Collection represents a single contained unit. The members of that unit will be using SharePoint to track information that describes their unit at the root level, and then there will also be sub-sites to track their contacts, their documents and their meetings (one site for each).
What I am having trouble with is this: the information that describes their unit is not really "list"-worthy. I mean, I created a List that has placeholders for the unit's: title, address, telephone line, manager, business number, telephone line, etc. etc., but then its a list that necessarily only has one item in it - a unit can only have one title, one address, one manager, etc.
Is that the proper way to record that data though? I was thinking that I could create a big term store with Managed Metadata and then have one list and then I could add a list item for each Managed Metadata item ... that's the only other way I can think of it.
Also, in the documents site, there are some document types like "communications" or "contracts" which there will be lots of, and then there are other document types that are really one-offs, like "schematics" : all units will always have just one schematic ... Does that mean I should create a "schematics" library just to house that one document?