User Tools

Site Tools


damsym:resource_management

This is an old revision of the document!


Resource Management

General Description

The Add Resource section allows authenticated users to add resources to the database within the DaMSym system.

Each resource represents a unit of content (text, excerpt, or document) that may subsequently be included in the semantic search engine and made available for public consultation.

The entire management process is governed by a multi-level approval workflow, which distinctly involves the roles of Researcher, Reviewer, and WP Lead.

This model ensures that every new resource is verified and validated before final publication.


Adding New Resources (Add Resource)

Once authenticated, the user sees the “Add Resource” button in the top navigation bar, which provides access to the submission form.

From this section, it is possible to upload a new resource by completing the mandatory and optional fields provided for the selected language.

The creation of a resource follows these steps:

  • Language selection → The user selects one of the available linguistic domains (Arabic, Church Slavonic, Greek, Latin, Sanskrit).
  • Field completion → Depending on the selected language, the required metadata fields are displayed (Work title, Author, Date, Text, Comments, etc.).
  • Saving the draft → By clicking the Save draft button, the resource is saved in Draft status in the Contributions section of the Dashboard.
  • Submission for approval → After reviewing the content, the user may click Submit to send the resource to the WP Lead for evaluation and approval.

All mandatory fields must be completed in order to submit a resource; otherwise, the system displays validation errors.


Structure and Behavior of the Form

The resource submission and editing form is composed of multiple adaptive sections, which dynamically update according to the selected language.

Common Fields

  • Work title
  • Author
  • Text
  • License
  • Comments
  • Date (corresponding to the Period field in the Arabic language, and not present in the Sanskrit form)

Available Actions in the Form

  • Submit → sends the resource to the WP Lead for approval. This action is available in the Dashboard, next to a resource in Draft status, together with the icons 🗑️ Delete (to remove), ✏️ Edit (to modify), and 👁️ View (to display).
  • Save draft → allows the user to save the resource in Draft status without submitting it for approval. After saving, the resource becomes visible in the user’s Dashboard.
  • Cancel → cancels the ongoing modifications and allows the user to return to the homepage without saving the changes made.

During the saving process, the system performs automatic validation checks to ensure that all required fields are correctly completed and consistent with the selected language.


Creation and Approval Workflow

Each resource created within DaMSym follows a defined status path, regulating interactions between Researcher, Reviewer, and WP Lead.

Status Description Enabled Role
Draft Resource saved as draft. Visible and editable only by the author. Researcher / Reviewer
Waiting for approval Resource submitted to the WP Lead for approval. Researcher / Reviewer
Approved Resource approved and made searchable within the corpus. WP Lead
Rejected Resource rejected by the WP Lead, possibly with an explanatory note. WP Lead

Operational Flow Summary

Researcher / Reviewer / WP Lead → Add Resource

      ↓  
   Save draft  
      ↓  
Confirm submission  
      ↓  
  WP Lead review  
      ↓  

Approve → Published in search Reject → Returns to Draft

This model guarantees accurate control and complete traceability of the editorial process.


Dashboard and Contributions

The Dashboard is the personal resource management area for all authenticated users.

It can be accessed through the user menu (profile icon in the upper-right corner) and consists of a table listing the resources associated with the user or their working group.

The table displays:

  • Resource Title
  • Language
  • Current status (Draft, Waiting for approval, Approved, Rejected)
  • Creation or modification date

Users with the roles of Researcher and Reviewer can manage only their own resources, whereas WP Leads can view the entire list and intervene in approval or rejection processes.


Role of the WP Lead

The WP Lead plays a key supervisory and control role over the entire editorial workflow.

In addition to standard creation and editing functionalities, the WP Lead has additional privileges within the Dashboard:

  • approval or rejection of resources submitted by researchers;
  • deletion of non-compliant content;
  • visualization and management of feedback (See Ratings function);
  • access to the Ratings Export section;
  • access to the Add Font section, with the possibility of integrating new characters or graphic variants into the Church Slavonic search system.

These functions make the WP Lead the primary authority responsible for the quality and consistency of published content.


Security and Traceability

Every creation, modification, or approval operation is recorded in the system with the following parameters:

  • ID of the user who performed the action;
  • type of operation (create, edit, approve, reject, delete);
  • timestamp of the operation;
  • any review notes or motivations.

This ensures a high level of auditability and transparency, in line with the security policies of ITSERR and RESILIENCE.


Resource Modifications

The system includes advanced editing tools that allow users to intervene on resources that have already been saved:

  • Edit Text (Corrections) → for modifications or suggestions on existing texts.
  • Edit Metadata (Corrections) → for modifying metadata.
  • Add Metadata → for adding new metadata.

All modifications are tracked within the system and submitted for verification by the WP Lead, who approves or rejects the updates.

These functionalities make data management dynamic and collaborative, in accordance with the academic validation principles of the ITSERR project.


damsym/resource_management.1770893528.txt.gz · Last modified: by fincons