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
adms:status Vocabulary
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
01 Oct 2015
dct:isReplacedBy Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
08 Oct 2013
dct:replaces Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
08 Oct 2013
hasFeatureOfInterest Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
08 Feb 2016
hasIdentifierScheme Vocabulary
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
22 Nov 2024
inCountry Vocabulary
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
29 Aug 2014

Add new data elements

Mandatory
Mandatory
Optional
Optional
 

Vocabulary concepts

440,076 concepts found, displaying 61 to 80.First12345678Last
Id Label Status Status Modified Notation
eionetMonitoringSiteCode.ALGW_504 173 SHEQERAS Quick edit Valid - stable 2021-06-17 ALGW_504
eionetMonitoringSiteCode.ALGW_601 KAFARAJ Quick edit Valid - stable 2021-06-17 ALGW_601
eionetMonitoringSiteCode.ALGW_602 BUDUK Quick edit Valid - stable 2021-06-17 ALGW_602
eionetMonitoringSiteCode.ALGW_603 NOVOSELE Quick edit Valid - stable 2021-06-17 ALGW_603
eionetMonitoringSiteCode.ALGW_604 VALARE Quick edit Valid - stable 2021-06-17 ALGW_604
eionetMonitoringSiteCode.ALGW_605 BODRISHTE Quick edit Valid - stable 2021-06-17 ALGW_605
eionetMonitoringSiteCode.ALGW_801 ORIKUM Quick edit Valid - stable 2021-06-17 ALGW_801
eionetMonitoringSiteCode.ALGW_802 CUKE - KARAHAXH Quick edit Valid - stable 2021-06-17 ALGW_802
eionetMonitoringSiteCode.ALGW_803 VRION Quick edit Valid - stable 2021-06-17 ALGW_803
eionetMonitoringSiteCode.ALGW_804 XARE-MURSI Quick edit Valid - stable 2021-06-17 ALGW_804
eionetMonitoringSiteCode.ALISH1 UNKNOWN Quick edit Deprecated - retired 2021-06-17 ALISH1
eionetMonitoringSiteCode.ALISH2 UNKNOWN Quick edit Deprecated - retired 2021-06-17 ALISH2
eionetMonitoringSiteCode.ALISH3 UNKNOWN Quick edit Deprecated - retired 2021-06-17 ALISH3
eionetMonitoringSiteCode.ALLK_101 SHIROKE Quick edit Valid - experimental 2021-06-17 ALLK_101
eionetMonitoringSiteCode.ALLK_102 BAJZE Quick edit Deprecated - retired 2021-06-17 ALLK_102
eionetMonitoringSiteCode.ALLK_103 ZOGAJ Quick edit Valid - experimental 2021-06-17 ALLK_103
eionetMonitoringSiteCode.ALLK_603 PRESPA Quick edit Deprecated - retired 2021-06-17 ALLK_603
eionetMonitoringSiteCode.ALLK_801 BUTRINTI Quick edit Valid - experimental 2021-06-17 ALLK_801
eionetMonitoringSiteCode.ALLK_802 KSAMILI Quick edit Deprecated - retired 2021-06-17 ALLK_802
eionetMonitoringSiteCode.ALOHRI-LAKE OHRI LAKE Quick edit Deprecated - retired 2021-06-17 ALOHRI-LAKE
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?