Report Request Log – City Council and its Committees

The City Clerk's Office maintains a log of report requests made by City Council and its committees. The log is intended for reference and convenience purposes.

What you'll see in the log

Report requests adopted by City Council and its committees and the Board of Health

Exceptions

The following report requests are not included in the log:

Committee requests for reports directly to Council for consideration with an agenda item.
Report requests made by the Budget Committee for briefing notes/reports to itself during the Budget process.
Report requests adopted by other Boards supported by the City Clerk's Office Secretariat.

How requests are logged

Requests for reports adopted on the same item are generally logged individually, as different staff or timelines may apply. Except where a directive is clear, a request for a report "to Council" means a report through the usual legislative process – the appropriate Committee.

When reports are due

The report back timing of requests is logged: - by specific date where indicated: YYYY-MM-DD; or

by the timeframe where indicated. For example "Q2 2019"; "by the end of 2020"; "annually".

If the request does not include a report back date, the timing will be logged as "not indicated".

Status of Report Requests - Open - When a report request is adopted by committee or Council. - Closed - When staff determine that the report request has been addressed by a subsequent agenda item. A link to the "closing" item is included in the status column of the log. - Due - When the report back timing has been reached and no report has been submitted. - Ongoing - When the report back timing is ongoing. - Not carried forward (NCF) - outstanding report requests are not carried forward to the next term report log.

Keeping the Log Up to Date

The City Clerk's Office updates the log at the end of each meeting cycle. Staff can contact if a report status needs to be updated or corrected.

Datasets available for download

Additional Info

Field	Value
Last Updated	October 4, 2024, 04:48 (UTC)
Created	October 4, 2024, 02:37 (UTC)
Domain / Topic Domain or topic of the dataset being cataloged.	City government
Description A description of the dataset.	The City Clerk's Office maintains a log of report requests made by City Council and its committees. The log is intended for reference and convenience purposes. What you'll see in the log Report requests adopted by City Council and its committees and the Board of Health Exceptions The following report requests are not included in the log: Committee requests for reports directly to Council for consideration with an agenda item. Report requests made by the Budget Committee for briefing notes/reports to itself during the Budget process. Report requests adopted by other Boards supported by the City Clerk's Office Secretariat. How requests are logged Requests for reports adopted on the same item are generally logged individually, as different staff or timelines may apply. Except where a directive is clear, a request for a report "to Council" means a report through the usual legislative process – the appropriate Committee. When reports are due The report back timing of requests is logged: - by specific date where indicated: YYYY-MM-DD; or by the timeframe where indicated. For example "Q2 2019"; "by the end of 2020"; "annually". If the request does not include a report back date, the timing will be logged as "not indicated". Status of Report Requests - Open - When a report request is adopted by committee or Council. - Closed - When staff determine that the report request has been addressed by a subsequent agenda item. A link to the "closing" item is included in the status column of the log. - Due - When the report back timing has been reached and no report has been submitted. - Ongoing - When the report back timing is ongoing. - Not carried forward (NCF) - outstanding report requests are not carried forward to the next term report log. Keeping the Log Up to Date The City Clerk's Office updates the log at the end of each meeting cycle. Staff can contact if a report status needs to be updated or corrected.
Format (CSV, XLS, TXT, PDF, etc) File format of the dataset.	.xlsx - application/vnd.openxmlformats-officedocument.spreadsheetml.sheet, .pdf - application/pdf
Dataset Size Dataset size in megabytes.
Metadata Identifier Metadata identifier – can be used as the unique identifier for catalogue entry
Published Date Published date of the dataset.	2019-10-31
Time Period Data Span (start date) Start date of the data in the dataset.
Time Period Data Span (end date) End date of time data in the dataset.
GeoSpatial Area Data Span A spatial region or named place the dataset covers.

Field	Value
Access category Type of access granted for the dataset (open, closed, service, etc).
License License used to access the dataset.	License not specified
Limits on use Limits on use of data.
Location Location of the dataset.	https://open.toronto.ca/dataset/report-request-log-city-council-and-its-committees
Data Service Data service for accessing a dataset.
Owner Owner of the dataset.	City Clerk's Office, clerk@toronto.ca
Contact Point Who to contact regarding access?
Contact Point Email The email to contact regarding access?
Publisher Publisher of the dataset.
Publisher Email Email of the publisher.	clerk@toronto.ca
Author Author of the dataset.	clerk@toronto.ca
Author Email Email of the author.	clerk@toronto.ca
Accessed At Date the data and metadata was accessed.

Field	Value
Identifier Unique identifier for the dataset.
Language Language(s) of the dataset
Link to dataset description A URL to an external document describing the dataset.
Persistent Identifier Data is identified by a persistent identifier.
Globally Unique Identifier Data is identified by a persistent and globally unique identifier.
Contains data about individuals Does the data hold data about individuals?
Contains data about identifiable individuals Does the data hold identifiable data about individual?
Contains Indigenous Data Does the data hold data about Indigenous communities?

Field	Value
Source Source of the dataset.	www.toronto.ca/council
Version notes Version notes about the dataset.
Is version of another dataset Link to dataset that it is a version of.
Other versions Link to datasets that are versions of it.
Provenance Text Provenance Text of the data.
Provenance URL Provenance URL of the data.
Temporal resolution Describes how granular the date/time data in the dataset is.
GeoSpatial resolution in meters Describes how granular (in meters) geospatial data is in the dataset.
GeoSpatial resolution (in regions) Describes how granular (in regions) geospatial data is in the dataset.

Field	Value
Indigenous Community Permission Who holds the Indigenous Community Permission. Who to contact regarding access to a dataset that has data about Indigenous communities.
Community Permission Community permission (who gave permission).
The Indigenous communities the dataset is about Indigenous communities from which data is derived.

Field	Value
Number of data rows If tabular dataset, total number of rows.
Number of data columns If tabular dataset, total number of unique columns.
Number of data cells If tabular dataset, total number of cells with data.
Number of data relations If RDF dataset, total number of triples.
Number of entities If RDF dataset, total number of entities.
Number of data properties If RDF dataset, total number of unique properties used by the triples.
Data quality Describes the quality of the data in the dataset.
Metric for data quality A metric used to measure the quality of the data, such as missing values or invalid formats.

Report Request Log – City Council and its Committees

Datasets available for download

Additional Info

0 Comments

Please login or register to comment.