Case
Note: The Case model is currently incomplete and needs further development.
A case is a way to track transactions with a citizen.
Use cases and requirements
The Case model should have properties for:
subject
Describe what the case is about.
customer
The person who created the case, or is recipient of the outcome.
date created
When the case was opened.
status
Current status of the case.
Types
This maps to the Smart Cities Concept Model Case type.
Sub-types
Just as Action and other common types have a number of sub-types, here are specific Service request sub-types for different kinds of services councils provide:
- AdditionalBinRequest
- AssistedCollectionRequest
- BulkyCollectionRequest
- ChargeableBulkyCollectionRequest
- ClinicalOneTimeCollection
- ClinicalCollection
- ReportDamage
- ReportMissedBin
- DeadAnimal
- EmergencyCollection
- FreezerCollection
- NewCollection
Properties
Term | Mapping | Definition |
---|---|---|
subject | schema:name | Subject of the case. |
status | Text | Current status, e.g. active, closed. |
customer | schema:person | Customer of the case. Should include name, address, telephone, email. |
date_created | schema:dateCreated | When the case was created. |
ReportMissedCollection
Additional properties needed to report a missed bin collection:
Term | Mapping | Definition |
---|---|---|
collection_type | string | The Container type machine name, if related to a missed bin collection. Otherwise a common string identifier of the collection type. |