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 2,421 to 2,440.First118119120121122123124125Last
Id Label Status Status Modified Notation
DK002D00031 Beder-Malling Quick edit Valid 2013-06-11 DK002D00031
DK002D00032 Mårslet og Solbjerg Quick edit Valid 2013-06-11 DK002D00032
DK002D00034 Harlev-Framlev og Sabro-Borum Quick edit Valid 2013-06-11 DK002D00034
DK002D00036 Trige-Spørring Quick edit Valid 2013-06-11 DK002D00036
DK002D00038 Hjortshøj og Hårup-Mejlby Quick edit Valid 2013-06-11 DK002D00038
DK002D00039 Skødstrup-Løgten Quick edit Valid 2013-06-11 DK002D00039
DK002D00999 DK002D00999 Quick edit Valid 2013-06-11 DK002D00999
DK002F Århus Quick edit Valid 2022-10-18 DK002F
DK002L2 Århus Quick edit Valid 2014-11-19 DK002L2
DK002L3 Århus Quick edit Valid 2017-10-05 DK002L3
DK003C1 Odense Quick edit Valid 2013-06-11 DK003C1
DK003D00 DK003D00 Quick edit Valid 2013-06-11 DK003D00
DK003D00001 Odense city/nord/øst Quick edit Valid 2013-06-11 DK003D00001
DK003D00002 Odense city/vest/øst Quick edit Valid 2013-06-11 DK003D00002
DK003D00003 Agedrup/Munkebo/Odense nord/syd/øst Quick edit Valid 2013-06-11 DK003D00003
DK003D00004 Odense city/syd/øst/ Quick edit Valid 2013-06-11 DK003D00004
DK003D00005 Odense city/syd/øst/vest Quick edit Valid 2013-06-11 DK003D00005
DK003D00006 Blommenlyst/odense syd/vest Quick edit Valid 2013-06-11 DK003D00006
DK003D00007 Odense syd/vest Quick edit Valid 2013-06-11 DK003D00007
DK003D00008 Blommenslyst/Odense city/nord/vest Quick edit Valid 2013-06-11 DK003D00008
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?