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 181 to 200.First678910111213Last
Id Label Status Status Modified Notation
BE001D05013 ETTERBEEK Quick edit Valid 2013-06-11 BE001D05013
BE001D06 EVERE Quick edit Valid 2013-06-11 BE001D06
BE001D06014 EVERE Quick edit Valid 2013-06-11 BE001D06014
BE001D07 VORST / FOREST Quick edit Valid 2013-06-11 BE001D07
BE001D07015 VORST OOST / FOREST EST Quick edit Valid 2013-06-11 BE001D07015
BE001D07016 VORST WEST / FOREST OUEST Quick edit Valid 2013-06-11 BE001D07016
BE001D08 GANSHOREN Quick edit Valid 2013-06-11 BE001D08
BE001D08017 GANSHOREN Quick edit Valid 2013-06-11 BE001D08017
BE001D09 ELSENE / IXELLES Quick edit Valid 2013-06-11 BE001D09
BE001D09018 ELSENE SUD / IXELLES ZUID Quick edit Valid 2013-06-11 BE001D09018
BE001D09019 ELSENE NOORD / IXELLES NORD Quick edit Valid 2013-06-11 BE001D09019
BE001D09020 ELSENE WEST/ IXELLES OUEST Quick edit Valid 2013-06-11 BE001D09020
BE001D10 JETTE Quick edit Valid 2013-06-11 BE001D10
BE001D10021 JETTE Quick edit Valid 2013-06-11 BE001D10021
BE001D11 KOEKELBERG Quick edit Valid 2013-06-11 BE001D11
BE001D11022 KOEKELBERG Quick edit Valid 2013-06-11 BE001D11022
BE001D12 MOLENBEEK Quick edit Valid 2013-06-11 BE001D12
BE001D12023 MOLENBEEK WEST / MOLENBEEK OUEST Quick edit Valid 2013-06-11 BE001D12023
BE001D12024 MOLENBEEK OOST/ MOLENBEEK EST Quick edit Valid 2013-06-11 BE001D12024
BE001D13 SINT-GILLIS / SAINT-GILLES Quick edit Valid 2013-06-11 BE001D13
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?