Repository and Graph Structure of Data Stored in PoolParty

14/04/2025

Abstract

PoolParty generates data which spreads across different graph databases. This section summarizes the names of these graph databases in tabular form.

PoolParty supports configuration of an external graph database, which can be useful in the following cases:

Corpus Management
Exporting RDF Project DataExport RDF Project Data
Ontology Management
Sorting extraction results

The data created by PoolParty is spread across different repositories where each repository can be seen as one graph database.

	Repository	Content description
System Repositories	PPT System	Metadata of all projects on a PoolParty Thesaurus server.
		Metadata of all corpora for all projects on a PoolParty Thesaurus server.
Project Repositories	Project repositories	Each repository contains project specific data only.
Project Repositories	Corpus repositories	Corpus data and the annotations from Corpus Management.
User Repository		Information on users and user groups.
Custom Schemes Repository		Metadata of all custom schemes and ontologies on a PoolParty Thesaurus server.
GraphSearch Repository		Metadata of all corpora for all projects on a PoolParty Thesaurus server.

The project repositories contain several named graphs. Default graphs are created when either the project or its first custom scheme is created. All optional graphs are only created if the respective data is available.

	Data	Graph name	Note
Default Graphs (Projects)	VoID	`<<baseUrl>/<projectId>/metadata/void>`	This graph contains metadata of the project e.g. number of concepts, creation date etc.
	ADMS	`<<baseUrl>/<projectId>/metadata/adms>`	This graph contains ADMS information on the project: see Project Data Stored as ADMS Graph. ADMS is a vocabulary used to describe semantic assets. See also: https://www.w3.org/TR/vocab-adms/
	Quality settings	`<<baseUrl>/<projectId>/thesaurus/qualitySettings>`	These graphs contain the project quality settings. See also: Define Quality Settings
	Notification settings	`<<baseUrl>/<projectId>/notification/settings>`	This graph stores information on the notification settings in the Approval Workflow.
	RDF Editor	`<<baseUrl>/<projectId>/metadata/rdfeditor>`	Stores the data of RDF edits created in the RDF Editor.
Default Graphs (Thesaurus Management)	Thesaurus data	`<<baseUrl>/<projectId>/thesaurus>`	This graph contains the data of concepts, concept schemes, collections and SKOS-XL labels.
	History data	`<<baseUrl>/<projectId>/thesaurus/history>`	This graph contains the history data related to all PoolParty actions. See also: PoolParty History
	URI settings	`<<baseUrl>/<projectId>/thesaurus/uriSettings>`	This graph stores the URI settings for a project. See also: URI Management - Overview
	Local users	`<<baseUrl>/<projectId>/thesaurus/users>`	Contains all local user profiles (excluding default user roles). For details refer to: PoolParty User Administration Setup Using Keycloak
Optional Graph (Projects)	Template configurations	`<<baseUrl>/<projectId>/configuration>`	Stores the definitions of templates for project export. After you have created a project export template, its metadata, such as creator, modification date, and configuration triples, appears here.
Optional Graphs (Thesaurus Management)	SKOS Notes	`<<baseUrl>/<projectId>/thesaurus/notes>`	This graphs contains SKOS change/editorial/history notes. See also: Adding Notes to your Concepts
	Workflow data	`<<baseUrl>/<projectId>/thesaurus/workflow>`	This graph contains the workflow data (state, assignee) of concepts or SKOS-XL labels. See also: Approval Workflow
	Deprecated resources	`<<baseUrl>/<projectId>/thesaurus/deprecated>`	This graph contains the information on deprecated/deleted resources such as concepts and concept schemes. See also: Deleting Concepts & Subtrees
	Suggested concepts	`<<baseUrl>/<projectId>/thesaurus/suggestions>`	This graph contains all suggested concepts introduced via the respective API. See also: Web Service Method: Suggest Concept.
	Quality management data	`<<baseUrl>/<projectId>/thesaurus/qualityReport>`	This graph contains the quality report data of the last report. See also: Create a Quality Report
	SPARQL lists	`<<baseUrl>/<projectId>/thesaurus/sparqllists>`	This graph contains information about all SPARQL lists created. See also: SPARQL Lists
	Batch linking data	`<<baseUrl>/<projectId>/thesaurus/linking>`	This graph contains all information on the last batch linking task. See also: Project Linking - Batch Linking
	Concepts added to the exclude-list	`<<baseUrl>/<projectId>/thesaurus/blacklist>`	This graph contains all concepts and terms added to the exclude-list. See also: Add Concepts and Terms to Exclude-list
	Linked Data	`<<baseUrl>/<projectId>/linkeddata/<ld-source>> e.g. <<baseUrl>/<projectId>/linkeddata/en/dbpedia>`	This graphs contain data copied from a linked data source. The name of the graph depends on the linked data sources used. See also: Linked Data Enrichment with PoolParty
	Categories data	`<<baseUrl>/<projectId>/linkeddata/categories>`	Linked data categories retrieved using the linked data feature will be stored in this graph.
Temporary Graphs (Data Validator & Reasoning)	Import linked projects data	`<<baseUrl>/<projectId>/thesaurus/import/projects>`	The imported project data will be stored in this graph. See also: PoolParty RDF Import & Export
	Import schema data	`<<baseUrl>/<projectId>/thesaurus/import/schema>`
	Import project metadata	`<<baseUrl>/<projectId>/thesaurus/import/metadata>`
	Reasoning schema data	`<<baseUrl>/<projectId>/thesaurus/reasoning>`
Optional Graphs (Corpus Management)	Candidate concepts	`<<baseUrl>/<projectId>/corpus/candidates>`	This graph contains candidate concepts that have been selected in the corpus analysis. See also: Candidate Concepts List
	Disambiguation	`<<baseUrl>/<projectId>/corpus/disambiguation>`	This graph contains the project disambiguation settings used for extraction. See also: Thesaurus Based Disambiguation of Annotated Concepts
Optional Graphs (Semantic Classifier)	Document classification	`<<baseUrl>/<projectId>/classification>`	The classification results for the trained classifiers will be stored in this graph. See also: Semantic Classifier - Overview
	Indexed documents	`<<baseUrl>/<projectId>/documents>`	This graph contains all documents uploaded during training and testing classifiers.

Please note that projectIDs used in graph URIs are textual project identifiers and not UUIDs. A textual identifier is generated during project creation as part of the URI generation process, which, along with the project’s base URI, forms the complete project URI. This URI can be found at the Triples tab after navigating to the project's details view. The image below shows that the URI http://server.com/ProjectExample consists of base URI (starting with "http:// ") and textual project identifier ProjectExample.

In this section: