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,681 to 3,700.First181182183184185186187188Last
Id Label Status Status Modified Notation
ES015D07 ES015D07 Quick edit Valid 2013-06-11 ES015D07
ES015D07007 Santander sub-city dist. No. 7 Quick edit Valid 2013-06-11 ES015D07007
ES015D08 ES015D08 Quick edit Valid 2013-06-11 ES015D08
ES015D08008 Santander sub-city dist. No. 8 Quick edit Valid 2013-06-11 ES015D08008
ES015F Santander Quick edit Valid 2022-10-18 ES015F
ES015L1 Santander Quick edit Valid 2013-06-11 ES015L1
ES015L2 Santander Quick edit Valid 2014-04-22 ES015L2
ES016C1 Toledo Quick edit Valid 2013-06-11 ES016C1
ES016D05 ES016D05 Quick edit Valid 2013-06-11 ES016D05
ES016D05002 Toledo sub-city dist. No. 5 Quick edit Valid 2013-06-11 ES016D05002
ES016D08 ES016D08 Quick edit Valid 2013-06-11 ES016D08
ES016D08001 Toledo sub-city dist. No. 8 Quick edit Valid 2013-06-11 ES016D08001
ES016D09 ES016D09 Quick edit Valid 2013-06-11 ES016D09
ES016D09003 Toledo sub-city dist. No. 9 Quick edit Valid 2013-06-11 ES016D09003
ES016F Toledo Quick edit Valid 2022-10-18 ES016F
ES016L1 Toledo Quick edit Valid 2013-06-11 ES016L1
ES016L2 Toledo Quick edit Valid 2014-04-22 ES016L2
ES017C1 Badajoz Quick edit Valid 2013-06-11 ES017C1
ES017D01 ES017D01 Quick edit Valid 2013-06-11 ES017D01
ES017D01001 Badajoz sub-city dist. No. 1 Quick edit Valid 2013-06-11 ES017D01001
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?