We are running a database system which is basically working as a pipeline flow architecture, i.e. we have lot of incoming data, process this using a variety of in-house knowledge data, and then we produce output data.
Right now everything is intermingled, which makes it difficult to know what is autogenerated and what is not etc. We are now looking to divide it up in these classes into schemas of their own but we don't have a good idea of what to name the different schemas. Here are the classes we have:
- Incoming data
- Static, human-entered, manually updated data
- Analyzed/aggregated data (i.e. produced with the two other components an input)
Is there a standard way of naming this kind of division? Does anybody have a good suggestion on what we might call them?