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
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
22 Nov 2024
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
owl:sameAs Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
30 Sep 2013
skos:altLabel Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
24 Sep 2013
skos:broader Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
30 Sep 2013
skos:exactMatch Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
30 Sep 2013
skos:narrower Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
17 Sep 2015
skos:narrowMatch Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
30 Sep 2013
validFrom Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
18 Nov 2024
validThrough Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
18 Nov 2024

Add new data elements

Mandatory
Mandatory
Optional
Optional
 

Vocabulary concepts

1,920 concepts found, displaying 1,401 to 1,420.First6768697071727374Last
Id Label Status Status Modified Notation
nuts2010.PL32 PODKARPACKIE Quick edit Deprecated - superseded 2024-12-03 PL32
nuts2010.PL323 KROŚNIEŃSKI Quick edit Deprecated - superseded 2024-12-03 PL323
nuts2010.PL324 PRZEMYSKI Quick edit Deprecated - superseded 2024-12-03 PL324
nuts2010.PL325 RZESZOWSKI Quick edit Deprecated - superseded 2024-12-03 PL325
nuts2010.PL326 TARNOBRZESKI Quick edit Deprecated - superseded 2024-12-03 PL326
nuts2010.PL33 ŚWIĘTOKRZYSKIE Quick edit Deprecated - superseded 2024-12-03 PL33
nuts2010.PL331 KIELECKI Quick edit Deprecated - superseded 2024-12-03 PL331
nuts2010.PL332 SANDOMIERSKO-JĘDRZEJOWSKI Quick edit Deprecated - superseded 2024-12-03 PL332
nuts2010.PL34 PODLASKIE Quick edit Deprecated - superseded 2024-12-03 PL34
nuts2010.PL343 BIAŁOSTOCKI Quick edit Deprecated - superseded 2024-12-03 PL343
nuts2010.PL344 ŁOMŻYŃSKI Quick edit Deprecated - superseded 2024-12-03 PL344
nuts2010.PL345 SUWALSKI Quick edit Deprecated - superseded 2024-12-03 PL345
nuts2010.PL4 REGION PÓLNOCNO-ZACHODNI Quick edit Deprecated - superseded 2024-12-03 PL4
nuts2010.PL41 WIELKOPOLSKIE Quick edit Deprecated - superseded 2024-12-03 PL41
nuts2010.PL411 PILSKI Quick edit Deprecated - superseded 2024-12-03 PL411
nuts2010.PL414 KONIŃSKI Quick edit Deprecated - superseded 2024-12-03 PL414
nuts2010.PL415 MIASTO POZNAŃ Quick edit Deprecated - superseded 2024-12-03 PL415
nuts2010.PL416 KALISKI Quick edit Deprecated - superseded 2024-12-03 PL416
nuts2010.PL417 LESZCZYŃSKI Quick edit Deprecated - superseded 2024-12-03 PL417
nuts2010.PL418 POZNAŃSKI Quick edit Deprecated - superseded 2024-12-03 PL418
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?