Unique identifier for a ticket in the city's internal system

Working, plain-English name given to the ticket. These are not unique IDs and can change at the discretion of the Open Data team

Where the request/inquiry originated (Public, Private Business, Academia, City Division, City Council, etc)

Which city division this request is associated with.

A short description of the dataset.

Open Data Inquiry is where most intake starts; it's where Open Data staff investigate the existance of a requested dataset and feasibility of publishing it. From there, it can become a Publish New Open Dataset Page, which is the process of connecting to city systems containing data to be published, and reviewing the content and context on an open dataset page before it's published. Update Existing Open Dataset Page tickets are the process of making and validating changes to the schema, source system or metadata of an existing page. Some of these values are 'Unknown' because these statuses were introduced after these tickets were made.

The ticket's original creation time

When open data team first replied to this ticket

Ticket's status before its current status, if any

Ticket's current status

When the ticket changed to this record's status

Tickets are often linked to other tickets. When an Open Data Inquiry ticket is completed, it can become a 'Publish New Open Dataset Page' ticket or an 'Update Existing Open Dataset Page' ticket

1. CSV
2. XML
3. JSON