build3 / LSOA

Learning Sciences Observation App - Vanderbilt University
2 stars 0 forks source link

Teacher can return to an existing observation with additional tags/constructs selected #145

Open cbradyatinquire opened 5 years ago

cbradyatinquire commented 5 years ago

Scenario: Teacher is doing observations, and realizes, mid-observation (e.g., after collecting a photo or video) that it reflects more Tags or Constructs than are on the "palette".

He or she would like to go back to the Setup screen, add tags or constructs, and then, on submitting these changes, resume the editing of that in-process observation.

This would obviously NOT happen if they changed the Class that was being observed. But all other features of the setup screen could (coherently) accommodate returning to the observation screen in process.

A similar thing may be needed for EDITING past observations. So, this ability to have a "pending" or "open" observation that we "go back to" might be useful in more scenarios than this one.

zachmccormick commented 5 years ago

Note to self: this might be possible via saving the observation, going back to the setup screen, then going back to the observation screen for that particular observation. Maybe use a in_progress flag or something if needed?

zachmccormick commented 5 years ago

From #164 "Right now, if you begin an observation, leave the screen, and come back, your work is cleared. This is USUALLY only an inconvenience.

However, there is at least one place where it puts the teachers in a bind. If they are working with the class, realize that the data they've collected falls outside of the set of the constructs you have chosen, and then need to go back to the SETUP screen, you lose your work when you return.

Saving the in-process state of the observation screen would solve this problem. An alternative solution could be to figure out a later editing path using the "N/A" observation classification mentioned in #163"

zachmccormick commented 5 years ago

I totally think we should do this with a "Save as Draft" concept. It'll be easy to implement that way and you can save multiple drafts, and maybe have a draft list to go back and either edit more, commit it as an observation, or delete it.

zachmccormick commented 5 years ago

Note to self -- "Done" and "Save As Draft" can be two different buttons on the bottom right, and we can expose these as drafts in the "Work Queue" via a column