This is an old revision of the document!
Table of Contents
Resource management (Researcher / WPLead)
4.1 General overview
The resource management section allows users with the Researcher or WPLead role to create new records (“items”) containing structured information about attacks that occurred in religious contexts.
Each resource represents an individual entry in the database and includes multiple fields related to:
- event context,
- victims and killers,
- modalities and motivations,
- sources and annotations.
All resources created by Researchers follow an approval workflow supervised by the WPLead, who is responsible for validating the content before publication.
4.2 Access and user menu
After logging in via Keycloak, users can access the resource management features through the user menu located in the top-right corner of the interface.
Clicking on the profile icon opens a menu with the following options:
| Option | Description |
|---|---|
| Dashboard | Provides access to the personal area containing submitted and draft requests. |
| Logout | Ends the active session and returns the user to the public view. |
(Figure 9)
4.3 Creating a new resource
By clicking the Add Resource button in the top toolbar, users are redirected to the resource creation page:
🧾 *Create new item*
The page consists of a structured form containing multiple thematic fields. Each field can be configured as:
- a text input,
- a select field (with predefined values or *Unknown*),
- or a numeric field.
Main form sections
| Category | Included fields |
|---|---|
| General information | Date, Status, Particular Occasion, Event |
| Location | Place-Based Worship, Place of Worship, City, Country |
| Attack data | Mode, Weapons, No. Injured, No. Victims |
| Victims | Victims’ Names, Victims’ Religion, Confession, Denomination |
| Religious / ideological aspects | Funeral Sermon, Martyrdom Acknowledgment |
| Killers | Killers’ Militant Group, Religion, Confession, Denomination, Ideology |
| Judicial data | No. Killers, No. Killers Survived, No. Killers Convicted, Trial, Sentence |
| Additional details and sources | Motive, Additional Notes, Sources, Regesto, Compilers |
All optional fields that are not filled in are automatically set to *Unknown*, ensuring data consistency across the platform.
At the bottom of the page, the following elements are available:
- Confirmation checkbox → *“By proceeding with the publication of the resource, the user accepts that it will be published on the PLORABUNT platform.”*
- Action buttons:
- Cancel → aborts the operation
- Save Draft → saves the resource as a draft in the personal Dashboard
(Figure 10)
4.4 Draft management (Researcher)
Resources saved as drafts are displayed in the personal Dashboard, accessible from the user menu.
Dashboard – Contributions
This page lists all requests created by the Researcher, including:
- Resource title / name
- Status (e.g. Draft, Submitted, Rejected, Approved)
- Available actions (depending on the status)
If no resources are available, the following message is displayed:
*No requests*
Available actions for Researchers
| Status | Available actions |
|---|---|
| Draft | Edit, Submit, Delete, View |
| Submitted | View (pending review) |
| Rejected | Edit (with visible rejection motivation), Resubmit, Delete |
| Approved | View |
(Figure 11)
4.5 Resource review (WPLead)
WPLeads can view all resources submitted by Researchers within their Dashboard.
For each resource, the WPLead can perform the following actions:
| Action | Description |
|---|---|
| View | Opens the complete resource record to verify the entered data. |
| Approve | Validates the resource and publishes it in the central database. |
| Reject | Rejects the request, providing a motivation for the decision. The resource is automatically returned to Draft status. |
| Delete | Permanently removes the resource. |
4.6 Complete workflow
The lifecycle of a resource follows the standard workflow outlined below:
Draft → Submitted → [Approved | Rejected → Editable Draft → Resubmitted]
Workflow details
- The Researcher creates a resource and saves it as a Draft.
- When ready, the resource is submitted for review.
- The WPLead reviews the request:
- If approved, the resource status becomes *Approved*.
- If rejected, a motivation is provided and the resource returns to *Draft* status.
- The Researcher can modify the resource and resubmit it for a new evaluation.
WPLeads can also directly create and submit new resources. In this case, the approval workflow is not applied, as WPLeads have the privileges required to validate and publish content autonomously.
Resources created by WPLeads are therefore immediately registered as *Approved*, without passing through the *Draft* or *Submitted* states.
4.7 Export permissions
All authenticated users — Admin, WPLead, and Researcher — are allowed to use the *Export* function to extract search results in CSV or JSON format, according to the criteria described in Chapter 3.
4.8 Admin role
The Admin user does not participate directly in the resource creation or validation workflow.
This role is intended exclusively for technical purposes, including:
- initial platform setup,
- management of roles and permissions,
- technical maintenance of the database and system configuration.