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,201 to 3,220.First157158159160161162163164Last
Id Label Status Status Modified Notation
ES003L2 Valencia Quick edit Valid 2014-04-22 ES003L2
ES003L3 Valencia Quick edit Valid 2017-03-20 ES003L3
ES004C1 Sevilla Quick edit Valid 2013-06-11 ES004C1
ES004D01 ES004D01 Quick edit Valid 2013-06-11 ES004D01
ES004D01001 Sevilla sub-city dist. No. 1-A Quick edit Valid 2013-06-11 ES004D01001
ES004D01002 Sevilla sub-city dist. No. 1-B Quick edit Valid 2013-06-11 ES004D01002
ES004D01003 Sevilla sub-city dist. No. 1-C Quick edit Valid 2013-06-11 ES004D01003
ES004D02 ES004D02 Quick edit Valid 2013-06-11 ES004D02
ES004D02004 Sevilla sub-city dist. No. 2-A Quick edit Valid 2013-06-11 ES004D02004
ES004D02005 Sevilla sub-city dist. No. 2-B Quick edit Valid 2013-06-11 ES004D02005
ES004D02006 Sevilla sub-city dist. No. 2-C Quick edit Valid 2013-06-11 ES004D02006
ES004D02007 Sevilla sub-city dist. No. 2-D Quick edit Valid 2013-06-11 ES004D02007
ES004D02008 Sevilla sub-city dist. No. 2-E Quick edit Valid 2013-06-11 ES004D02008
ES004D02009 Sevilla sub-city dist. No. 2-F Quick edit Valid 2013-06-11 ES004D02009
ES004D02010 Sevilla sub-city dist. No. 2-G Quick edit Valid 2013-06-11 ES004D02010
ES004D02011 Sevilla sub-city dist. No. 2-H Quick edit Valid 2013-06-11 ES004D02011
ES004D03 ES004D03 Quick edit Valid 2013-06-11 ES004D03
ES004D03008 Sevilla sub-city dist. No. 3-A Quick edit Valid 2014-01-20 ES004D03008
ES004D03009 Sevilla sub-city dist. No. 3-B Quick edit Valid 2014-01-20 ES004D03009
ES004D03012 Sevilla sub-city dist. No. 3-A Quick edit Valid 2013-06-11 ES004D03012
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?