Validation Errors
  • This element has value in Concepts: VocabularyConcept[id=430007,identifier=1,label=Verified,definition=Data has gone through full quality assurance and quality control by data provider/owner. Data is considered verified and can be formally used for its reporting purposes.,notation=1],VocabularyConcept[id=430008,identifier=2,label=Preliminary verified,definition=Data has gone through initial checks by data provider/owner. Extra quality assurance and quality control verifications have been carried out compared to "Not verified" data. Data Verification might be carried out on an ongoing basis and is nominally a process to "clean-up" the initial "Not verified" data. Any corrections to the data made during the verification process are changes the status flag to "Preliminary verified". The data with this data flag is considered provisional and can be used as provisional. This flag is independant to the validity status.,notation=2],VocabularyConcept[id=430009,identifier=3,label=Not verified,definition=Data has not gone through (or has gone through minimal) checks by data provider/owner. Some basic screening criteria in order to exclude clearly faulty data as far as possible maybe used. The data with this data flag is considered provisional and can be used as provisional. This flag is independant to the validity status.,notation=3] Please delete the values before removing the element binding.

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:scopeNote Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
24 Sep 2013
Remove

Add new data elements

Mandatory
Mandatory
Optional
Optional
 

Vocabulary concepts

3 concepts found, displaying all concepts.
Id Label Status Status Modified Notation
1 Verified Quick edit Valid 22.03.2013 1
2 Preliminary verified Quick edit Valid 22.03.2013 2
3 Not verified Quick edit Valid 22.03.2013 3
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?