Differences

This shows you the differences between two versions of the page.

--- plorabunt:introduction [2026/01/14 15:59] – fincons
+++ plorabunt:introduction [2026/01/15 16:50] (current) – [Project context] fincons
@@ Line 9: / Line 9: @@
 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 ====
+==== Research and data exploration approach ====
-Access to the PLORABUNT platform is managed through Keycloak (D4Science Identity Provider), allowing users to authenticate via several academic or social identity providers:
+PLORABUNT is designed to support the structured exploration and analysis of episodes of violence or attacks occurring in places of worship through a data-driven research approach.
-  * Academic / Other
+The platform provides advanced search functionalities that allow users to query the dataset using both free-text search and structured filters.
-  * Google
+Search results can be refined according to multiple criteria, including thematic categories, geographic location, and temporal range.
-  * LinkedIn
-  * Twitter
-  * GitHub
-  * ORCID
-  * CNR-ISTI
-Unauthenticated users can still access and use the public search functionality.
+PLORABUNT integrates interactive visualization tools that enable users to analyze data both in list-based views and through geographic representations, supporting the identification of spatial patterns and trends.
-However, they are not allowed to create or modify resources, nor to export search results. (Figure 1)
+This approach allows researchers to perform both qualitative and quantitative analysis on structured datasets, facilitating comparative studies, thematic investigations, and cross-regional analysis within a shared research environment.
-==== 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.