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,961 to 2,980.First145146147148149150151152Last
Id Label Status Status Modified Notation
ES001D14097 Madrid sub-city dist. No. 14-C Quick edit Valid 2014-01-20 ES001D14097
ES001D14098 Madrid sub-city dist. No. 14-D Quick edit Valid 2014-01-20 ES001D14098
ES001D14099 Madrid sub-city dist. No. 14-E Quick edit Valid 2014-01-20 ES001D14099
ES001D14140 Madrid sub-city dist. No. 14-F Quick edit Valid 2014-01-20 ES001D14140
ES001D15 ES001D15 Quick edit Valid 2013-06-11 ES001D15
ES001D15097 Madrid sub-city dist. No. 15-A Quick edit Valid 2013-06-11 ES001D15097
ES001D15098 Madrid sub-city dist. No. 15-B Quick edit Valid 2013-06-11 ES001D15098
ES001D15099 Madrid sub-city dist. No. 15-C Quick edit Valid 2013-06-11 ES001D15099
ES001D15100 Madrid sub-city dist. No. 15-A Quick edit Valid 2013-06-11 ES001D15100
ES001D15101 Madrid sub-city dist. No. 15-B Quick edit Valid 2013-06-11 ES001D15101
ES001D15102 Madrid sub-city dist. No. 15-C Quick edit Valid 2013-06-11 ES001D15102
ES001D15103 Madrid sub-city dist. No. 15-D Quick edit Valid 2013-06-11 ES001D15103
ES001D15104 Madrid sub-city dist. No. 15-E Quick edit Valid 2013-06-11 ES001D15104
ES001D15105 Madrid sub-city dist. No. 15-F Quick edit Valid 2013-06-11 ES001D15105
ES001D15106 Madrid sub-city dist. No. 15-G Quick edit Valid 2013-06-11 ES001D15106
ES001D15107 Madrid sub-city dist. No. 15-H Quick edit Valid 2014-01-20 ES001D15107
ES001D15108 Madrid sub-city dist. No. 15-I Quick edit Valid 2014-01-20 ES001D15108
ES001D15109 Madrid sub-city dist. No. 15-J Quick edit Valid 2014-01-20 ES001D15109
ES001D16 ES001D16 Quick edit Valid 2013-06-11 ES001D16
ES001D16107 Madrid sub-city dist. No. 16-A Quick edit Valid 2013-06-11 ES001D16107
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?