Example for a Thesaurus Curation Workflow
Example for a Thesaurus Curation Workflow
At the latest when going productive (or online) with a thesaurus project the question arises how to handle curation and updates. The following workflow provides a blueprint on how such a workflow could be managed with PoolParty.
The suggested configuration here is to have two PoolParty servers installed:
Server 1, staging server: use to do the actual curation of the vocabulary
Server 2, production server: use to publish the latest version of the vocabulary
See the setup architecture diagram below.
So these are the two main tasks:
Curation of the vocabularies on the staging server
Updates of the vocabularies to the production server
Curation of Vocabularies on the Staging Server
The curation process includes the following tasks:
Adding new entries / vocabularies
Editing and updating
Review of changes
Adding New Entries / Vocabularies
Suggesting new entries or new vocabularies at the moment should be done on request by the thesaurus management team. Request can be handled for example through email or webforms.
Tip
PoolParty also offers an API call which enables users to suggest concepts/terms via a web-based interface.
Such suggestions can thus be stored in existing vocabularies and can be curated directly in the PoolParty environment by the thesaurus management team.
Editing and Updating
Editing, deleting and updating should be done by the thesaurus management team following the documentation on how to work with PoolParty.
Review of Changes
Reviewing of changes should be done by the thesaurus management team based on the workflow function of PoolParty:
Basically a review of all changes since the last version on time or a continuous monitoring of changes through working on a new version can be done.
Update of Vocabulary to Production Server
The update process includes the following tasks:
Export of vocabularies from staging server
Import of vocabularies to production server
Update of the extraction model on the production server
These steps can be executed from the PoolParty user interface, via the PoolParty API or by using the optional Mirror App. It is recommended that you export and keep a copy of the project after updating, so that a record of all released versions is available.