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
owl:sameAs 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

Add new data elements

Mandatory
Mandatory
Optional
Optional (forcefully equal to identifier in this vocabulary)
 

Vocabulary concepts

4,043 concepts found, displaying 1,041 to 1,060.First4950515253545556Last
Id Label Status Status Modified Notation
DEE24 Merseburg-Querfurt (NUTS 2003) Quick edit Valid 2013-09-25 DEE24
DEE25 Saalkreis (NUTS 2003) Quick edit Valid 2013-09-25 DEE25
DEE26 Sangerhausen (NUTS 2003) Quick edit Valid 2013-09-25 DEE26
DEE27 Weißenfels (NUTS 2003) Quick edit Valid 2013-09-25 DEE27
DEE3 Magdeburg (NUTS 2003) Quick edit Valid 2013-09-25 DEE3
DEE32 Aschersleben-Staßfurt (NUTS 2003) Quick edit Valid 2013-09-25 DEE32
DEE33 Bördekreis (NUTS 2003) Quick edit Valid 2013-09-25 DEE33
DEE34 Halberstadt (NUTS 2003) Quick edit Valid 2013-09-25 DEE34
DEE35 Jerichower Land (NUTS 2003) Quick edit Valid 2013-09-25 DEE35
DEE36 Ohrekreis (NUTS 2003) Quick edit Valid 2013-09-25 DEE36
DEE37 Stendal (NUTS 2003) Quick edit Valid 2013-09-25 DEE37
DEE38 Quedlinburg (NUTS 2003) Quick edit Valid 2013-09-25 DEE38
DEE39 Schönebeck (NUTS 2003) Quick edit Valid 2013-09-25 DEE39
DEE3A Wernigerode (NUTS 2003) Quick edit Valid 2013-09-25 DEE3A
DEE_SAU Saale-Unstrut Quick edit Valid 2013-09-25 DEE_SAU
DEF Schleswig-Holstein Quick edit Valid 2013-09-25 DEF
DEF0 Schleswig-Holstein Quick edit Valid 2013-09-25 DEF0
DEF01 Flensburg, Kreisfreie Stadt Quick edit Valid 2013-09-25 DEF01
DEF02 Kiel, Kreisfreie Stadt Quick edit Valid 2013-09-25 DEF02
DEF03 Lübeck, Kreisfreie Stadt Quick edit Valid 2013-09-25 DEF03
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?