You are here:
Eionet
Data Dictionary
Edit vocabulary

Edit vocabulary

Folder Mandatory
Identifier Mandatory
Label Mandatory
Base URI Optional
Registration status Mandatory
Type Mandatory Common
Numeric concept identifiers Mandatory
Optional
Definition Optional
Version Optional
Source Optional
License Optional
 

Bound elements for concepts

Element Type Status
adms:status Vocabulary
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
01 Oct 2015
dct:isReplacedBy Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
08 Oct 2013
dct:replaces Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
08 Oct 2013
hasIdentifierScheme Vocabulary
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
29 Oct 2015
hasRelatedZone Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
08 Feb 2016
hasSpecialisedZoneType Vocabulary
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
03 Nov 2015
hasZoneType Vocabulary
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
18 Oct 2016
inCountry Vocabulary
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
29 Aug 2014

Add new data elements

Mandatory
Mandatory
Optional
Optional
 

Vocabulary concepts

729 concepts found, displaying 661 to 680.First3031323334353637Last
Id Label Status Status Modified Notation
euSubUnitCode.PTRH3 DOURO Quick edit Valid - stable 2019-09-10 PTRH3
euSubUnitCode.PTRH4 VOUGA, MONDEGO, LIS AND WEST RIVERS Quick edit Deprecated - superseded 2019-09-10 PTRH4
euSubUnitCode.PTRH4A VOUGA, MONDEGO AND LIS Quick edit Valid - stable 2019-09-10 PTRH4A
euSubUnitCode.PTRH5 TAGUS Quick edit Deprecated - superseded 2019-09-10 PTRH5
euSubUnitCode.PTRH5A TAGUS AND WEST RIVERS Quick edit Valid - stable 2019-09-10 PTRH5A
euSubUnitCode.PTRH6 SADO AND MIRA Quick edit Valid - stable 2019-09-10 PTRH6
euSubUnitCode.PTRH7 GUADIANA Quick edit Valid - stable 2019-09-10 PTRH7
euSubUnitCode.PTRH8 ALGARVE RIVERS Quick edit Valid - stable 2019-09-10 PTRH8
euSubUnitCode.PTRH9 AZORES Quick edit Valid - stable 2019-09-10 PTRH9
euSubUnitCode.RO1 ABA BANAT Quick edit Valid - stable 2019-09-10 RO1
euSubUnitCode.RO10 ABA SIRET Quick edit Valid - stable 2019-09-10 RO10
euSubUnitCode.RO11 ABA PRUT-BARLAD Quick edit Valid - stable 2019-09-10 RO11
euSubUnitCode.RO2 ABA JIU Quick edit Valid - stable 2019-09-10 RO2
euSubUnitCode.RO3 ABA OLT Quick edit Valid - stable 2019-09-10 RO3
euSubUnitCode.RO4 ABA ARGES-VEDEA Quick edit Valid - stable 2019-09-10 RO4
euSubUnitCode.RO5 ABA BUZAU-IALOMITA Quick edit Valid - stable 2019-09-10 RO5
euSubUnitCode.RO6 ABA DOBROGEA-LITORAL Quick edit Valid - stable 2019-09-10 RO6
euSubUnitCode.RO7 ABA MURES Quick edit Valid - stable 2019-09-10 RO7
euSubUnitCode.RO8 ABA CRISURI Quick edit Valid - stable 2019-09-10 RO8
euSubUnitCode.RO9 ABA SOMES-TISA Quick edit Valid - stable 2019-09-10 RO9
CSV Import

The CSV file should contain a header row for element names and data rows for concepts.
It is strongly recommended to use an exported CSV file as a template for bulk editing. Columns and rows can be added to or deleted from the template file.
A concept can be ignored by prepending a double-slash '//' to the concept row in the CSV
    Notes:
  • If the header row contains unknown elements the import will aborted and data will be rolled back
  • Erroneous concept rows are ignored, valid data rows are still imported
  • Successful import cannot be undone (unless "undo checkout" is performed)
  • If a concept with the same identifier already exists in the vocabulary it will be overwritten
  • "Purge Vocabulary" option deletes all the vocabulary concepts before import
Note
  • With this operation, contents of RDF file will be imported into vocabulary folder.
  • Only a working copy can be updated with a RDF file upload.
  • If user select "Purge Per Predicate" option. All seen predicates will be removed from vocabulary.
  • If user select "Purge All Vocabulary Data" option. All data will be removed from vocabulary.
  • Once import is successful, operation cannot be undone. If an error occurs during import, then all data will be rolled back.
In this case, existing vocabulary information will be updated with information from imported concepts.
In this case, predicates of existing concepts will be replaced with the imported predicates.
In this case, all existing concepts will be removed and the imported concepts will be added.
In this case, all imported concepts will be removed from the vocabulary.
How to handle missing concepts?