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,841 to 2,860.First139140141142143144145146Last
Id Label Status Status Modified Notation
ES001D01005 Madrid sub-city dist. No. 1-E Quick edit Valid 2013-06-11 ES001D01005
ES001D01006 Madrid sub-city dist. No. 1-F Quick edit Valid 2013-06-11 ES001D01006
ES001D01007 Madrid sub-city dist. No. 1-G Quick edit Valid 2013-06-11 ES001D01007
ES001D02 ES001D02 Quick edit Valid 2013-06-11 ES001D02
ES001D02008 Madrid sub-city dist. No. 2-A Quick edit Valid 2013-06-11 ES001D02008
ES001D02009 Madrid sub-city dist. No. 2-B Quick edit Valid 2013-06-11 ES001D02009
ES001D02010 Madrid sub-city dist. No. 2-C Quick edit Valid 2013-06-11 ES001D02010
ES001D02011 Madrid sub-city dist. No. 2-D Quick edit Valid 2013-06-11 ES001D02011
ES001D02012 Madrid sub-city dist. No. 2-E Quick edit Valid 2013-06-11 ES001D02012
ES001D02013 Madrid sub-city dist. No. 2-F Quick edit Valid 2013-06-11 ES001D02013
ES001D03 ES001D03 Quick edit Valid 2013-06-11 ES001D03
ES001D03014 Madrid sub-city dist. No. 3-A Quick edit Valid 2013-06-11 ES001D03014
ES001D03015 Madrid sub-city dist. No. 3-B Quick edit Valid 2013-06-11 ES001D03015
ES001D03016 Madrid sub-city dist. No. 3-C Quick edit Valid 2013-06-11 ES001D03016
ES001D03017 Madrid sub-city dist. No. 3-D Quick edit Valid 2013-06-11 ES001D03017
ES001D03018 Madrid sub-city dist. No. 3-E Quick edit Valid 2013-06-11 ES001D03018
ES001D03019 Madrid sub-city dist. No. 3-F Quick edit Valid 2013-06-11 ES001D03019
ES001D04 ES001D04 Quick edit Valid 2013-06-11 ES001D04
ES001D04020 Madrid sub-city dist. No. 4-A Quick edit Valid 2013-06-11 ES001D04020
ES001D04021 Madrid sub-city dist. No. 4-B Quick edit Valid 2013-06-11 ES001D04021
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?