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
inCountry Vocabulary
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
29 Aug 2014
skos:broader Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
30 Sep 2013
skos:narrower Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
17 Sep 2015

Add new data elements

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

Vocabulary concepts

18 concepts found, displaying all concepts.
Id Label Status Status Modified Notation
ABI Bay of Biscay and Iberian Coast Quick edit Valid 2014-01-24 ABI
ACS Celtic Seas Quick edit Valid 2014-01-24 ACS
AMA Macaronesia Quick edit Valid 2014-01-24 AMA
ANS Greater North Sea Quick edit Valid 2014-01-24 ANS
ATL North East Atlantic Ocean Quick edit Valid 2015-10-09 ATL
BAL Baltic Sea Quick edit Valid 2014-01-24 BAL
BAR Barents Sea Quick edit Valid 2015-10-09 BAR
BLA Black Sea - sea of Azov Quick edit Valid 2017-10-27 BLA
BLK Black Sea Quick edit Valid 2014-01-24 BLK
BLM Black Sea - sea of Marmara Quick edit Valid 2017-10-27 BLM
ICE Iceland Sea Quick edit Valid 2015-10-09 ICE
MAD Adriatic Sea Quick edit Valid 2014-01-24 MAD
MAL Aegean-Levantine Sea Quick edit Valid 2014-01-24 MAL
MED Mediterranean Sea Quick edit Valid 2015-10-09 MED
MIC Ionian Sea and Central Mediterranean Sea Quick edit Valid 2014-01-24 MIC
MWE Western Mediterranean Sea Quick edit Valid 2014-01-24 MWE
NOR Norwegian Sea Quick edit Valid 2015-10-09 NOR
WHI White Sea Quick edit Valid 2015-10-09 WHI
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?