Skip to main content

Edit a Concept Scheme

Inside Hanami SKOS Edition, a skos:ConceptScheme serves as a container for organizing concepts and collections. When you work with a skos:ConceptScheme, you are not just editing that central scheme, but you are also editing all the related concepts and collections that are part of that scheme. So, if you want to make changes to any of these elements, you would do so through the editing interface provided by the skos:ConceptScheme edition form. This approach ensures that all the interconnected data is managed cohesively through the central concept scheme.

What’s inside an edition form?

You will use different types of fields depending on the type of editing form you are in.

Concept Scheme form​

Here are the different fields available, in their default order:

  • Title: dct:title, available as xsd:string or rdf:langString1.
  • Label: skos:prefLabel, available as xsd:string or rdf:langString1.
  • Description: dct:description, available as xsd:string or rdf:langString1.
  • Publisher: dct:publisher, available as foaf:Agent, using either iris or blank nodes. It is also possible to link to an existing foaf:Agent withing the graph, for example one used for dct:creator2.
  • Creator: dct:description, same logic as dct:publisher2.
  • Version: owl:version, available as xsd:string.
  • License: dct:license, available as dct:LicenseDocument2.
  • Rights: dct:rights, available as dct:RightsStatement2.
  • Top concepts: skos:hasTopConcept, available as skos:Concept2.See below for available fields for those.
  • Collections: skos:inScheme on skos:Collection nodes. This field is configured as an inverse property to be able to pull naturally the collections in the graph of the skos:ConceptScheme.

Concept form​

Here are the different fields available, in their default order and groups:

  • Labels:
    • Label: skos:prefLabel, available as xsd:string or rdf:langString1.
    • Alternative label: skos:altLabel, available as xsd:string or rdf:langString1.
    • Hidden label: skos:hiddenLabel, available as xsd:string or rdf:langString1.
  • Notations
    • Notation: skos:notation. TODO, will change with new development.
  • Documentation
    • Definition: skos:definition, available as xsd:string or rdf:langString1.
    • Note: skos:note, available as xsd:string or rdf:langString1.
    • Change note: skos:changeNote, available as xsd:string or rdf:langString1.
    • Editorial note: skos:editorialNote, available as xsd:string or rdf:langString1.
    • History note: skos:historyNote, available as xsd:string or rdf:langString1.
    • Scope note: skos:scopeNote, available as xsd:string or rdf:langString1.
  • Relations
    • Narrower: skos:narrower, available as skos:Concept2.
    • Related: skos:related, available as skos:Concept2.
  • Mapping:
    • Close match: skos:closeMatch, to reference external skos:Concept3.
    • Exact match: skos:exactMatch, to reference external skos:Concept3.
    • Narrow match: skos:narrowMatch, to reference external skos:Concept3.
    • Related match: skos:relatedMatch, to reference external skos:Concept3.
info

Where are skos:broader, skos:topConceptOf and others?

Since those fields can be computed based on other fields, they are automatically set on save, and hidden to the user to prevent wrongful modifications.

Collection form​

Here are the different fields available, in their default order and groups:

  • Labels:
    • Label: skos:prefLabel, available as xsd:string or rdf:langString1.
    • Alternative label: skos:altLabel, available as xsd:string or rdf:langString1.
    • Hidden label: skos:hiddenLabel, available as xsd:string or rdf:langString1.
  • Notations
    • Notation: skos:notation. TODO, will change with new development.
  • Documentation
    • Definition: skos:definition, available as xsd:string or rdf:langString1.
    • Note: skos:note, available as xsd:string or rdf:langString1.
    • Change note: skos:changeNote, available as xsd:string or rdf:langString1.
    • Editorial note: skos:editorialNote, available as xsd:string or rdf:langString1.
    • History note: skos:historyNote, available as xsd:string or rdf:langString1.
    • Scope note: skos:scopeNote, available as xsd:string or rdf:langString1.
  • Concepts
    • Members: skos:member, available as skos:Concept2.

Agent, RightsStatement and LicenseDocument forms​

Those forms are pretty bare-bone and only have one field:

  • Label: rdfs:label, available as xsd:string or rdf:langString1.

How to find a concept to edit?

When you are in a concept scheme edition form containing various concepts, there are two techniques for quickly and accurately finding the concepts you want to edit:

  • using the tree navigation
  • or the command palette.

Using the tree navigation ​

(perfect solution for small concept schemes)

On the side of the screen you can see a navigation tree. In its simplest use, you can expand on each visible concept to open the view to deeper levels. You can easily browse the list for the concept you want to edit.

This navigation principle is perfectly adapted to concept schemes containing a reasonable amount of information. As soon as you get more complex data, we recommend using the command palette.

Search in tree navigation​

A search field is available at the top of the navigation. The search engine offers suggestions on the label of the concepts inside the concept scheme you are editing.

The search is carried out independently of navigation in the internal hierarchy of the item, and selecting a suggested result will take you directly to the relevant part of the form.

Using the command palette​

Amongst other features, the search presented in the previous section is also available in the command palette.

To access the command palette, you can use a keyboard shortcut or the main navigation menu bar:

  • You can use the following keyboard shortcut on any page:

    on Mac →  ⌘ **+ K 

    on Windows or Linux → Command (or Cmd) **+ K

  • Or you can use the search icon in the main navigation menu bar.

How to search a node with the command palette

  1. Open the command palette

  2. Use the search field at the top of the command palette

  3. Type what you’re looking for. The results suggestions and options will appear as you type.

  4. Go to the section titled "Go to node". You will see a list of suggestions based on the label of the concepts inside the concept scheme you are editing.

  5. Select a suggestion. You will be redirected to the relevant part of the form.

  1. The possibility to choose between either xsd:string or rdf:langString is provided thanks to the "monolingual" and "multilingual" options presents, respectively. For more details on how such field works, you can take a look at either the text field, the lang string field or the or field pages.↩
  2. See the node field page for more details about interacting with such field.↩
  3. See the iri field page for more details about interacting with such field.↩