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 8,421 to 8,440.First418419420421422423424425Last
Id Label Status Status Modified Notation
LT001D00020 Zirmunu seniunija Quick edit Valid 2013-06-11 LT001D00020
LT001D00021 Zveryno seniunija Quick edit Valid 2013-06-11 LT001D00021
LT001D00999 Not indicated Quick edit Valid 2013-06-11 LT001D00999
LT001F Vilnius Quick edit Valid 2022-10-18 LT001F
LT001L1 Vilnius Quick edit Valid 2013-06-11 LT001L1
LT002C1 Kaunas Quick edit Valid 2013-06-11 LT002C1
LT002D00 LT002D00 Quick edit Valid 2013-06-11 LT002D00
LT002D00001 Aleksoto seniunija Quick edit Valid 2013-06-11 LT002D00001
LT002D00002 Centro seniunija Quick edit Valid 2013-06-11 LT002D00002
LT002D00003 Dainavos seniunija. Dainava Quick edit Valid 2013-06-11 LT002D00003
LT002D00004 Dainavos seniunija. Griciupis Quick edit Valid 2013-06-11 LT002D00004
LT002D00005 Eiguliu seniunija Quick edit Valid 2013-06-11 LT002D00005
LT002D00006 Panemunes seniunija Quick edit Valid 2013-06-11 LT002D00006
LT002D00007 Petrasiunu seniunija Quick edit Valid 2013-06-11 LT002D00007
LT002D00008 Vilijampoles seniunija Quick edit Valid 2013-06-11 LT002D00008
LT002D00009 Sanciu seniunija Quick edit Valid 2013-06-11 LT002D00009
LT002D00010 Silainiu seniunija Quick edit Valid 2013-06-11 LT002D00010
LT002D00011 Zaliakalnio seniunija Quick edit Valid 2013-06-11 LT002D00011
LT002D00999 Not indicated Quick edit Valid 2013-06-11 LT002D00999
LT002F Kaunas Quick edit Valid 2022-10-18 LT002F
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?