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,781 to 8,800.First436437438439440441442443Last
Id Label Status Status Modified Notation
NL004D00024 Abstede, Hoograven, Lunetten Quick edit Valid 2014-01-20 NL004D00024
NL004D00025 Leidsche Rijn-N, Vleuten, Haarzuilens Quick edit Valid 2014-01-20 NL004D00025
NL004D00026 De Meern, Leidsche Rijn-Z, Utrecht-ZW Quick edit Valid 2014-01-20 NL004D00026
NL004F Utrecht Quick edit Valid 2022-10-18 NL004F
NL004L2 Utrecht Quick edit Valid 2013-06-11 NL004L2
NL004L3 Utrecht Quick edit Valid 2017-03-20 NL004L3
NL005C Alphen aan den Rijn Quick edit Valid 2015-04-20 NL005C
NL005C1 Eindhoven Quick edit Valid 2013-06-11 NL005C1
NL005C2 Greater Eindhoven Quick edit Valid 2018-01-12 NL005C2
NL005D00 NL005D00 Quick edit Valid 2013-06-11 NL005D00
NL005D00001 Binnenstad Quick edit Valid 2013-06-11 NL005D00001
NL005D00002 Stratum west Quick edit Valid 2013-06-11 NL005D00002
NL005D00003 Stratum oost Quick edit Valid 2013-06-11 NL005D00003
NL005D00004 Tongelre Quick edit Valid 2013-06-11 NL005D00004
NL005D00005 Woensel Zuidwest Quick edit Valid 2013-06-11 NL005D00005
NL005D00006 Woensel Zuidoost Quick edit Valid 2013-06-11 NL005D00006
NL005D00007 Ontginning Quick edit Valid 2013-06-11 NL005D00007
NL005D00008 Achtse molen Quick edit Valid 2013-06-11 NL005D00008
NL005D00009 Aanschot Quick edit Valid 2013-06-11 NL005D00009
NL005D00010 Dommelbeemd Quick edit Valid 2013-06-11 NL005D00010
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?