Categories, and keywords for each client comes directly from XML file imported in the system via the “Feed Parser”. Categories are retrieved from the parsed “pname” (profile name) field in the xml. States are a fixed list of options (50 States plus DC, PR, and US).
Filter configurations will be kept for each user. To aid in setting defaults and modelling changes client-wide, filter records will be stored in a symetrical client filters table.
Any filter setting (State, Category, or Keyword), being disabled for a user, will hide the associated bill. A bill will have multiple Keywords and Categories, so an “active” filter does not override an “inactive” filter. Any disabled filter match disables the bill. Certain features will ignore the filters, but that will be a rare case in the system.
Client filters that are Inactive are inactive for all users belonging to that client.
Each filter settings will be stored inside the database with the following fields
client_filters Table and user_filters Table:
client_id(int) / user_id (int) [only field not identical in both tables]
filter id(varchar) [ e.g. US; Environment, Pesticide ]
As categories and keywords are imported, they will be added to the table:
Figure 1 - setting client categories
* All bills (legislations, regulation and hearings) that comes with XML file have state “field /column” are filled in with abbreviations of all the US states (including Alaska, Hawaii, District of Columbia and Puerto Rico) and plus they can have a value of US. Value of “US” means that this bill is federal legislation.
Figure 2 - setting client states
For each setting, a staff role will be able to set 2 possibilities of options:
· Setting mail active/inactive – This setting is only used for the “daily” and “weekly” digest emails. It is not used for email notifications.
· Setting frontend active/inactive – meaning that the bills will be presented inside the legislation dashboard view (map and list view). This setting also is used for deciding if a notification should be sent (by email), meaning that if frontend set to active a notification about
Figure 3-setting client keywords