search

AguaClara / post.odkForms-DEPRECATED

0 stars 0 forks source link

1 L/s plant option #6

Open jacuerp opened 7 years ago

jacuerp commented 7 years ago

Soon it will be common for plants to have a 1 L/s plant operating parallel to their main treatment plant. This is so far only the case at Cuatro Comunidades. Operators should be able to submit data separately for the 1 L/s plant and the main plant.

This can't be done by simply adding a "Cuatro Comunidades 1 L/s" option because operators no longer choose the name of plant they are submitting for. That leaves a few ways I can see to do this:

  1. Add a column like 'nLiterPerSec' to plantParmeters, and add a question asking the user if they want to report 1 L/s data as well.
  2. Add a column to plantParameters like above, and instead just automatically display the questions for both the main plant and the 1 L/s plant.

I like option 2 because it enforces equal reporting for both plants. It also wouldn't look too ugly if we displayed questions on the same page. i.e. call the new column for 1 L/s raw water turbidity "rawWaterTurbidity_L" and have the questions for rawWaterTurbidity and rawWaterTurbidity_L share one page.

@danelimjoco @fawnwong What do you think?

danelimjoco commented 7 years ago

Plant operators probably wouldn't be able to conveniently collect data from one plant and then walk over to the other plant so it probably isn't ideal to have questions for both the main plant and the 1 L/s displayed on the same page. So instead, it'd probably be better to ask all the questions for the main plant, and then follow that with all the questions for the 1 L/s plant.

eak24 commented 7 years ago

@danelimjoco @jacuerp I have a different suggestion. Pretend the 'plantName' is not actually the plant's name, but rather the name of the group of operators in the region, meaning many plants can belong to a given operating group name. This understanding more accurately maps to the way it is currently programmed - the operators' login info defines the boundaries for what info they can enter about which plants. Now, within that understanding, the particular 'plant' just becomes another multiple choice question that is populated from the plantParameters CSV sheet. In short, the operator will see a list of plants IN THEIR 'OPERATING GROUP' DEFINED BY THEIR LOGIN CREDS to choose from. That choice should populate the plantName column of the submission. This method wouldn't add any columns to Fusion Table, still restricts operators to only submit data for their particular plant, and enables practically infinite number of plants in a given operating group. How does that sound?