Knowledge Base

User Tools

Site Tools

Trace:
damsym:resource_management

Differences

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

Link to this comparison view

Next revision		Previous revision
damsym:resource_management [2026/01/15 16:28] – created finconsdamsym:resource_management [2026/02/12 12:47] (current) – [Dashboard and Contributions] fincons
Line 3: Line 3:
 ===== General Description ===== ===== General Description =====
  
-The **Add Resource** section allows authenticated users to create, edit, and monitor textual resources within the DaMSym system. +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 can subsequently be included in the semantic search engine and made publicly available for consultation. + 
-The entire management process is regulated by a multi-level approval workflow, which distinctly involves the roles of Researcher, Reviewer, and WP Lead.+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. This model ensures that every new resource is verified and validated before final publication.
  
Line 12: Line 15:
 ===== Adding New Resources (Add Resource) ===== ===== 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. +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 filling in the mandatory and optional fields required for the selected language. (Figures 12–14)+
  
-The resource creation process follows these steps:+From this section, it is possible to upload a new resource by completing the mandatory and optional fields provided for the selected language.
  
-  1. **Language selection** → the user selects one of the available linguistic domains (Arabic, Slavic, Greek, Latin, Sanskrit). +The creation of a resource follows these steps:
-  2. **Field completion** → depending on the language, the required metadata fields are displayed (title, author, work, text, description, etc.). +
-  3. **Draft saving** → by clicking **Save draft**, the resource is stored in *Draft* status within the **Contributions** section of the Dashboard. +
-  4. **Submission for approval** → after review, the user can select **Submit** to send the resource to the WP Lead for evaluation.+
  
-All mandatory fields must be completed in order to submit a resource; otherwise, the system highlights validation errors.+  * **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.
  
-Figure 9, Create new item   +All mandatory fields must be completed in order to submit a resource; otherwise, the system displays validation errors.
-Figure 10, Add Resource   +
-Figure 11, Add Slavonic resource+
  
 +{{damsym:damsym_create_new_item.png?650|Create new item}}
 ---- ----
 +{{damsym:damsym_add_latin_res.png?700|Add Latin Resource}}
 +----
 +{{damsym:damsym_add_church_slavonic_res.png?700|Add Church Slavonic Resource}}
 +----
 +{{damsym:damsym_add_greek_res.png?700|Add Greek Resource}}
 +----
 +{{damsym:damsym_add_arabic_res.png?700|Add Arabic Resource}}
  
-===== Module Structure and Behaviour =====+----
  
-The resource creation and editing module is composed of multiple adaptive sections that dynamically update according to the selected language.+===== Structure and Behavior of the Form =====
  
-**Common fields:** +The resource submission and editing form is composed of multiple adaptive sections, which dynamically update according to the selected language. 
-  * Title + 
-  * Language+==== Common Fields ==== 
 + 
 +  * Work title
   * Author   * Author
   * Text   * Text
-  * Description +  * License 
-  * Date (not available for the Sanskrit language)+  * Comments 
 +  * Date (corresponding to the Period field in the Arabic language, and not present in the Sanskrit form)
  
-**Language-specific fields:** +==== Available Actions in the Form ====
-  * **Slavic**: font selection field (required for correct character rendering)+
  
-**Add Font:** +  * **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). 
-  * For the **Church Slavonic** language, the **Add Font** functionality is available, allowing the integration of new fonts or specific character sets into the display system. +  * **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. 
-  * This function is accessible to the WP Lead from the Dashboard and ensures correct graphical rendering of texts using special characters.+  * **Cancel** → cancels the ongoing modifications and allows the user to return to the homepage without saving the changes made.
  
-**Available actions within the module:** +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.
-  * **Save draft** → saves the resource in Draft status +
-  * **Submit** → sends the resource to the WP Lead for approval; this action is available in the Dashboard next to Draft resources, together with the icons: +
-    * 🗑️ Delete (delete) +
-    * ✏️ Edit (edit) +
-    * 👁️ View (view) +
-  * **Cancel** → cancels the current changes +
-  * **Delete** → permanently deletes the selected resource +
- +
-During saving, the system performs automatic validation checks to ensure that all required fields are correctly filled in and consistent with the selected language.+
  
 ---- ----
Line 64: Line 65:
 ===== Creation and Approval Workflow ===== ===== Creation and Approval Workflow =====
  
-Each resource created within DaMSym follows a defined status workflow that regulates interactions between Researcher, Reviewer, and WP Lead.+Each resource created within DaMSym follows a defined status path, regulating interactions between Researcher, Reviewer, and WP Lead.
  
-^ Status ^ Description ^ Enabled role ^ +^ Status ^ Description ^ Enabled Role ^ 
-| **Draft** | Resource saved as a draft. Visible and editable only by the author. | Researcher / Reviewer |+| **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 | | **Waiting for approval** | Resource submitted to the WP Lead for approval. | Researcher / Reviewer |
 | **Approved** | Resource approved and made searchable within the corpus. | WP Lead | | **Approved** | Resource approved and made searchable within the corpus. | WP Lead |
-| **Rejected** | Resource rejected by the WP Lead, optionally with an explanatory note. | WP Lead |+| **Rejected** | Resource rejected by the WP Lead, possibly with an explanatory note. | WP Lead | 
 + 
 +==== Operational Flow Summary ==== 
 + 
 +^ Step ^ Action ^ Responsible Role ^ 
 +| 1 | Add Resource | Researcher / Reviewer / WP Lead | 
 +| 2 | Save draft | Researcher / Reviewer | 
 +| 3 | Confirm submission | Researcher / Reviewer | 
 +| 4 | Review resource | WP Lead | 
 +| 5a | Approve → Published in search | WP Lead | 
 +| 5b | Reject → Returns to Draft | WP Lead | 
 + 
 +This model guarantees accurate control and complete traceability of the editorial process.
  
-**Summary workflow:** 
  
-Researcher / Reviewer → Add Resource   
-       ↓   
-      Save draft   
-       ↓   
-     Confirm submission   
-       ↓   
-     WP Lead review   
-       ↓   
-Approve → Published in search   
-Reject → Returns to Draft   
  
-This model ensures accurate control and complete traceability of the editorial process. 
  
 ---- ----
Line 91: Line 92:
 ===== Dashboard and Contributions ===== ===== Dashboard and Contributions =====
  
-The **Dashboard** is the personal resource management area for all authenticated users. +The Dashboard is the personal resource management area for all authenticated users. 
-It can be accessed via the user menu (profile icon in the top-right corner) and consists of a table listing the resources associated with the user or their working group.+ 
 +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: The table displays:
-  * resource title, 
-  * language, 
-  * current status (Draft, Waiting for approval, Approved, Rejected), 
-  * creation or modification date, 
-  * available actions (Edit, Confirm, Delete). 
  
-Users with the Researcher and Reviewer roles can manage only their own resources, while WP Leads can view the complete list and intervene in approval or rejection processes. (Figure 15)+  * 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.
  
-Figure 12, Approve / Reject+{{damsym:damsym_approve_reject.png?700|Approve / Reject}}
  
 ---- ----
Line 110: Line 112:
  
 The WP Lead plays a key supervisory and control role over the entire editorial workflow. The WP Lead plays a key supervisory and control role over the entire editorial workflow.
-In addition to standard creation and editing functions, the WP Lead has the following additional privileges in the Dashboard:+ 
 +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;   * approval or rejection of resources submitted by researchers;
   * deletion of non-compliant content;   * deletion of non-compliant content;
-  * visualization and management of feedback (**See Ratings**); +  * visualization and management of feedback (See Ratings function); 
-  * **Rating Export** section; +  * access to the Ratings Export section; 
-  * **Add Font** section, with the ability to integrate new characters or graphical variants into the search system.+  * 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. These functions make the WP Lead the primary authority responsible for the quality and consistency of published content.
Line 125: Line 128:
  
 Every creation, modification, or approval operation is recorded in the system with the following parameters: Every creation, modification, or approval operation is recorded in the system with the following parameters:
 +
   * ID of the user who performed the action;   * ID of the user who performed the action;
   * type of operation (create, edit, approve, reject, delete);   * type of operation (create, edit, approve, reject, delete);
-  * operation timestamp; +  * timestamp of the operation; 
-  * optional review notes or justifications.+  * any review notes or motivations.
  
-This ensures a high level of auditability and transparency, in compliance with the security policies of ITSERR and RESILIENCE.+This ensures a high level of auditability and transparency, in line with the security policies of ITSERR and RESILIENCE.
  
 ---- ----
Line 136: Line 140:
 ===== Resource Modifications ===== ===== Resource Modifications =====
  
-The system includes advanced editing tools that allow intervention on already saved resources:+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 Text (Corrections)** → for modifications or suggestions on existing texts. 
-  * **Edit Metadata** → for updating or correcting descriptive information; +  * **Edit Metadata (Corrections)** → for modifying metadata. 
-  * **Add Metadata** → for adding new informational fields, such as alternative titles or additional sources.+  * **Add Metadata** → for adding new metadata.
  
-All modifications are tracked by the system and submitted for verification by the WP Lead, who can approve or reject the updates. +All modifications are tracked within the system and submitted for verification by the WP Lead, who approves or rejects the updates. 
-These features make data management dynamic and collaborative, in line with the academic validation principles of the ITSERR project.+ 
 +These functionalities make data management dynamic and collaborative, in accordance with the academic validation principles of the ITSERR project. 
 + 
 +----
  
damsym/resource_management.1768490900.txt.gz · Last modified: by fincons