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 8,641 to 8,660.First429430431432433434435436Last
Id Label Status Status Modified Notation
NL002D00006 Staatslieden- en Frederik Hendrikbuurt Quick edit Valid 2013-06-11 NL002D00006
NL002D00007 Da Costa-, Kinker- en Van Lennepbuurt Quick edit Valid 2013-06-11 NL002D00007
NL002D00008 Overtoom- en Helmersbuurt Quick edit Valid 2013-06-11 NL002D00008
NL002D00009 Museum-, Apollo- en Willemparksbuurt Quick edit Valid 2013-06-11 NL002D00009
NL002D00010 De Pijp en Diamantbuurt Quick edit Valid 2013-06-11 NL002D00010
NL002D00011 Hoofddorpplein- , Schinkel- en Stadionbuurt Quick edit Valid 2013-06-11 NL002D00011
NL002D00012 Rivierenbuurt Quick edit Valid 2013-06-11 NL002D00012
NL002D00013 Zuidas en Buitenveldert Quick edit Valid 2013-06-11 NL002D00013
NL002D00014 Weesperzijde en Oosterpark Quick edit Valid 2013-06-11 NL002D00014
NL002D00015 Transvaal- en Dapperbuurt Quick edit Valid 2013-06-11 NL002D00015
NL002D00016 Watergraafsmeer Quick edit Valid 2013-06-11 NL002D00016
NL002D00017 Indische buurt Quick edit Valid 2013-06-11 NL002D00017
NL002D00018 Oostelijk Havengebied en IJburg Quick edit Valid 2013-06-11 NL002D00018
NL002D00019 Bijlmer Centrum Quick edit Valid 2013-06-11 NL002D00019
NL002D00020 Bijlmer Oost Quick edit Valid 2013-06-11 NL002D00020
NL002D00021 Holendrecht/Reigersbos Quick edit Valid 2013-06-11 NL002D00021
NL002D00022 Gein, Nellestein en Driemond Quick edit Valid 2013-06-11 NL002D00022
NL002D00023 Baarsjes Zuid en Oost Quick edit Valid 2013-06-11 NL002D00023
NL002D00024 Baarsjes Noord en West Quick edit Valid 2013-06-11 NL002D00024
NL002D00025 Bos en Lommer Oost Quick edit Valid 2013-06-11 NL002D00025
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?