This is an old revision of the document!
Table of Contents
Introduction
Project context
PLORABUNT is a tool developed within Work Package 6 (WP6) of the ITSERR project, aimed at the collection, management, and analysis of episodes of violence or attacks occurring in places of worship.
The system is integrated into the RESILIENCE RI ecosystem, with the goal of providing an advanced research platform that can be filtered according to thematic and geographic parameters, and that includes collaborative resource management functionalities.
This approach enables researchers to explore structured data related to attacks in religious contexts, supporting both qualitative and quantitative analysis within a shared research environment.
Platform access
Access to the PLORABUNT platform is managed through Keycloak (D4Science Identity Provider), allowing users to authenticate via several academic or social identity providers:
- Academic / Other
- Google
- LinkedIn
- Twitter
- GitHub
- ORCID
- CNR-ISTI
Unauthenticated users can still access and use the public search functionality. However, they are not allowed to create or modify resources, nor to export search results.
User roles
The platform defines three main user profiles, each with specific responsibilities and permissions.
| Role | Description | Main permissions |
|---|---|---|
| Admin | Technical user account employed by the management team for setup and maintenance operations. | Backend management, system maintenance, configuration of roles and permissions. |
| WPLead | User responsible for reviewing and validating requests submitted by Researchers. | Can approve, reject, delete, or view submitted requests. |
| Researcher | User enabled to create new resources (“items”) and manage their own submissions. | Can create, edit, submit, view, and delete their own requests. |
Requests submitted by Researchers are reviewed by the WPLead according to the following logic:
- If approved, the resource is published in the central database.
- If rejected, the resource is returned to Draft status, accompanied by a rejection motivation that allows the user to modify and resubmit the request.
This workflow ensures data quality and consistency before publication, while maintaining an efficient and collaborative validation process.