Metadata - Analysis and Inventories
 Share
The version of the browser you are using is no longer supported. Please upgrade to a supported browser.Dismiss

 
View only
 
 
ABCDEFGHIJKLMNOPQRSTUVWXYZAA
1
PortalField LabelRequired?
Conditional Requirement
Definition/InstructionsPermitted values
2
Project Open Data
3
Project Open DatatitleTitleRequired
Human-readable name of the asset. Should be in plain English and include sufficient detail to facilitate search and discovery. Avoid acronyms
String
4
Project Open DatadescriptionDescriptionRequired
Human-readable description (e.g., an abstract) with sufficient detail to enable a lay user to quickly understand whether the asset is of interest.
String
5
Project Open DatakeywordTagsRequired
Tags (or keywords) help users discover your dataset; please include terms that would be used by technical and non-technical users.
6
Project Open DatamodifiedLast UpdateRequired
Most recent date on which the dataset was changed, updated or modified.
ISO 8601: YYYY-MM-DDThh:mm:ss.s (as much as is relevant to the dataset) or, to reflect continual updating, ISO has duration standards like P1D for daily and P2W for every two weeks
7
Project Open DatapublisherPublisherRequiredThe publishing entity.String
8
Project Open DatacontactPointContact NameRequiredContact person’s name for the asset.String (First Last)
9
Project Open DatamboxContact EmailRequiredContact person’s email address.email address
10
Project Open DataidentifierUnique IdentifierRequired
A unique identifier for the dataset or API as maintained within an Agency catalog or database.
Alphanumeric; up to agencies, but must be unique
11
Project Open DataaccessLevelPublic Access LevelRequired
The degree to which this dataset could be made publicly-available, regardless of whether it has been made available. Choices: public (Data asset is or could be made publicly available to all without restrictions), restricted public (Data asset is available under certain use restrictions), or non-public (Data asset is not available to members of the public)
“public”, “restricted public”, “non-public”
12
Project Open DatabureauCodeBureau CodeRequired-if
Publisher is a federal agency
Federal agencies, combined agency and bureau code from OMB Circular A-11, Appendix C in the format of 015:11.
Array of strings ("agency code1:bureau code1" , "agencycode2:buraucode2"
13
Project Open DataprogramCodeProgram CodeRequired-if
Publisher is a federal agency
Federal agencies, list the primary program related to this data asset, from the Federal Program Inventory. Use the format of 015:001
Array of strings (references federal program inventory)
14
Project Open Data
accessLevelComment
Access Level CommentRequired-if
Access Level is not "public"
An explanation for the selected “accessLevel” including instructions for how to access a restricted file, if applicable, or explanation for why a “non-public” or “restricted public” data asset is not “public,” if applicable. Text, 255 characters.
String
15
Project Open DataaccessURLDownload URLRequired-if
File is available for public download
URL providing direct access to the downloadable distribution of a dataset. Not for landing/disambiguation pages
URL
16
Project Open DatawebServiceEndpointRequired-if
Dataset has an API
Endpoint of web service to access dataset.URL
17
Project Open DataformatFormatRequired-if
File is available for public download
The file format or API type of the distribution.
String using MIME types (http://www.iana.org/assignments/media-types/media-types.xhtml)
18
Project Open DatalicenseLicenseRequired-if
Unclear - if the dataset is licensed?
The license with which the dataset or API is published. See Open Licenses for more information.
http://opendefinition.org/licenses/
19
Project Open DataspatialSpatialRequired-if
Dataset is spatial
The range of spatial applicability of a dataset. Could include a spatial region like a bounding box or a named place.
Latitude/longitude or a geographic feature from Geography Markup Language http://www.ogcnetwork.net/gml-sf or the GeoNames database http://www.geonames.org/
20
Project Open DatatemporalTemporalRequired-if
If there is a defined range of applicability
The range of temporal applicability of a dataset (i.e., a start and end date of applicability for the data).
start and end date interval using ISO 8601. ISO has options to clarify that the dataset is continually updated in a certain date range
21
Project Open DatathemeCategoryExpandedMain thematic category of the dataset.
Array of strings. May use ISO Topic Categories
22
Project Open DatadataDictionaryData DictionaryExpanded
URL to the data dictionary for the dataset or API. Note that documentation other than a data dictionary can be referenced using Related Documents as shown in the expanded fields.
URL
23
Project Open DatadataQualityData QualityExpanded
Whether the dataset meets the agency’s Information Quality Guidelines (true/false).
boolean, true or false
24
Project Open DatadistributionDistributionExpanded
Holds multiple download URLs for datasets composed of multiple files and/or file types
access URL and format (separate entries if multiple datasets)
25
Project Open DataaccrualPeriodicityFrequencyExpandedFrequency with which dataset is published.
“Annual”,”Bimonthly”,”Semiweekly”,”Daily”,”Biweekly”,”Semiannual”,”Biennial”,”Triennial”,”Three times a week”,”Three times a month”,”Continuously updated”,”Monthly”,”Quarterly”,”Semimonthly”,”Three times a year”,”Weekly”,”Completely irregular”
26
Project Open DatalandingPageHomepage URLExpanded
Alternative landing page used to redirect user to a contextual, Agency-hosted “homepage” for the Dataset or API when selecting this resource from the Data.gov user interface.
URL
27
Project Open DatalanguageLanguageExpandedThe language of the dataset.
Array of strings using RFC 5646 standard (en-US)
28
Project Open Data
PrimaryITInvestmentUII
Primary IT Investment UII
Expanded
For linking a dataset with an IT Unique Investment Identifier (UII)
numeric - given in federal documents
29
Project Open DatareferencesRelated DocumentsExpanded
Related documents such as technical information about a dataset, developer documentation, etc.
URL or multiple URLs
30
Project Open DataissuedRelease DateExpandedDate of formal issuance.
ISO 8601: YYYY-MM-DDThh:mm:ss.s - as much as is relevant to the dataset
31
Project Open DatasystemOfRecordsSystem of RecordsExpanded
If the systems is designated as a system of records under the Privacy Act of 1974, provide the URL to the System of Records Notice related to this dataset.
URL
32
Project Open DatagranularityRemoved
33
Project Open DatasizeRemoved
34
Project Open DatafeedRemoved
35
Albuquerque
36
AlbuquerqueName
Contact Information: Who is the contact for this dataset? The contact will be the City employee who is accountable for the data provided in this dataset and can act as front-line support in the event of any questions about the data.
37
AlbuquerqueDepartment/Division
Contact Information: Who is the contact for this dataset? The contact will be the City employee who is accountable for the data provided in this dataset and can act as front-line support in the event of any questions about the data.
38
AlbuquerquePhone
Contact Information: Who is the contact for this dataset? The contact will be the City employee who is accountable for the data provided in this dataset and can act as front-line support in the event of any questions about the data.
39
AlbuquerqueEmail
Contact Information: Who is the contact for this dataset? The contact will be the City employee who is accountable for the data provided in this dataset and can act as front-line support in the event of any questions about the data.
40
AlbuquerqueDataset Title
What Does this Dataset Describe? What is the name of this dataset? How should a user identify this dataset in any communication with contact above?
41
AlbuquerqueShort Description
What Does this Dataset Describe? Provide a shorter description of the Dataset that can act as a one-line summary of the dataset when dealing with stakeholders.
42
Albuquerque
Full Non-Technical Description
What Does this Dataset Describe? Provide a longer description of the data that can be readily understood by non-technical users.
43
Albuquerque
How Should this Dataset be Cited?
How should external sources refer to this dataset in publications or documentation? Often this will simple be the URL and the date retrieved.
44
AlbuquerqueStart Date
Start date of the time period within which this data falls.
MM/DD/YYYY HH:MM:SS
45
AlbuquerqueEnd Date
End date of the time period within which this data falls.
MM/DD/YYYY HH:MM:SS
46
Albuquerque
Dataset Refresh Interval
Time period between Dataset refreshes.
"nn [seconds|minutes|hours|days|weeks|months|years]" or "Static"
47
AlbuquerqueData Expiration Date
Date after which the data must be considered stale and no longer of sufficient utility (fit-for-purpose).
MM/DD/YYYY HH:MM:SS
48
AlbuquerqueDataset Review Date
Date after which this dataset will be reviewed by the City for utility (fit-for-purpose) and usage.
MM/DD/YYYY HH:MM:SS
49
AlbuquerqueComments
Specific comments related to any time-specific features of this dataset.
50
Albuquerque
Dataset Definition/Format
Provide a field-by-field breakdown and definition of each record. This section acts as the formal data dictionary for an individual record.
51
Albuquerque
Dataset Technical Description
Provide a technical description of the dataset. This should be a complete technical description aimed at developers and expert users who need to understand the scope, strengths and limitations of the dataset.
52
AlbuquerqueDataset Assumptions
What technical and business assumptions are implied in the creation of this dataset? Examples could include the way in which a salary figure was calculated or data that was omitted for specific reasons.
53
Albuquerque
Who Produced the Dataset?
Which department in the City produced this dataset? Note that this might not always be the data owner.
54
Albuquerque
Who Manages the Data?
Where did this data originate? Who manages the data used in this dataset? Note that this might not always be the dataset producer.
55
Albuquerque
Why was the Dataset Created?
All datasets should have an explicit reason for existence and should, somehow, have value to someone. What is the perceived value that this dataset will bring?
56
Albuquerque
How was the Dataset Created?
How was this dataset produced? Was it a manual process? An automated process? What were the main IT systems involved in producing this dataset?
57
Albuquerque
What Similar or Related Data Should the User be Aware of?
Are there any other datasets available that may contain related or similar information? Might there be situations in which these other datasets might be a better alternative?
58
Albuquerque
How Reliable are the Data?
Are there any concerns about overall data reliability? Are there any data problems that the user needs to be aware of? Are there any constraints with data accuracy? What levels of confidence with this dataset could the user reasonably assume?
59
Albuquerque
How Well Have the Observations Been Checked?
What quality assurance steps have been performed? Sometimes, a third - party verification/audit process may also be required. If so, provide the name of the third - party who performed the verification.
60
Albuquerque
Are there Legal Restrictions on the Access or Use of the Data?
Are there any specific legal or compliance restrictions for this data? How might this affect the way in wh ich end users might access and use this data?
61
AlbuquerqueLegal DisclaimerUniform - see "permitted"
The City's standard copyright, disclaimers and legal statements may be found at http://www.cabq.gov/about/legal. The City data policy governing data.cabq.gov may be found at http://data.cabq.gov/policy/.
62
New York City
63
New York CityContributorRequiredIndicates the agency that supplied the data.
64
New York CityCoverageRequired
Indicates the range of data from either a temporal or spatial perspective.
65
New York CityCreatorRequiredIndicates the agency that supplied the data.
66
New York CityDateRequired
Auto-generated by Socrata when data set (or metadata) is modified.
67
New York CityDescriptionRequiredA brief description of the data set.
68
New York CityFormatRequired
Dependent upon export methodology. Refer to Public Standards for more information.
69
New York CityFrequencyRequired
Indicates the rate at which the information in the data set is updated.
DCCD Vocab: Not updated [historical only], Annual, Quarterly, Bi-monthly, Monthly, Bi-weekly, Weekly, Daily, Hourly, Continuous
70
New York CityIdentifierRequired
Socrata uses a 9-digit identifier (usually xxxx-xxxx); may have the option for better permalinking under the "resource name" field.
71
New York CityLanguageRequired
Language of the data set. Assumed to be en-US for all data sets. Exceptions must be noted.
en-US
72
New York CityPublisherRequired
Entity that is responsible for publishing the data; this will always be the City of New York.
City of New York
73
New York CityRelationRequiredNot used.
74
New York CityRightsRequired
NYC data sets should be attributed to the City. Refer to Public Policies.
75
New York CitySourceRequired
Identifies the name of the source system within the City.
76
New York CitySubjectRequired
Comma-separated list of nouns describing the content of the data set.
77
New York CityTitleRequiredThe brief descriptive name of the data set.
78
New York CityTypeRequired
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.
NYC's categories - note that these don't line up with the categories on their homepage?
79
New York CityColumn Metadata
No label for column metadata
Expanded
80
New York CityCitation Standard
no data for citation standards
Expanded
81
Seattle
82
SeattleDataset title
83
SeattleKeyword
About:<Key words for use in a search for data like parks, streets, transportation, etc.>
84
SeattleAbstract
Provide a short descriptive narrative about the dataset.
85
SeattlePurpose
Departmental first line point of contact. This is usually the departmental PIO or delegate and serves as triage for incoming questions. The business owner/technical owner would be second point of contact for a specific dataset.
This dataset has been published by <department name> of the City of Seattle and data.seattle.gov. The mission of data.seattle.gov is to provide timely and accurate City information to increase government transparency and access to useful and well organized data by the general public, non-governmental organizations, and City of Seattle Employees
86
SeattleAccess constraints
Departmental first line point of contact. This is usually the departmental PIO or delegate and serves as triage for incoming questions. The business owner/technical owner would be second point of contact for a specific dataset.
The data is publicly available and accessible.
87
SeattleUse constraints
Departmental first line point of contact. This is usually the departmental PIO or delegate and serves as triage for incoming questions. The business owner/technical owner would be second point of contact for a specific dataset.
A link to the terms and conditions, data policy, as well as a couple paragraphs of disclaimer
88
SeattleDepartment
Departmental first line point of contact. This is usually the departmental PIO or delegate and serves as triage for incoming questions. The business owner/technical owner would be second point of contact for a specific dataset.
89
SeattleName
Departmental first line point of contact. This is usually the departmental PIO or delegate and serves as triage for incoming questions. The business owner/technical owner would be second point of contact for a specific dataset.
90
SeattleBusiness phone
Departmental first line point of contact. This is usually the departmental PIO or delegate and serves as triage for incoming questions. The business owner/technical owner would be second point of contact for a specific dataset.
91
SeattleMailing address
Departmental first line point of contact. This is usually the departmental PIO or delegate and serves as triage for incoming questions. The business owner/technical owner would be second point of contact for a specific dataset.
92
SeattleFax number
Departmental first line point of contact. This is usually the departmental PIO or delegate and serves as triage for incoming questions. The business owner/technical owner would be second point of contact for a specific dataset.
93
SeattleBusiness hours
Departmental first line point of contact. This is usually the departmental PIO or delegate and serves as triage for incoming questions. The business owner/technical owner would be second point of contact for a specific dataset.
94
SeattleCredits
City of Seattle Office of the Chief Technology Officer (OCTO), data.seattle.gov staff
95
SeattleDistribution
Same as use constraints, oddly.
96
SeattleDistributed by
City of Seattle Office of the Chief Technology Officer (OCTO), data.seattle.gov staff
97
SeattleEntityTitle of dataset
98
SeattleAttributes
Provide a complete list of all columns in the dataset, the datatype for each column, and a description in plain English of what the column values represent
99
SeattleProvided by
Metadata provided by <name/department>
100
Canada
Loading...
Main menu