Data Entry Function :
Issue Brief & Policy Options construction
I would like to investigate piecing together the issue brief from individual database records.
Issue Brief Construction
I will scope this out with mock-ups, but just to tell you I'm imagining there being a page which we would start by:
- defining a topic (using a title and goal statement)
- then linking in specific entries under each of the major sections:
- scope of the problem
- past policy
- current policy
- policy options (the planning tree--see below)
- glossary
- key organizations
- key individuals
A few of these would require our building a data entry form (i.e., scope of the problem, past policy, current policy), while others already exist but would require a linking function to identify existing data (i.e., organizations, individuals, glossary).
Planning Tree Construction
The underlying structure for policy options is a simple outline, which we can start with as our on-screen display. For example:
- Option 1 [add]
- Option 1a [add]
- Option 1b [add]
- Option 2 [add]
- Option 2a [add]
- Option 2b [add]
- Option 2b1 [add]
- Option 2b2 [add]
- Option 3 [add]
- Option 3a [add]
- Option 3b [add]
For these we will need two modules: one for a descriptive category and one for the policy option or model program description.
What's tricky here is that some of these options will be descriptive rather than a specific policy option, so we'll need to have that data entry option available. You might look at the PolicyOptions Wiki for more background on how these are constructed.
Note: Later we can work on displaying the outline in graphical form:
