Table items

[felskia]

@dereklieu I am wondering where the table columns are coming from. My thought of ones that would be good would be the following:

• Name of item (ex. Ballard Elementary School)
• Device or person who submitted
• How complete the observation is
• The time that it came in
• What survey it came from

Let me know what you think here.

[dereklieu]

This sounds good. I'm basically just spitting out all the properties on every observation right now, but that's not very usable.

One thing, I'm not actually sure we can tell how complete an observation is. We could maybe have a metric for how complete a survey is, but that seems out of scope.

[felskia]

We're supposed to be doing this on the observation. At least tracking how complete it is in the app. Maybe this is something to ask @sethvincent about?

[sethvincent]

I think completeness is calculated like this:

• get an observation
• get the related survey by its id
• get the fields associated with that survey
• figure out which of the total fields have been completed based on the properties on the observation
• turn that into a percentage

My plan for the mobile app was to calculate it for any view that needs it as part of the map function that turns objects into ui components, rather than set a property on the observation.

It's possible we could set the completeness percentage as a property to simplify things.

[dereklieu]

Ah I see.

I'm actually fine not attaching it as a property, I feel that has the potential to complicate it more. @sethvincent have you already written the code to calculate completion? If so maybe I could modify what you've already done.

[sethvincent]

Cool. I think I agree about not making it a property. I haven't written that calculation function yet. Was expecting to get that bit done later this week.