Changes between Version 9 and Version 10 of BluePrintIncidentReporting

Timestamp:

08/23/10 14:30:22 (14 years ago)

Author:

Dominic König

Comment:

--

BluePrintIncidentReporting

@@ -140 +140 @@
 The back-end should NOT be easily customised as otherwise it is hard to share data between instances.
 
-Proposal: change to something more like this (doesn't yet handle the mapping - needs work!):
+== Proposal ==
+
+Change to something more like this (doesn't yet handle the mapping - needs work!):
+
 {{{
 irs_incident_type_opts = Storage (
@@ -157 +160 @@
  * Q: Should .represent also be modified for Display of records?
 
+== Proposal (nursix) ==
+
+a) keep the original dict, but change the values of the dict into tuples like:
+{{{
+irs_incident_type_opts = {
+        101: ("roadway.bridgeClosure", T("Broken Road")),
+}
+}}}
+b) make the .represent towards normal users show the second item in the tuple 
+rather than the first (easy tweak), while admin users may see both (the 
+controller can switch between those two)
+
+c) have a admin-only-accessible DB table irs_incident_type_opts with the 
+options available for the "normal" user like:
+{{{
+define_table("irs_incident_type_opts",
+             Field("code", "integer", requires=IS_IN_SET(irs_incident_type_opts)))
+}}}
+d) In the model, make .requires the normal IS_IN_SET (To allow Sync of records with any of the options):
+{{{
+.requires = IS_IN_SET(irs_incident_type_opts)
+}}}
+f) In the controller, if "normal" user, override this requires by:
+{{{
+allowed_options = [opt.code for opt in db().select(db.irs_incident_type_opts.code)]
+.requires = IS_IN_SET(allowed_opts)
+}}}
+
+== Questions ==
+
 Where there are hierarchies (such as roadway.roadwayClosure) provide a JS widget to split this into a hierarchical selector.