Add new Drawing OR user field: Background of field worker

[krissy]

What

Field workers interacting with artists vary in background; some are professionals in psychology, child protection and some may be general volunteers.

It will add value to our dataset to understand the source of our information, and be able to disseminate what data can be attributed to specialists in a particular field.

How

TBC - see considerations below.

Considerations

We could add this data as an attribute of the User model. However, it isn't assured that the person uploading the drawing is the same person who interacted with the artist and collected the data. The first pilot showed a case where the user was given the drawings collected by field workers to upload later with their notes.

An alternative is we add a field to the Drawing model such as "Background of Field Worker", a simple dropdown of options such as "Psychologist", "Volunteer" etc.

To Do

• @CathMollie to confirm which route we want to take, possible input from @EChesters @rocioleon @marizoldi

[CathMollie]

Following call with @smurfyrach 19 Oct:

• Create new field with fixed values
• Start with the following set and test in pilot; can build up over time:
• Consult with @EChesters and @rocioleon on where in Data Upload page this field should go - at beginning or end, etc?

Values:

• Psychologist
• Volunteer
• Medical professional

[tanyapowell]

@CathMollie @krissy maybe add these to user signup page rather than on the upload page? Otherwise, the drawing upload form will start getting too long and the field worker will just be repeating this step everytime they upload a drawing.
In the DB can group the id column from the users table to the drawings table (e.g. make fieldworker_id column in the drawings table) via a foreign key. Haven't looked at the DB schema so this may already exist which would make adding this field to the signup page easier

[CathMollie]

@tanyapowell I think this sounds like a great option.

[krissy]

@tanyapowell really valid point about data input repetition if we introduce this field. One thing to note though is this field wasn't tied to the user specifically because in a lot of cases the person who is using the admin tool isn't necessarily the field worker who was interacting with the child - which is what this field aims to capture.

I'd say we park this ticket and not let it block the pilot, as it's not core to our dataset just yet and needs some UX review. Will de-prioritise and we can pick it up again post-pilot.

[rocioleon]

Value to add:

• Child protection