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,281 to 1,300.First6162636465666768Last
Id Label Status Status Modified Notation
8321 Klarup Quick edit Valid 2013-05-30 8321
8322 Gudum Quick edit Valid 2013-05-30 8322
8323 Lillevorde Quick edit Valid 2013-05-30 8323
8324 Mou Quick edit Valid 2013-05-30 8324
8325 Storvorde Quick edit Valid 2013-05-30 8325
8326 Sejlflod Quick edit Valid 2013-05-30 8326
8327 Nibe Quick edit Valid 2013-05-30 8327
8328 Vokslev Quick edit Valid 2013-05-30 8328
8329 Sønderholm Quick edit Valid 2013-05-30 8329
8330 Frejlev Quick edit Valid 2013-05-30 8330
8331 Nørholm Quick edit Valid 2013-05-30 8331
8332 Ellidshøj Quick edit Valid 2013-05-30 8332
8333 Svenstrup Quick edit Valid 2013-05-30 8333
8334 Øster Hornum Quick edit Valid 2013-05-30 8334
8335 Buderup Quick edit Valid 2013-05-30 8335
8336 Gravlev Quick edit Valid 2013-05-30 8336
8337 Aarestrup Quick edit Valid 2013-05-30 8337
8338 Haverslev Quick edit Valid 2013-05-30 8338
8339 Sønderup Quick edit Valid 2013-05-30 8339
8340 Suldrup Quick edit Valid 2013-05-30 8340
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?