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
errorType Fixed values
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
03 May 2023
skos:editorialNote Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
24 Sep 2013
skos:hiddenLabel Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
24 Sep 2013

Add new data elements

Mandatory
Mandatory
Optional
Optional (forcefully equal to identifier in this vocabulary)
 

Vocabulary concepts

612 concepts found, displaying 241 to 260.First910111213141516Last
Id Label Status Status Modified Notation
E15 Check valid definition for startTime Quick edit Valid 2023-05-04 E15
E16 Check valid definition for endTime Quick edit Valid 2023-05-04 E16
E17 Check valid definition for observation validity Quick edit Valid 2023-05-04 E17
E18 Check valid definition for observation verification Quick edit Valid 2023-05-04 E18
E19 Check valid definition for the observation values (primaryObservation code & concentration) Quick edit Valid 2023-05-04 E19
E19a Check primaryObservation definition for the observation values are defined as /hour /day or /var Quick edit Valid 2023-05-04 E19a
E19b Check if data is provided using the recommended unit according to vocabulary. Important note: aggregates will not be calculated.  Quick edit Valid 2023-05-04 E19b
E19c Check if data is provided using the mandatory unit according to vocabulary Quick edit Valid 2024-11-27 E19c
E19d Check consistency of primaryObservatin (hour/day/var) with data already reported for same SamplingPoint Quick edit Valid 2024-01-30 E19d
E19e Check primaryObservation definition for the observation values (hour /day or /var) against Cadence/Duration reported in meta-data (D) Quick edit Valid 2024-01-30 E19e
E1aCrossCheck Cross checks with other data-flows Quick edit Valid 2023-05-04 E1aCrossCheck
E1bCrossCheck Cross checks with other data-flows Quick edit Valid 2023-05-04 E1bCrossCheck
E20 Check valid definition for the data coverage element (if provided) Quick edit Valid 2023-05-04 E20
E21 Check valid TextEncoding (decimalSeparator="." tokenSeparator=“”SEMICOLON”” blockSeparator="@@") Quick edit Valid 2023-05-04 E21
E22 The order of the fields within individual data blocks must correspond to the order described. Quick edit Valid 2023-05-04 E22
E23 The count of values provided for observation should match the count declared and should not be 0. Quick edit Valid 2023-05-04 E23
E23b The primaryObsevation value can not be empty (NULL) Quick edit Valid 2023-05-04 E23b
E24 Difference between endTime & startTime must correspond to the definition under <swe:field name="Value"><swe:Quantity definition=>. Quick edit Valid 2023-05-04 E24
E24b All reported dates within the data array must be fully ISO Quick edit Valid 2023-05-04 E24b
E25 The temporal envelopes of the swe:values (reported via starTime and EndTime) shall reconcile with ./om:phenomenonTime/gml:TimePeriod/gml:beginPosition Quick edit Valid 2023-05-04 E25
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?