Status wording or descriptions

[smit1678]

Feedback from user test: wording of the status. Open status was slightly confusing and didn't convey whether it was active. Complete wasn't entirely clear. Is it complete of the flight or complete that the right product was produced and ready.

To do: review wording. May need to look to reword, add descriptive text, or look to add more types of statuses for better granularity.

[smit1678]

Related to #129

[sharkinsspatial]

@smit1678 Any feedback on new descriptions so we can close this one out for the milestone?

[smit1678]

@sharkinsspatial Yes, will work on these over the next day and post here.

[smit1678]

How about this? cc @cgiovando

Requests can be:

• Open
• Active - this is new (perhaps if it has In Progress tasks?)
• Closed
• Cancelled

Tasks can be:

• Open
• In Progress
• Completed

[cgiovando]

Those look good to me. If there's a way to add a ? tooltip for each, then we could include more explicit descriptions to what each status means:

• Open --> The request has been submitted
• Active --> Tasks are in progress in order to fulfill this request
• Closed --> This request has been fulfilled
• Cancelled --> This request has been cancelled before completion

For tasks:

• Open --> A provider has accepted this task
• In Progress --> A provider (e.g. a UAV pilot) is collecting imagery for this task
• Completed --> Imagery was collected, processed and is now available for download (in OAM)

I'm wondering if we should add a Processing status for tasks, since quite often for aerial surveys it can take a long time between collection and when the imagery is actually mosaicked and made available.

[smit1678]

Open --> A provider has accepted this task

Well right now, when you create a task, it's set as Open. Just not assigned to anyone. Do we want to have the difference between Open, Open and Assigned (Planned), and Open and Collecting (In Progress)?

[smit1678]

Update after discussion with @sharkinsspatial: we're going to hold on this for a bit since some of this may make more sense to rethink how requests and tasks interact with each other in the future. We'll keep the three levels but expose the three Task levels better in the tooltip and cards -- which is being handled in #129.