PoolParty is an editor for SKOS vocabularies; it is not an editor for generic RDF. That means:
The SWC web site has some background information on how PoolParty uses SKOS:
https://help.poolparty.biz/pp/poolparty-overview/poolparty-skos-rdf-and-uris
More specifically, here are some details about what must be included in a SKOS file that is to be imported into PoolParty:
You have a couple of options for checking your vocabulary data, before or during the import process. Please use at least one of these:
ARDC staff have experience in working with RDF imported into PoolParty. Here are some practical observations based on this experience:
skos:Collection
and a skos:ConceptScheme
(contra SKOS integrity constraint S37), PoolParty will report an "internal server error" and the project will break.skos:hasTopConcept
property is necessary and sufficient to link a concept into the hierarchy at the top level. That is, the skos:topConceptOf
property plays no role in determining what PoolParty considers to be a top concept.skos:topConceptOf
the concept scheme. It did not appear in the hierarchy. Importing more RDF that specifies that the concept scheme skos:hasTopConcept
the concept causes the concept to appear in the hierarchy.skos:hasTopConcept
property for imported top concepts. If you wish an imported concept to have the skos:hasTopConcept
property, this must also be included in the imported data.skos:topConceptOf
property for imported top concepts. If you wish an imported concept to have the skos:topConceptOf
property, this must also be included in the imported data.skos:hasTopConcept
and skos:topConceptOf
properties.skos:narrower
properties from a top concept down to a concept is necessary and sufficient to link such a non-top concept into the hierarchy. That is, the skos:broader
property plays no role in determining what PoolParty considers to be a broader concept.skos:broader
to a top concept that is already visible in the user interface. The new concept did not appear in the hierarchy. Importing more RDF that specifies that the existing top concept has skos:narrower
the new concept causes the new concept to appear in the hierarchy.skos:narrower
from a top concept that is already visible in the user interface, but does not include the corresponding skos:broader
property. The new concept did appear in the hierarchy.skos:narrower
property for imported concepts that are otherwise linked to another concept using skos:broader
. If you wish an imported concept to have the skos:narrower
property, this must also be included in the imported data.skos:broader
property for imported concepts that are otherwise linked to another concept using skos:narrower
. If you wish an imported concept to have the skos:broader
property, this must also be included in the imported data.skos:broader
and skos:narrower
properties.dcterms:title
property for their title, and need it so that they show up in the Collections list. So before importing, you need to add an extra triple for each Collection so that PoolParty can cope with it. If you import existing vocabulary data without having added these triples, the Collections list shows a table with blank titles, which makes it unusable.