Original vs sourced material

Original vs sourced material

You might have noticed that we spoke about "sources" and "regions" in the previous pages. It is time to explain what we meant. When users insert content in the storage engine, they may either mark it as an original content they made by themselves or make it a "quote".

Ambaradan primary mission is to import and unify content from a number of external sources. We do want to be able to improve content's quality, but we cannot lie to our data consumers. If we say that some data comes from source X, this data must mirror what source X really has, to the best of our knowledge.

We also need to enable our users to choose what sources they want to use, as many of them may be sectorial, others may be controversial and, last but least, users have their likings, whatever they may be.

We manage this by dividing our content in instances of the region object. We shall later explore all network related issues for these objects, now let us start by stating the practical goal that a region is set to achieve:

  1. Group all content produced by a single external source
  2. Allow independent taxonomies (you don't expect external sources to converge onto a unified taxonomy just to make our life easier, now do you?)
  3. Allow user to select what sources they want to use
  4. Allow a unified licensing policy management at single source level
So what about quality improvements? The answer is in making communiy regions, that are capable of spawning copies from an original "sourced" material and improve it. The original stays there in its pristine state, and any user is free to join/found an editing community. How much this improved data will be eventually used is... largely a matter of marketing, as always.
It all looks very neat and easy, right? Sort of "good fences make good neighbours" policy. The problem, as we shall see, is that we also need regions to interact and exchange data. Spawning is nice, but we cannot solve everything by simply spawning stuff.