custom survey service locking and copying discussion

----- February 22nd ----- eric_jahn [12:37 PM] @javier: So the way I currently have it, survey questions are editable and can be associated with a given survey. I wanted to ask you about the survey locking functionality, since there are at least a couple ways we could go about implementing it.

[12:39] One way, we could have it, is that when a survey is locked, all dependent questions used by it are also then locked (unless they are standard HUD questions). But this would sort of preclude reusing VI-SPDAT questions and such, which is a problem, since the 3 VI-SPDAT surveys are really similar and reuse a lot.

javier [12:43 PM] @ eric_jahn I was thinking that we can lock things on different levels , so a locked survey won't allow you to add or remove questions or labels

[12:43] then we can lock questions at their own level so that no one can change them this would include all HUD questions and VI Spdat Questions

eric_jahn [12:44 PM] Another way, a modification of the previous, is that certain questions, when created, are unlockable by a survey. So when a survey is locked, questions with this unlockable flag can still change. Only a project group admin can change them. We would use this for VI-SPDAT and HUD HMIS questions. This feature would allow questions to be reused if they are part of a "Core" set of questions. Then, we can make fixes/adjustments to HMIS questions, and all would benefit form them. These questions are tied to a particular HMIS data model/VI-SPDAT version also, so we won't change 2014 HMIS without also accidentally changing 2015 HMIS data model.

javier [12:44 PM] this allows us to reuse those questions in other surveys, so in case someone wants to create a custom survey they can still use those questions

eric_jahn [12:44 PM] @javier: I like it. We are on the same page.

[12:45] So you can lock a question. You can lock a survey.

[12:46] The other way ( a third option), is a little more flexible, but I'm not sure I like it. It would involve taking survey "snapshots".

javier [12:46 PM] @ eric_jahn yeah, that is why we have a question bank, you should look at what kavitha and anusha created in gitub for the homeapp since they were working on the survey creator and question bank, i will be reviewing it with them today at 2 in person

[12:46] yeah i don't like survey snapshots

eric_jahn [12:46 PM] Yes, I have a question bank in the current ERD.

javier [12:46 PM] we are allowing people to copy surveys, and copy questions to modify stuff

eric_jahn [12:48 PM] yes, makes sense. but if the question is locked, then even if they copy the survey, they can't edit the contained locked question.

[12:48] Do you have a link to their survey bank stuff in the home app?

javier [12:50 PM] right but the locked questions are only hud specific stuff which they can't edit

eric_jahn [12:50 PM] yes, or VI-SPDAT versions, right? (edited)

[12:51] since I think if you alter VI-SPDAT, org.code might have a problem with it. (edited)

javier [12:51 PM] so if they want to change the working etc, they can make a copy the copy works as an alias for the display text

[12:51] yes

[12:52] VI SPDAT is also locked

eric_jahn [12:52 PM] So the alias copy can be changed, even if it's HUD or VI-SPDAT and locked?

javier [12:52 PM] the display text can be changed, but not the answers

eric_jahn [12:53 PM] Okay, as long as we have a way of knowing it's altered, and not the system's official HUD/VI-SPDAT. (edited)

javier [12:54 PM] so if for domestic violence they want to diplay "did you ever feel threatened by a partner and/or fleeing from a violent relationship" they can, yes the questions have an "isCopy" flag

eric_jahn [12:54 PM] since I think altering VI-SPDAT question text is also a no-no.

[12:55] But for HMIS, I think that's okay. iirc there was discussion about scripts for case manager about how they ask the question, and how that is not standardized.

[12:57] What I'll do, asap, is get preliminary service relational diagrams posted, so kavitha and anusha can review. Then the apis flow from that.

javier [12:57 PM] ok excellent

eric_jahn [12:59 PM] I like draw.io for shared ERDs, because it has all the technical symbols, but google draw is just easier, so I'll start with that, and then move it to something better, like er master.

----- February 23rd ----- eric_jahn [11:20 AM] I'm not sure how useful "isCopy" will be, since we could make an official HUD version of a copy of a previou/original HUD survey. It might be more useful to have a way to designate, for people building new surveys that "this survey (or question) is the fully compliant official version" of HMIS standard x, or VI-SPDAT version y, so they know to pick it from the question bank.

[11:22] Maybe we could have a configurable tag we attach to each survey question or survey. We could set up tags like Official HUD 2015. Official VI-SPDAT Individual 2.1. Only the administrator could set tags.

[11:22] What do you think?

javier [4:05 PM] we are setting a hud flag as well, but we want copies to map to the original data element not create a new one

[4:06] the iscopy flag allows them to choose an already existing question and copy the question name and the answers but not modify them, only allows them to modify display text

----- February 25th ----- eric_jahn [2:36 PM] Okay, so iscopy has a question ID pointer as a data value?

[2:38] And can we use configurable tags, so we can have tags for new things like VI-SPDAT or whatever other regs/standards come our way in the future, so we don't have to hard code specific flags like "hud"? Because we'll have various years of HUD even, so tags would allow us to do things like hud-2014v2.1, hud-2015v3.0 or whatever, on the fly.