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 3,241 to 3,260.First159160161162163164165166Last
Id Label Status Status Modified Notation
ES004D04027 Sevilla sub-city dist. No. 4-I Quick edit Valid 2013-06-11 ES004D04027
ES004D05 ES004D05 Quick edit Valid 2013-06-11 ES004D05
ES004D05015 Sevilla sub-city dist. No. 5-A Quick edit Valid 2014-01-20 ES004D05015
ES004D05016 Sevilla sub-city dist. No. 5-B Quick edit Valid 2014-01-20 ES004D05016
ES004D05017 Sevilla sub-city dist. No. 5-C Quick edit Valid 2014-01-20 ES004D05017
ES004D05018 Sevilla sub-city dist. No. 5-D Quick edit Valid 2014-01-20 ES004D05018
ES004D05019 Sevilla sub-city dist. No. 5-E Quick edit Valid 2014-01-20 ES004D05019
ES004D05028 Sevilla sub-city dist. No. 5-A Quick edit Valid 2013-06-11 ES004D05028
ES004D05029 Sevilla sub-city dist. No. 5-B Quick edit Valid 2013-06-11 ES004D05029
ES004D05030 Sevilla sub-city dist. No. 5-C Quick edit Valid 2013-06-11 ES004D05030
ES004D05031 Sevilla sub-city dist. No. 5-D Quick edit Valid 2013-06-11 ES004D05031
ES004D05032 Sevilla sub-city dist. No. 5-E Quick edit Valid 2013-06-11 ES004D05032
ES004D05033 Sevilla sub-city dist. No. 5-F Quick edit Valid 2013-06-11 ES004D05033
ES004D05034 Sevilla sub-city dist. No. 5-G Quick edit Valid 2013-06-11 ES004D05034
ES004D06 ES004D06 Quick edit Valid 2013-06-11 ES004D06
ES004D06020 Sevilla sub-city dist. No. 6-A Quick edit Valid 2014-01-20 ES004D06020
ES004D06021 Sevilla sub-city dist. No. 6-B Quick edit Valid 2014-01-20 ES004D06021
ES004D06022 Sevilla sub-city dist. No. 6-C Quick edit Valid 2014-01-20 ES004D06022
ES004D06035 Sevilla sub-city dist. No. 6-A Quick edit Valid 2013-06-11 ES004D06035
ES004D06036 Sevilla sub-city dist. No. 6-B Quick edit Valid 2013-06-11 ES004D06036
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?