Skip to main content

Prerequisites for Importing non-PoolParty SKOS Thesauri

Abstract

Here are the prerequisites for Importing non-PoolParty SKOS Thesauri.

If you import SKOS thesauri which were not created with PoolParty, there are certain prerequisites a file should satisfy in order to be imported smoothly. You can verify the consistency of your imported data via Quality Management in PoolParty. Additionally, SWC provides free online services for checking the quality of SKOS vocabularies (http://qskos.poolparty.biz/login).

Prerequisites for importing thesauri into PoolParty are:

  • The file has to be valid RDF and should be valid SKOS.

    Tip

    RDF validity can be checked at http://www.w3.org/RDF/Validator/. Several SKOS checks can be made at http://www.w3.org/2004/02/skos/validation.

  • There has to be a skos:ConceptScheme (which represents the thesaurus itself) and one or more concepts connected to it via skos:hasTopConcept / skos:topConceptOf (refer PoolParty, SKOS, RDF and URIs about SKOS definition and PoolParty).

  • All skos:ConceptSchemes have to be labeled with one of the following properties in the default language of the project:

    • dc:title

    • dcterms:title

    • rdfs:label

    • skos:prefLabel

      Note

      dcterms:title is the default property for labeling concept schemes in PoolParty. If one of the other properties is used a dcterms:title property is added.

  • All concepts should be connected to a parent concept via skos:broader / skos:narrower or to a concept scheme via skos:hasTopConcept / skos:topConceptOf.

  • URIs shouldn't contain space characters.

  • Concepts must have a preferred label in the default language of the project.

  • The labels of concepts and concept schemes should have language tags attached to denote which language the label is in.

  • Concepts shouldn't have double quotes in their preferred label.

Find additional for download available taxonomies and thesauri in our vocabulary hub.

In this section: