how to implement a “colourScheme”
-
Hi,
My app deals with several different entities.
Company
>Region
>Area
>Office
Therefore, within the same company, the uniform and truck colour can vary by region/area.
What complicates matters further is that I am dealing with multiple companies, some of which vary their uniform colours by region etc, some don't.
I am thinking of the following snipped schema:
<SCHEMA>
tblColour
colourId
colourName
tblUniformColour
companyId
colourId
regionId
tblRegion
regionId
regionName
tblCompanyRegion
companyId
regionId
<\SCHEMA>
I have been searching for pointers, but all the articles seem to deal with UI colour scheme design; not how to represent the permutations that implementing a colour scheme involves.
Oviously, I want to provide a solution that is flexible.Can anyone offer a few words of advice on the above?
I'd really appreciate it.
ta,
yogi
-
This was removed by the editor as SPAM
-
I'm not sure that I'm completely following you. If I understand correctly:
- There are multiple companies
- Each company can have multiple regions
- Each region can have multiple areas
- Each area can have multiple offices
- Colour schemes vary by company, and within a company can vary be region or region/area
Questions:
- Are regions and/or areas defined by a company, or independently of a company?
- Does the database need to keep track of what level a valid special colour scheme can exist at?
- Are there default colour schemes - ones that most of a company's regions or a region's areas would use?
Depending on the answers to these question, I would consider implementing field at each parent level (Company, region) that indicates whether or not entities below that level can have their own colour schemes. I would include a colour scheme field for any Company, Region, or Area. I would set up my queries so that, if a given area has no colour scheme specified, it uses the colour scheme of the parent Region or Company, whichever has a scheme. Of course, I'm assuming that our answers to the questions fall out just right, here.
Do you follow the idea?
R David Francis -
Hi David,
Ta for the reply.
you asked:
<<
Q) Are regions and/or areas defined by a company, or independently of a company?
A) BY A COMPANY
Q) Does the database need to keep track of what level a valid special colour scheme can exist at?
A) unfortunately, there is no colourSheme defined at the moment.
Q) Are there default colour schemes - ones that most of a company's regions or a region's areas would use?
A) unfortunately, there is no colourSheme defined at the moment.
>>
The scenario is that the companies have the dodgy, non-normalised "freetext" definition for colours, ie, a free for all.
I'd like to eventually move towards a good colourScheme.
What I initially have (as an improvement) is a table for each entity, eg for a door.
<SCHEMA>
tblCompanyDoorColour
companyId
colourId
tblRegionDoorColour
regionId
colourId
tblCompanyRegion
companyId
regionId
tblRegion
regionId
isRegionRestrictedColourScheme BIT
<\SCHEMA>
Therefore, when the user is perfroming data entry for a particular office within a region, they should only be able to select a SUBSET of door colours that are applicable to that particular region, if tblRegion. IsRegionRestrictedColourScheme =1.
I can see flaws in this, namely that I have to create a new table for each:
1) ENTITY that is involved in the colourScheme.
2) LEVEL that the entity is involved with, eg company>region>area
I could go on, but I’ve already lost most of the audience in my ramble.
Can you folks see where I am trying to go with this?
All suggestions mucho appreciated,
cheers,
yogiberr
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply