Task
A Task could prepresent any form of work required in the council’s region, e.g.:
- a scheduled bin collection
- cleanup of a fly tip
- maintenance of a street
Use cases and requirements
The Task model should have properties for:
name
What the Task is.
description
More details about the Task.
status
Whether the Task is pending, started, completed, etc.
location
A link to a property or street location.
start date
When the task was started.
end date
When the task ended.
scheduled start date
When the task was planned to start.
features
What features this task is acting on. Optional depending on whether system connects them.
Types
This Task type extends from the Action schema.org type.
Sub-types
Just as Action and other common types have a number of sub-types, here are specific Task sub-types for different kinds of services councils provide:
- EmptyBinTask
- StreetCleansingTask
- FlytippingCleanupTask
Properties
Term | Mapping | Definition |
---|---|---|
name | schema:name | Identifer for the Task. |
description | schema:description | A short description of the Task. |
status | schema:actionStatus | The status of the Task. |
location | schema:location | Location information. |
start date | schema:startDate | Planned start date. |
end date | schema:date | End date. |
actual start date | schema:date | Actual start date. |
features | Feature | List of related features. |
Serialisation
Codelists
Task statuses
- Not started
- In progress
- On break
- Closed / Complete
- Closed / Not done
- Closed / Not required
- Closed / Part done
- Blocked
- Abandoned