You are here:
Eionet
Data Dictionary
Edit vocabulary

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
skos:broadMatch Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
30 Sep 2013

Add new data elements

Mandatory
Mandatory
Optional
Optional
 

Vocabulary concepts

2,122 concepts found, displaying 1,621 to 1,640.First7879808182838485Last
Id Label Status Status Modified Notation
8665 Stagstrup Quick edit Valid 2013-05-30 8665
8666 Skyum Quick edit Valid 2013-05-30 8666
8667 Hørdum Quick edit Valid 2013-05-30 8667
8668 Sejerslev Quick edit Valid 2013-05-30 8668
8669 Ejerslev Quick edit Valid 2013-05-30 8669
8670 Jørsby Quick edit Valid 2013-05-30 8670
8671 Flade Quick edit Valid 2013-05-30 8671
8672 Bjergby Quick edit Valid 2013-05-30 8672
8673 Alsted Quick edit Valid 2013-05-30 8673
8674 Sønder Dråby Quick edit Valid 2013-05-30 8674
8675 Solbjerg Quick edit Valid 2013-05-30 8675
8676 Sundby Quick edit Valid 2013-05-30 8676
8677 Dragstrup Quick edit Valid 2013-05-30 8677
8678 Skallerup Quick edit Valid 2013-05-30 8678
8679 Galtrup Quick edit Valid 2013-05-30 8679
8680 Øster Jølby Quick edit Valid 2013-05-30 8680
8681 Tødsø Quick edit Valid 2013-05-30 8681
8682 Erslev Quick edit Valid 2013-05-30 8682
8683 Hassing Quick edit Valid 2013-05-30 8683
8684 Villerslev Quick edit Valid 2013-05-30 8684
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?