Chattanooga: Draft Metadata Standard

	A	B	C	D	E	F	G	H	I	J	K
1	No.	Field	Field Set	Consensus	Condition	Discussion/Justification	Definition	Permitted values	Type of value	Existing	Comments on feedback

2	1	Title	Default Program	Required		Title helps discover and select datasets as well as differentiate between similar datasets.	Human-readable name of the asset. Should be in plain English and include sufficient detail to facilitate search and discovery. Avoid acronyms.	Text with character limit.	Open text	Yes	Will provide guidance to promote consistency in naming.
3	2	Description	Default Program	Required		Description helps discover and select datasets as well as differentiate between similar datasets.	What the dataset describes. Provide a longer description of the data that can be readily understood by non-technical users.	Text with character limit.	Open text	Yes	Will provide guidance to promote consistency and to address common questions.
4	3	Row Label	Default Program	Auto-generated
5	4	Category	Default Program	Required		Category provides a distinct navigation method and groups similar datasets together regardless of source	The category of the data set identified by the list of possible values. If a data set can fall into multiple categories, select the one which is most significant. This list will be subject to change on an ongoing basis.	Drop down menu: Economy Education Finance Public Safety Recreation Social Services Transportation	Drop down	Yes
6	5	Tags	Default Program	Optional		Tags provide a means to include technical language, secondary categories, and acronyms. While we want to encourage the use of tags, we don't believe it should be required as implementing a rigorous approach is too burdensome.	Tags (or keywords) help users discover your dataset; please include terms that would be used by technical and non-technical users.	Text	Simple text	Yes	Will provide guidance on how to use approrpiately.
7	6	License/Rights	Default Program	Required		A license reduces legal uncertainty for data consumers or users	The license with which the dataset or API is published.	Drop down menu: see comment	Drop down	Yes	Will provide depending on how many options are available; This may be the same for all datasets.
8	7	Source Link	Default Program	Auto-generated						Yes
9	8	Attachements	Default Program	Optional		Data dictionaries are essential to understanding how the data can be used, whether it is to understand fields, differences in fields, and assessing whether or not the data is appropriate for the intended use. However, we want to strike a balance between making it easy to publish and providing enough information for data users. The existing means of adding data dictionaries are either burdensome or clumsy. The implementation of this requirement must be flexible and provide sufficient guidance.	Data dictionary should explain the fields within the dataset in terms of their definition, type, size, and any other pertinent information that describes the dataset	TBD as part of metadata rollout.	Other	No	Will provide guidance on options to meet and complete this requirement (e.g. uploaded documents, inputs into Socrata, links to external resources/documents). Use attachments metadata field to upload if available.
10	9	Department	Internal	Required		Department name is needed for navigation and to ensure a single responsible department.	The department that collects and manages the data as the canonical source.	City Attorney Economic and Community Development Finance Fire Human Resources Information Technology Mayor's Office Police Public Library Public Works Purchasing Transportation Youth and Family Development	Drop down	Yes
11	9	Update Frequency - data change	Internal	Required		Together with the publishing frequency, this gives us an indication of our timeliness; It also gives data users insight into the rate of data change for planning and use.	Frequency with which dataset changes.	Daily Weekly Monthly Quarterly Yearly As Needed	Drop down	Yes	Will provide guidance on the difference between field 7 and 8
12	10	Dataset Sensitivity	Internal	Required - Private				Confidential - Not to be shared Private Only - Shared with specific teams and individuals Internal - Shared with all city employees Public - Ability to be shared with general public	Drop down
13	11	Data Steward name	Internal	Required - Private		We want to include internal contacts for each dataset to support the data coordinators and to answer dataset questions. However, we do not want this public as it limits our ability to track data questions and response times. In addition, this role contrasts with the data coordinator role, which will be the initial public contact point for department datasets.	Data Steward's name. Who manages the data and is responsible for making changes to the data? Who understands what the dataset includes and can answer questions about it?	String (First Last)	Simple text	No
14	12	Data Steward email	Internal	Required - Private		See previous field 15	Data Steward's email address.	Email address	Simple text	Yes
15	13	Results Areas	Internal	Optional				Growing Economy Smarter Students Stronger Families Stronger Neighborhoods Safer Streets High Performing Government
16	16	Public Contact	Public	Required				opendata@chattanooga.gov
17		Last updated	Default Program	Auto-generated		Last updated gives an indication of the recency of the data, which helps users determine if it is appropriate to use	Most recent date and time when the dataset was changed, updated or modified.	Auto generated by platform	Auto-generated	Yes
18		Unique Identifer	Default Program	Auto-generated		A unique dataset identifier is required for dataset management.	A unique identifier for the dataset or API as maintained within an Agency catalog or database.	Auto generated by platform	Auto-generated	Yes
19		Permalink/Identifier	Default Program	Auto-generated		A permalink helps provide continuity for accessing the dataset.	Persistent link to the dataset	Auto generated by platform	Auto-generated	Yes
20		Row Count	Default Program	Auto-generated	Required if automatically provided by platform.	Row count is a useful indicator of dataset size. However it is too burdensome to manually generate and update this.		Auto generated by platform	Auto-generated	Yes
21		Endpoint	Default Program	Auto-generated	Required if the dataset has an API or is an API	An API endpoint facilitates programmatic access to the data.	Endpoint of web service to access dataset.	Auto generated by platform	Auto-generated	Yes
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100