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
coreCityOf Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
20 Oct 2013
hasDistrict Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
20 Oct 2013
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:broader Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
30 Sep 2013
skos:closeMatch 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

Add new data elements

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

Vocabulary concepts

13,394 concepts found, displaying 1,601 to 1,620.First7778798081828384Last
Id Label Status Status Modified Notation
DE008D00920 Nord 2 Quick edit Valid 2013-06-11 DE008D00920
DE008F Leipzig Quick edit Valid 2022-10-18 DE008F
DE008L2 Leipzig Quick edit Valid 2013-06-11 DE008L2
DE009C1 Dresden Quick edit Valid 2013-06-11 DE009C1
DE009D00 DE009D00 Quick edit Valid 2013-06-11 DE009D00
DE009D00001 OA Altstadt ohne Johannstadt Quick edit Valid 2013-06-11 DE009D00001
DE009D00002 Johannstadt Quick edit Valid 2013-06-11 DE009D00002
DE009D00003 OA Neustadt ohne Leipziger Vorstadt Quick edit Valid 2013-06-11 DE009D00003
DE009D00004 Pieschen, Leipziger Vorstadt Quick edit Valid 2013-06-11 DE009D00004
DE009D00005 Mickten, Kaditz, Trachau Quick edit Valid 2013-06-11 DE009D00005
DE009D00006 OA Klotzsche, nördliche Ortschaften Quick edit Valid 2013-06-11 DE009D00006
DE009D00007 OA Loschwitz, OS Schönfeld-Weißig Quick edit Valid 2013-06-11 DE009D00007
DE009D00008 Blasewitz, Striesen Quick edit Valid 2013-06-11 DE009D00008
DE009D00009 Tolkewitz, Seidnitz, Gruna Quick edit Valid 2013-06-11 DE009D00009
DE009D00010 OA Leuben Quick edit Valid 2013-06-11 DE009D00010
DE009D00011 Prohlis, Reick, Am Koitschgraben Quick edit Valid 2013-06-11 DE009D00011
DE009D00012 OA Prohlis ohne Bereich 11 Quick edit Valid 2013-06-11 DE009D00012
DE009D00013 Südvorstadt, Räcknitz/Zschertnitz Quick edit Valid 2013-06-11 DE009D00013
DE009D00014 Mockritz, Coschütz, Plauen Quick edit Valid 2013-06-11 DE009D00014
DE009D00015 Gorbitz Quick edit Valid 2013-06-11 DE009D00015
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?