Reference
Schema
Fields of the profile
Catalog (catalog
)
Name | Required | Description | Example | Variable | Type |
---|---|---|---|---|---|
Identifier | R | It's a unique identifier of the catalog inside the open data catalog network where it belongs. This identifier can be granted by the area in charge of open data policy of a country to its organisms, or established following any international convention in the case of catalogs of national jurisdiction hierarchy. The identifier must be one or more words in lower case, separated by "-", without using special characters. Identifies the catalog in a short and declarative way. | "energy" "justice" "argentina" "mexico" | identifier | String |
Title | Yes | Name given to the catalog. Should be clear, short and abstract enough to include the diversity of datasets contained. | Argentina's Data | title | String |
Description | Yes | Description of catalog contents. | Open Data Portal of Argentina's National Administration. | description | String |
Author | Yes | Responsibile authority of catalog publication. | Ministry of Modernization | publisher -> name | String |
Author e-mail | Yes | Responsibile authority of catalog publication e-mail. | datos@modernizacion.gob.ar | publisher -> mbox | String |
Datasets | Yes | List of datasets of the catalog. | [{...}, {...}] | dataset | Array |
Date of creation or publication | R | Date of creation or publication of the catalog. It's written following ISO-8601 format, using either the complete forme (date and time) or only the date part. | "2016-04-14T19:48:05.433640" specifies date and time "2016-04-14" specifies date only | issued | String |
Date of last modification or update of data or metadata | R | Date of last modification or update of any data or metadata in the catalog. It's written following ISO-8601 format, using either the complete forme (date and time) or only the date part. | "2016-04-14T19:48:05.433640" specifies date and time "2016-04-14" specifies date only | modified | String |
Date of last modification or update of data | No | Date of last modification or update of any data in the catalog. It's written following ISO-8601 format, using either the complete forme (date and time) or only the date part. | "2016-04-14T19:48:05.433640" specifies date and time "2016-04-14" specifies date only | dataModified | String |
Date of last modification or update of metadata | No | Date of last modification or update of any metadata in the catalog. It's written following ISO-8601 format, using either the complete forme (date and time) or only the date part. | "2016-04-14T19:48:05.433640" specifies date and time "2016-04-14" specifies date only | metadataModified | String |
Languages | R | Language(s) for metadata in this catalog. There are 2 ISO standards that can be used in this field: (a) ISO 639-1 (2 letters as "en" or "es") (b) ISO 639-2/T (3 letters as "eng" or "esp" - this is the most recommended one) 1 or more languages can be defined in the list. (Link to ISO standards: https://www.loc.gov/standards/iso639-2/php/code_list.php) | ["es"] for a language in ISO 639-1 ["spa", ”eng"] for two languages in ISO 639-2 | language | Array |
Theme taxonomy | R | Is the system of theme classification, created by the organization responsible of the catalog. Defines a list of themes that can be used to classify datasets in this catalog. If there is at least one dataset classified as having one or more themes in the catalog, this metadata field is mandatory because it is neccessary to make explicit the theme taxonomy available to use a theme for a dataset. For national catalogs, or others that have a broad variety datasets of different themes, it is recommended to use the European Union theme taxonomy (see standards/themeTaxonomy in the repository). This taxonomy has 13 general themes, under wicho any dataset can be classified. Nevertheless, some countries could prefer to develop a more detailed theme taxonomy, with more specific themes. | [{...}, {...}] | themeTaxonomy | Array |
License | R | License under wich all datasets and distributions are available to use. This should be a link to the selected license defined in the web or the specific strings that acts as a title as it appears in the Open Definition list of licenses (https://licenses.opendefinition.org/). It is recommended using "Creative Commons 4.0" as it covers data and contents, and is available in English and Spanish. A dataset or distribution specifying a different license, overwrites the general license of the catalog. | "https://creativecommons.org/licenses/by/4.0/" if using a link "Creative Commons 4.0" if using the name of the license | license | String |
Catalog web site | R | Access URL to the landing page of the catalog, if any. | http://datos.gob.ar | homepage | String |
Metadata schema version | R | Is the metadata scheme version used in the catalog. It should be used for applications to recongize and validate metadata of this catalog, and be able to safely build functionality upon a certain metadata scheme they can trust. | 1.0 | metadataSchemeVersion | String |
Spatial coverage | No | Is the spatial area covered by the catalog. This can be expressed using very different standards. It is recommended to develop a guide of territorial and administrative units specific to the country that manages the catalog, where official codes are used to express spatial coverage. A certain region or place. Can have different values: a) of countries, provinces, departments, counties, municipalities or cities, under the recommendations of the guide of territorial and administrative units of the country that is managing the catalog. b) an area of coordinates (or bounding box) represented by latitude / longitude in this order: minimum longitude, minimum latitude, maximum longitude, maximum latitude. c) a geographical point represented by latitude / longitude. d) if the geographical reference is not included in the official guide of territorial and administrative units of the country, can be referenced using a geonames URI from geonames.org as: http://sws.geonames.org/6255146 | "ARG" is the code for Argentina. "06007" is the official code of a "department" in Argentina [-58.111111, -35.111111, -57.111111, -33.111111] it's a bounding box [-58.111111, -35.111111] it's a geographical point "http://sws.geonames.org/6255146" | spatial | String or Array |
Additional rights or terms and conditions of the catalog | No | Information about additional rights or terms or conditions applyable to the catalog, in case they are not covered by the license. Datasets and distributions inherit this additional terms, unless different terms are specified in particular cases. | nan | rights | String |
Dataset (dataset
)
Name | Required | Description | Example | Variable | Type |
---|---|---|---|---|---|
Identifier | Yes | Unique identifier of the dataset. This identifier has to be unique inside the whole catalog. | "dataset-example-35782” | identifier | String |
Title | Yes | Name assigned to the dataset as it will be published. It must be clear, precise but general enough to include the distributions it contains. It is recommended not to exceed 100 characters, in most cases. | System of Electronic Contracts | title | String |
Description | Yes | Descriptions of the contents of the datasets, in a clear and precise way. It is recommended not to exceed 500 characters, in most cases. | Data about the System of Electronic Contracts ("Argentine Buys") | description | String |
Author | Yes | Authority responsible of dataset publication. It is recommended the adoption of a controlled vocabulary of the organizations of the country or national administration in charge of the catalog. Also a way of expressing hiearchy should be defined (ie.: using dots or "-" to separate hierarchical levels, express them ascending or descending way, etc.) | Ministry of Modernization. Secretary of Administrative Modernization. National Office of Contracts. | publisher -> name | String |
Author e-mail | R | Responsibile authority of dataset publication e-mail. | onc@modernizacion.gob.ar | publisher -> mbox | String |
Point of contact | R | Area or person acting as a point of contact that can bring relevant information of the dataset to a user. This should be te closest point of contact to the operation and maintainment of the dataset. | Ministerio de Modernización. Secretaría de Modernización Administrativa. Oficina Nacional de Contrataciones. Dirección de Compras Electrónicas. | contactPoint -> fn | String |
Point of contact e-mail | R | E-mail of the area or person acting as a point of contact that can bring relevant information of the dataset to a user. | onc-compraselectronicas@modernizacion.gob.ar | contactPoint -> hasEmail | String |
Primary or original source | No | Original or primary sources of data published in the dataset. It should be used when the publisher authority of the dataset it is not the one producing the data originally. | Ministerio de Hacienda. Instituto Nacional de Estadísticas y Censos. Dirección Nacional de Cuentas Nacionales. | attribution | String |
Collaborators | No | Entities, organizations or additional persons that are or were responsible of collecting, creating or contributing in any way in developing the data asset. Values should be separated by commas ",". | Argentine Institute for Fiscal Analysis | contributor | String |
Distributions | Yes | List of distributions contained in the dataset and their metadata. Each distribution is an object ("{}") where its metadata is described following "Distribution" class metadata fields. | [{...}, {...}] | distribution | Array |
Themes | R | Theme/s or categories of which this dataset has data about. A dataset can be classified with one or multiple themes, so this metadata field is a list of themes or categories. The available list of themes to use here is the theme taxonomy defined by the authority behind the catalog. The ids of the themes must be used here (see "id" of Theme class). Labels and descriptions of the themes, must not be used. | ["gove", "econ"] | theme | Array |
Date of creation or publication | Yes | Date of creation or publication of the dataset. It's written following ISO-8601 format, using either the complete forme (date and time) or only the date part. | "2016-04-14T19:48:05.433640" specifies date and time "2016-04-14" specifies date only | issued | String |
Date of last modification or update of data or metadata | R | Date of last modification or update of any data or metadata in the dataset. It's written following ISO-8601 format, using either the complete forme (date and time) or only the date part. | "2016-04-14T19:48:05.433640" specifies date and time "2016-04-14" specifies date only | modified | String |
Date of last modification or update of data | R | Date of last modification or update of any data in the dataset. It's written following ISO-8601 format, using either the complete forme (date and time) or only the date part. | "2016-04-14T19:48:05.433640" specifies date and time "2016-04-14" specifies date only | dataModified | String |
Date of last modification or update of metadata | R | Date of last modification or update of any metadata in the dataset. It's written following ISO-8601 format, using either the complete forme (date and time) or only the date part. | "2016-04-14T19:48:05.433640" specifies date and time "2016-04-14" specifies date only | metadataModified | String |
Updating frequency | Yes | Frequency in which responsibles update the dataset. It is recommended to use normalized periods following ISO-8601 format, adding the value “eventual” for datasets that are updated in a non regular basis. See annex "Frequencies specification under ISO-8601". | “R/P1Y” for datasets yearly updated | accrualPeriodicity | String |
Landing page | R | URL of the webpage where dataset, its resources, reports or any additional information of it can be accessed. | http://datos.gob.ar/dataset/sistema-de-contrataciones-electronicas-argentina-compra | landingPage | String |
Tags | R | Words describing title or content of the resource. It is neccesary that tags are well written, in plural and keeping an eye of previous tags. Tags are useful por users search. The longer and homogeneous is the list of tags, their efficiency will be better. See annex of “Guidelines for tags selection”. | ["goods", "contracts", "services"] | keyword | Array |
Temporal coverage | R | Time period covered by the dataset. The time period has an initial date and an end date, separated by "/", written in ISO 8601 format using only date part or date & time depending on the precission needed. Optionally, a single date can be specified (instead of two) and this one will be interpreted as an initial date, while the end date will remain unspecified (useful for datasets that are chronologically updated). | 2015-01-01/2015-12-31 2015-01-01T00:45:00Z/2016-01-15T00:06:00Z 2015-01-01 2015-01-01T00:45:00Z | temporal | String |
License | R | License under wich this dataset and its distributions are available to use. This should be a link to the selected license defined in the web or the specific strings that acts as a title as it appears in the Open Definition list of licenses (https://licenses.opendefinition.org/). It is recommended using "Creative Commons 4.0" as it covers data and contents, and is available in English and Spanish. A distribution specifying a different license, overwrites the license of this dataset. | "https://creativecommons.org/licenses/by/4.0/" if using a link "Creative Commons 4.0" if using the name of the license | license | String |
Languages | No | Language(s) for metadata in this dataset. There are 2 ISO standards that can be used in this field: (a) ISO 639-1 (2 letters as "en" or "es") (b) ISO 639-2/T (3 letters as "eng" or "esp" - this is the most recommended one) 1 or more languages can be defined in the list. (Link to ISO standards: https://www.loc.gov/standards/iso639-2/php/code_list.php) | ["es"] for a language in ISO 639-1 ["spa", ”eng"] for two languages in ISO 639-2 | language | Array |
Spatial coverage | No | Is the spatial area covered by the dataset. This can be expressed using very different standards. It is recommended to develop a guide of territorial and administrative units specific to the country that manages the catalog, where official codes are used to express spatial coverage. A certain region or place. Can have different values: a) of countries, provinces, departments, counties, municipalities or cities, under the recommendations of the guide of territorial and administrative units of the country that is managing the catalog. b) an area of coordinates (or bounding box) represented by latitude / longitude in this order: minimum longitude, minimum latitude, maximum longitude, maximum latitude. c) a geographical point represented by latitude / longitude. d) if the geographical reference is not included in the official guide of territorial and administrative units of the country, can be referenced using a geonames URI from geonames.org as: http://sws.geonames.org/6255146 | "ARG" is the code for Argentina. "06007" is the official code of a "department" in Argentina [-58.111111, -35.111111, -57.111111, -33.111111] it's a bounding box [-58.111111, -35.111111] it's a geographical point "http://sws.geonames.org/6255146" | spatial | Array or String |
Hierarchy, order or jurisdictional level | No | Classifies a dataset by hierarchy, order or jurisdictional level. Indicates type and scope of legal jurisdiction behind dataset publication. Values of this metadata can be "national" or "territorial" (covering national level as one case, and all sub-national levels as the other case), or belong to an alternative controlled vocabulary defined by the country or organization responsible for the open data policy (ie.: "federal", "provincial" o "municipal"). | "national" "territorial" | jurisdiction | String |
Distribution (distribution
)
Name | Required | Description | Example | Variable | Type |
---|---|---|---|---|---|
Identifier | Yes | Unique identifier of the distribution. This identifier must be unique within the catalog. The identifier should use lower or upper letter from "a" to "z" without using special characters (no accents and no "ñ"), numbers, underscores "_", hypens "-" and dots ".". | 1.2 | identifier | String |
Dataset identifier | Yes | Unique identifier of the dataset where this distribution belongs. | "dataset-example-35782” | datasetIdentifier | String |
Title | Yes | Name assigned to the distribution. | Contracts open in 2015 | title | String |
Description | R | Short description of the distribution. It is recommended not writing more than one line. Any other additional information can be included in the description. | List of contracts that were open during 2015 in the System of Electronic Contracts. | description | String |
Download URL | Yes | URL that allows direct download of the distribution Links directly to a downloadable file of a certain format. | http://datos.gob.ar/dataset/becaceb2-dbd0-4879-93bd-5f02bd3b8ca2/resource/bf2f67f4-9ab3-479b-a881-56b43565125e/download/contratos-2015.csv | downloadURL | String |
Access URL | Yes | URL that allows access to the distribution, through a web site, feed or other resource giving indirect access to the resource. If distributions are only accessible through the landing page of the dataset, this metadata field must be completed with the same value as the dataset landing page. | http://datos.gob.ar/dataset/sistema-de-contrataciones-electronicas-argentina-compra/archivo/fa3603b3-0af7-43cc-9da9-90a512217d8a | accessURL | String |
Fields of the distribution | R | List of fields that a tabular distribution contains (it doesn't apply to non tabular distributions) and its metadata. Each field is represente by an object ("{}") where metadata of the Field class are specified. | [{...}, {...}] | field | Array |
Date of creation or publication | Yes | Date of creation or publication of the distribution or resource. It's written following ISO-8601 format, using either the complete forme (date and time) or only the date part. | "2016-04-14T19:48:05.433640" specifies date and time "2016-04-14" specifies date only | issued | String |
Date of last modification or update of data or metadata | R | Date of last modification or update of any data or metadata in the distribution or resource. It's written following ISO-8601 format, using either the complete forme (date and time) or only the date part. | "2016-04-14T19:48:05.433640" specifies date and time "2016-04-14" specifies date only | modified | String |
Date of last modification or update of data | R | Date of last modification or update of any data in the distribution or resource. It's written following ISO-8601 format, using either the complete forme (date and time) or only the date part. | "2016-04-14T19:48:05.433640" specifies date and time "2016-04-14" specifies date only | dataModified | String |
Date of last modification or update of metadata | R | Date of last modification or update of any metadata in the distribution or resource. It's written following ISO-8601 format, using either the complete forme (date and time) or only the date part. | "2016-04-14T19:48:05.433640" specifies date and time "2016-04-14" specifies date only | metadataModified | String |
File format | R | Indicates the format of the file. If the type is defined by IANA (http://www.iana.org/assignments/media-types/media-types.xml), this definition can be used. In other case, the file extension (after the dot "." in the file name) should be used. | "text/csv" IANA definition "csv" file extension | format | String |
License | R | License under wich this distribution is available to use. This should be a link to the selected license defined in the web or the specific strings that acts as a title as it appears in the Open Definition list of licenses (https://licenses.opendefinition.org/). It is recommended using "Creative Commons 4.0" as it covers data and contents, and is available in English and Spanish. If the license was specified at the level of dataset, it is not neccessary to use this field unless a different license applies. | "https://creativecommons.org/licenses/by/4.0/" if using a link "Creative Commons 4.0" if using the name of the license | license | String |
File type | No | Indicates the type of file of the distribution, only if this one is defined by IANA (http://www.iana.org/assignments/media-types/media-types.xml). If not defined, this field should remain empty. | "text/csv" IANA definition "" when there is no IANA definition | mediaType | String |
Resource type | R | Indicates the type of resource. + "Data file" (file): physical file of a certain format that can be downloaded. + "API" (api): api web documentation URL, of data web service. + "Code" (code): scripting file or repository used for the generation, transformation, cleaning or validation of all or part of the data contained in the dataset. + "Documentation" (documentation): methodological documentation of all or part of the data in this dataset. | "file" | type | String |
Spatial coverage | No | Is the spatial area covered by the distribution. This can be expressed using very different standards. It is recommended to develop a guide of territorial and administrative units specific to the country that manages the catalog, where official codes are used to express spatial coverage. A certain region or place. Can have different values: a) of countries, provinces, departments, counties, municipalities or cities, under the recommendations of the guide of territorial and administrative units of the country that is managing the catalog. b) an area of coordinates (or bounding box) represented by latitude / longitude in this order: minimum longitude, minimum latitude, maximum longitude, maximum latitude. c) a geographical point represented by latitude / longitude. d) if the geographical reference is not included in the official guide of territorial and administrative units of the country, can be referenced using a geonames URI from geonames.org as: http://sws.geonames.org/6255146 | "ARG" is the code for Argentina. "06007" is the official code of a "department" in Argentina [-58.111111, -35.111111, -57.111111, -33.111111] it's a bounding box [-58.111111, -35.111111] it's a geographical point "http://sws.geonames.org/6255146" | spatial | String |
Temporal coverage | No | Time period covered by the distribution. The time period has an initial date and an end date, separated by "/", written in ISO 8601 format using only date part or date & time depending on the precission needed. Optionally, a single date can be specified (instead of two) and this one will be interpreted as an initial date, while the end date will remain unspecified (useful for datasets that are chronologically updated). | 2015-01-01/2015-12-31 2015-01-01T00:45:00Z/2016-01-15T00:06:00Z 2015-01-01 2015-01-01T00:45:00Z | temporal | String |
Additional rights or terms and conditions of the distribution | No | Information about additional rights or terms or conditions applyable to the distribution, in case they are not covered by the license or the addictional rights specified for the catalog don't apply. | nan | rights | String |
Size | No | Size of the file in bytes. Can be approximate if exact size is not known. | Example for a 5kb file: ”5120” | byteSize | Integer |
Standard codes | No | Names of standard codes, nomenclators or classifiers used ni the distribution. | ISO 8601 | codelists | String |
Standard codes documentation URLs | No | Links to official sources of the codes and standards used. | https://www.w3.org/TR/NOTE-datetime | codelistlink | String |
Field (field
)
Name | Required | Description | Example | Variable | Type |
---|---|---|---|---|---|
Title | R | Name of the field, exactly as it is used in the header of the distribution (inside the tabular file). It is recommended not to exceed 40 characters in most cases. In case that a longer title is neccessary or much more clear, this one must no exceed 60 characters in any case. Must use lower case letters from "a" to "z" without special characters (no accents and no "ñ"), numbers and underscores "_". | Ejemplo para el cuarto campo de la distribución "Convocatorias abiertas durante el año 2015", valor para el nombre: "unidad_operativa_contrataciones_desc" | title | String |
Type | R | Type of the data contained in the field following the list used by recline.js (http://okfnlabs.org/recline/docs/models.html#types). Types included in this list are: string (text): Text values. number (double, float, numeric): Numeric values including decimal values. integer (int): Numeric values that are always integer. date: Simple date expressed as in ISO 8601 standard including year, month and day only (YYYY-MM-DD) as in "2016-02-01". time: Time expressed as in ISO 8601 standard including only hours, minutes and seconds (hh:mm:ss) as in "10:05:00". date-time (datetime, timestamp): Complete datetime expressed as in ISO 8601 standard including year, month, day, hours, minutes and seconds (YYYY-MM-DDThh:mm:ssZ) as in "2016-02-01T10:05:00+03:00". boolean (bool): True or false values. binary: Representation of binary data in base64. geo_point: See structure in https://www.elastic.co/guide/en/elasticsearch/reference/current/geo-point.html. geojson: See in http://geojson.org/ array: List of values. object (json): JSON object. any: Field containing values of any type. | Ejemplo para el campo "unidad_operativa_contrataciones_desc" de la distribución "Convocatorias abiertas durante el año 2015", valor para tipo: "string" | type | String |
Description | R | Complete description of the information that the field contains. Must be precise and explicit enough so the data user understands how to use the data of this field. | Ejemplo para el campo "unidad_operativa_contrataciones_desc" de la distribución "Convocatorias abiertas durante el año 2015", valor para descripción: "Organismo que realiza la convocatoría. Organismo de máximo nivel jerárquico al que pertenece la unidad operativa de contrataciones." | description | String |
Units | No | Description of the unit of measure in which values are expressed. It is only used in numeric type fields. | Millones de pesos a precios de 1993 | units | String |
Spatial coverage | No | Is the spatial area covered by the field. This can be expressed using very different standards. It is recommended to develop a guide of territorial and administrative units specific to the country that manages the catalog, where official codes are used to express spatial coverage. A certain region or place. Can have different values: a) of countries, provinces, departments, counties, municipalities or cities, under the recommendations of the guide of territorial and administrative units of the country that is managing the catalog. b) an area of coordinates (or bounding box) represented by latitude / longitude in this order: minimum longitude, minimum latitude, maximum longitude, maximum latitude. c) a geographical point represented by latitude / longitude. d) if the geographical reference is not included in the official guide of territorial and administrative units of the country, can be referenced using a geonames URI from geonames.org as: http://sws.geonames.org/6255146 | "ARG" is the code for Argentina. "06007" is the official code of a "department" in Argentina [-58.111111, -35.111111, -57.111111, -33.111111] it's a bounding box [-58.111111, -35.111111] it's a geographical point "http://sws.geonames.org/6255146" | spatial | String |
Theme (theme
)
Name | Required | Description | Example | Variable | Type |
---|---|---|---|---|---|
Identifier | R | Theme unique identifier. | AGRI | id | String |
Title | R | Label or title of a theme. | Agriculture, fisheries, forestry and food | label | String |
Description | R | Short and precise description of the theme. | This concept identifies datasets covering such domains as agriculture, fisheries, forestry or food. | description | String |