Allow multiple versions to run from same database

[struan]

It could be useful to have multiple front ends with different subsets of data, e.g. for putting TWFY data that is not relevant to TCC.

Rough steps are:

• create a "sites" table which stores a list of front ends
• many to many link between sites and datasets
• many to many link between areatypes and sites
• update front end to only load datasets and areas for the current site
• update the front end to allow for cobranding based on current site

[ajparsons]

On a quick look, cobrands can prob be just the header footer and homepage?

[struan]

Probably, yes.

[ajparsons]

Additonal things:

Can assume that a private dataset on one cobrands won't be on another?
Users: will need to be gated to one site?

[struan]

hmm, users is a whole other thing I have not considered above so yeah, would need to associate users with sites which might require some annoying django model faffing.

Dataset wise I'd envisaged that the privacy settings would be universal. I'm a bit confused as to why you would want to have data private on one site and public on another?

[struan]

The user gating is mostly so we can handle any privacy/consent issues with admins for different sites. Again, we'd need to look at what current admin users have access to.

[ajparsons]

I could maybe imagine someone might have the same private data on two networks, but yes having it public anywhere would defeat the point

[struan]

oh, right, I see. There is nothing in my plan that would prevent private data being in two different cobrands.

I guess long term would need to have a "only available on original cobrand" and "available to all cobrands" setting for datasets and then each cobrand can have a page to let you select the set of public data you'd want to use.

In the short term could do this in the django admin using common sense.