This page contains instructions for actions that may be performed by editors through the graphical interface, including Sheet2RDF. 


Projects

Clear a project 

When you want to delete all contents of a project, use the option Clear Data.

  1. Go to Global Data Management → Clear Data

Note: Clear data removes everything from the project, including any ontology you may have imported.  


Get existing data into a project

Load RDF data in a project

This is to load data such as classifications/codelists into your project. You can use it to load an RDF file.  

For ontologies or similar vocabularies, use "Metadata - Namespaces and Import" (see below).

  1. Go to Global Data Management, Load Data 
  2. Select the File by clicking on Browse. Keep all other default value.
  3. Click Submit


Import ontologies or vocabularies

  1. Go to Metadata → Namespaces and Import
  2. In box Imports, select a value for Add Import from:
    1.  "Local project" for dedicated ontologies (FAO development)
      1.  In window "Import for local project", select the Project you want
      2. Base URI will be filled automatically
      3. Transitive imports: Resolve from web


Load ASFIS data 

  1. Clear data if needed (see above)
  2. Load data (see above)
  3. Import ontologies (see above). Take projects:
    1. ASFIS_ontology
    2. ISSCAAP ontology. 
  4. At this point, the hierarchies will be correctly visualized (thanks to the ontology), but for a correct procedure, set them in the Concept tree settings. In the left panel, click on the cogwheel. The window opens, where: 
    1. In the box Broader, add (click on +) asfis:broader and isscaap:broader
    2. In the box Broader, add (click on +) asfis:narrower and isscaap:narrower
  5. Now, you are ready. Select the concept scheme you want in menu Data → Scheme

Get "new" data into a project

Create a new classification via GUI

  1. Opens your project and check its base URI (menu Metadata) 
  2. In menu Data, tab Scheme, create a new scheme
  3. In menu Data, tab Concept, create your concepts

Clone an item, a branch, an entire code list? 

This task was added here to answer a question from NFI.

There is no such an option from the GUI. Possible alternative would consist in generate copies of the given items via SPARQL query. The query may be stored as a parameterized SPARQL update (the parameter is the root of the branch to be cloned), so that when invoking the stored parameterized update, the new root can be chosen through the UI.

Visualization & GUI customization

Chose your languages for the Hierarchy view

  1. Go to your account (top right corner) → Preferences
  2. in tab Languages, select the language(s) in which you want the hierarchy to be visualized. You can also chose their order.


Chose your languages for the Resource view 

  1. Go to your account (top right corner) → Preferences
  2. in tab Resource View, check box Sort lexicalizations by rendering languages
    1. You can select the language(s) and the order in which you want the items to be visualized. Eg. Russian first:




Visualization mode - Hierarchy based or Search based

  1. Menu Data → tab Concept
  2. click on the cogwheel, select Visualization mode
    1. Hierarchy based is the default
    2. with Search based, you will be able to see concepts based on a search result (search input is at the bottom of the left panel). You will get a message highlighted in yellow: 



View items a specific subset of a code list (question)


Versions

Create a version

  1. Go to Global Data Management → Versioning
  2. In box Versions, button Dump, click arrow
    1. Dump a new version
      1. assign an ID of choice
    2. Dump a new version to a different location
      1. assign an ID of choice
      2. Repository access: remote
      3. Repo configuration: GraphDB 10+ (no need to configure)
  3. When a new version is created, you can switch from one to the other (select the version you want, then click Switch to version)


Individual records (operations from GUI)

Edit a record

Edit a single record (ASFIS), e.g., EN name 

  1. In left panel, hierarchy, browse/search for the concept you want to edit and select it (click on it)
  2. In the right panel, go to block Lexicalizations.
    1. in subsection skos:prefLabel, chose Edit
    2. Edit the value, then click the green check to save your work


Edit a single record (ASFIS), e.g., scientific name 

Just like editing a prefLabel, but in section Other properties

Add a record

Add a single ASFIS record

  1. Select the scheme ASFIS
  2. Go to menu Data, tab Concept
  3. In the left panel, hierarchy, choose the parent for the concept you want to add
  4. Click on icon Create narrower concept (right below tab name)
  5. A window Create narrower concept will prompt
    1. Add label (= skos:prefLabel)
    2. add the last part of the URI. The convention adopted to date is that, for species, the last part of the URI is their taxon code.

Note:

  1. There can be only one prefLabel per language → if the one you add is already present, you get an error
  2. URIs are unique, if you try to create a concept with the same local part of the URI you get an error (... already exists in the current dataset)


Add a new area item (e.g., new subareas for area 31)

  1. Go to menu Data, tab Concept
  2. In left panel, select Area 31
  3. Clik icon Create narrower concept



Remove a single ASFIS record

  1. Go to menu Data, tab Concept
  2. In the left panel, browse/search for the concept you want to delete
  3. Click icon “Delete concept”
    1. note: the concept to delete should not have children, otherwise the operation is denied



Deprecate a single ASFIS record

  1. Go to menu Data, tab Concept
  2. In the left panel, browse/search for the concept you want to delete. Select it
  3. in the right panel, click on the downward pointing arrow next to the cogwheel
    1. click on Set as deprecated

The blue ball next to the Concept name (in both panels) will become grey and in box “Other properties” (right panel) you will see a property “owl:deprecated" with value "true”  



Restore a deprecated item 

  1. Delete the property owl:deprecated, in box "Other properties", right panel 
  2. Refresh the view of the right panel to see the grey ball icon to turn blue again
  3. Refresh the view of the left panel to see the grey ball icon to turn blue again in the hierarchy



Correspondences/alignments [new!]

Add a correspondence to a concept in a different VB project (but same deployment) 

  1. Go to menu Data, tab Concept
  2. Select the concept you want to be the "source" of the correspondence
  3. In right panel, top right, click on the little arrow pointing downward, then Align with external resource

You are now prompted with a small window Create alignment:

In Target Resource, click on the pencil icon to select the resource from which you want to take the target. You can choose one of the following:

  1. Browse local projects
  2. Assisted search
  3. Enter value manually



Browse local project. This is to use when the target concept is in a project on the same VB deployment. In this example, we want to draw a correspondence between an ASFIS species and a FAO Division in FAO_fishing_areas (fictional case). Then, after having selected the project in Project, select the type (Instance). In the left area you will be prompted with all choices available - you select Division in the left area, then the desired specific division in the right panel.  

In the third box, Property, you may select the type of property available to define the correspondence. 

 

Note: ..... 


Bulk operations with Sheet2RDF (test with ASFIS data)

The actions in this section have been prepared using the sample data provided by Sara Montanaro. Folder data

General data preparation made by CC:

  1. Generated 3 separate spreadsheets, one for adding data, one for deleting, one for revising.
  2. Each spreadsheet was then reorganized using the same order of columns used in the input data used to generate ASFIS-ISSCAAP classification (to reuse the mapping with minimum adjustment)

  3. In each file, added:

    1. a column FAMILY_code to be able to add the species under the correct family without having to generate a second file for the group-member relationship
    2. a column Note CC, for comments. A quick check of the results showed that many items seem to be repeated - items with the same EN name but different taxonomic code existed. Check with NFI.

Upload new ASFIS records in bulk

See Folder data

Delete ASFIS records in bulk 

See Folder data

Revise ASFIS records in bulk

Treated as a deletion followed by creation of new data. See Folder data

Upload a new full classification

See example already provided for FAO fishing areas.






Write a comment…