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:
All resources created by Researchers follow an approval workflow supervised by the WPLead, who is responsible for validating the content before publication.
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. |
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:
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:
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:
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 |
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. |
The lifecycle of a resource follows the standard workflow outlined below:
Draft → Submitted → [Approved | Rejected → Editable Draft → Resubmitted]
Workflow details
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.
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.
The Admin user does not participate directly in the resource creation or validation workflow.
This role is intended exclusively for technical purposes, including: