[logseq-plugin-git:commit] 2026-01-30T22:32:20.350Z

pages/todoist___2026-02-03.md

@@ -24,4 +24,29 @@
   todoist-project:: #📧EmailsToAnswer
   todoist-due:: 2026-02-03
   todoist-desc:: From: disorbo@unisannio.it Received: 2026-01-20T09:03:13Z ✉: [Web Link](https://outlook.office365.com/owa/?ItemID=AAMkADM1NGNiNjk0LTY0ZGUtNDgzOC04MDM5LWNhODNkYWNjNjU4YwBGAAAAAACT6qp78kRgRKuUMBdWEga%2FBwCOhWlC8F7PRKzlljZYZYQmAAAAAAEMAACOhWlC8F7PRKzlljZYZYQmAAidZtYrAAA%3D&exvsurl=1&viewmodel=ReadMessageItem) --- Here's a summary of the email content and the corresponding actionable task: **Task Summary:** The email is a rejection notification from the Journal of Systems and Software (JSS) for the submission "Examining Fairness Issues in Machine Learning-based Systems" (Ref. No.: JSSOFTWARE-D-25-01604). While the paper is rejected, the editor strongly advises resubmission after addressing the reviewers' detailed comments. The reviewers highlight significant areas for improvement in the manuscript's framing of fairness, integration of related work, methodological structure and detail (especially for the qualitative analysis), dataset selection justification, and the significance and implications of the results. The resubmitted paper will be treated as a new submission. **Actionable Task:** **Task:** Revise and Resubmit Paper to Journal of Systems and Software **Description:** The submission "Examining Fairness Issues in Machine Learning-based Systems" (Ref. No.: JSSOFTWARE-D-25-01604) has been rejected by the Journal of Systems and Software. However, the editor encourages resubmission after addressing detailed reviewer comments. Key areas for improvement include: * **Framing of Fairness:** Clearly define whether fairness is treated as a technical, socio-technical, or hybrid concern. * **Related Work:** Synthesize the literature into a coherent argument rather than an enumerative survey. * **Methodology:** * Present a unified methodological structure with clear workflows and transitions between phases. * Provide more detailed explanations for the qualitative coding process, including iteration, rater interaction, and reliance on LLM summaries. * Clarify the sequencing of methodological steps and ensure logical dependencies. * Justify dataset selection criteria and report exclusion numbers. * Ensure consistency between research questions and the role of LLMs. * Consider extending the dataset size if feasible through pre-screening. * **Results and Discussion:** * Explicitly discuss novel vs. incremental findings and align with previous empirical work. * Provide concrete examples of implications for practitioners. * Consider adding new research questions and discussions. * Clarify the rationale for using large language models. * **Overall Cohesion:** Improve the integration and cohesion across different methods employed in the study. **Recommended Actions:** 1. **Thoroughly read and understand all reviewer comments.** 2. **Develop a detailed plan to address each comment.** Categorize comments by theme (e.g., Introduction, Methodology, Results, Discussion) to facilitate systematic revision. 3. **Rewrite sections of the manuscript** based on the reviewer feedback, focusing on the identified weaknesses. 4. **Prepare a comprehensive response letter** detailing how each reviewer comment has been addressed. 5. **Ensure the resubmitted manuscript is treated as a NEW submission** but consider disclosing the original submission information and reference number. 6. **Consult empirical research guidelines** (e.g., Paul Ralph et al. 2020) for structuring the revised manuscript and methodology. 7. **Consider creating a methodological diagram** to clarify the workflow. **No Deadline:** The email does not specify a deadline for resubmission. --- Buongiorno a tutti, vi giro la mail ricevuta da JSS. Saluti, Andrea ---------- Forwarded message --------- Da: Journal of Systems and Software <em@editorialmanager.com> Date: lun 19 gen 2026 alle ore 10:59 Subject: Decision on your submission
+  todoist-status:: ◼️
+- [[2026-02-03]] Preparare missione per Difesa Dottorato Unimib
+  todoist-id:: [6fpJW7WhfQMvWGCc](https://todoist.com/showTask?id=6fpJW7WhfQMvWGCc)
+  todoist-project:: #✈ Missioni
+  todoist-due:: 2026-02-03
+  todoist-desc:: Partenza 18 Febbraio mattina ritorno 19 Febbraio pomeriggio
+  todoist-status:: ◼️
+- [[2026-02-03]] Missione thesis defense Barcellona
+  todoist-id:: [6fpMJPHCF85RJH7c](https://todoist.com/showTask?id=6fpMJPHCF85RJH7c)
+  todoist-project:: #✈ Missioni
+  todoist-due:: 2026-02-03
+  todoist-desc:: Weblink: [Outlook](https://outlook.office365.com/owa/?ItemID=AAMkADM1NGNiNjk0LTY0ZGUtNDgzOC04MDM5LWNhODNkYWNjNjU4YwBGAAAAAACT6qp78kRgRKuUMBdWEga%2FBwCOhWlC8F7PRKzlljZYZYQmAAAAAAEMAACOhWlC8F7PRKzlljZYZYQmAAicJKLJAAA%3D&exvsurl=1&viewmodel=ReadMessageItem)
+  todoist-status:: ◼️
+- [[2026-02-03]] Re: About a possible EULiST application for a stay of our PhD student Zakaria Hachm in 2026 at UAQ-DISIM-SWEN Group
+  todoist-id:: [6fWMgWwmjj3QF6Xg](https://todoist.com/showTask?id=6fWMgWwmjj3QF6Xg)
+  todoist-project:: #👷 WORK
+  todoist-due:: 2026-02-03
+  todoist-desc:: [Web Link](https://outlook.office365.com/owa/?ItemID=AAkALgAAAAAAHYQDEapmEc2byACqAC%2FEWg0AjoVpQvBez0Ss5ZY2WGWEJgAIhQbttwAA&exvsurl=1&viewmodel=ReadMessageItem) Okay, here's a detailed description of the task created from the email, formatted as I would present it as an agent summarizing a task creation request. This description includes actionable items: ## Task Description: UQAM-SHM Zakharia Hachm EULiST Application Confirmation - 2026 **Subject:** Final Review and Action Item – EULiСТ Application for PhD Student Zakharia Hachm **Purpose:** Formal confirmation and necessary actions for the UQAM-SHM (Staff Headmaster’s Management, potentially referencing a student’s PhD program) to move ahead with the potential EULiSt application for Zakaria Hachm in the year 2026, with a focus on collaboration within the SWEN Group (likely signifying a strategic partnership or shared goal). **Context:** This task was created from an email discussing the possibility of developing an EULiSt application. A crucial step requires a final sign-off from UQAM, the managing entity, on the project’s trajectory and commitment. **Actionable Tasks:** 1. **Client Contact & Schedule Meeting:** Immediately contact the UQAM Headmaster/relevant stakeholders (specifically, the SHM team) to request a meeting to discuss the EULiСТ project in greater detail. Aim for a brief, focused initial meeting to gauge their current position on the application and ensure alignment. * **Estimated Duration:** 30-60 minutes * **Priority:** Critical - Deadline is pending further discussion with stakeholders to ensure a coordinated approach. 2. **Internal Review & Data Audit (Mandatory):** * Gather relevant project documents: including preliminary scope documents, budget outlines, timeline proposals, and existing partnership agreements related to the SWEN Group. * Review existing internal policies surrounding student EULiSt projects and any guidelines regarding collaboration with international partners. * **Documentation Required:** Document review and potential clarification is required from internal teams to ensure adherence to all applicable regulations. 3. **Status Confirmation/Quasi-Approval – Urgent Action Requested:** Contact the UQAM team to formally confirm whether a ‘quasi-approval’ is needed at this stage before moving into significant documentation and preparation. This confirms the project’s timeline can be executed safely by the UQAM stakeholders. **Timeline:** (Provide an estimated timeframe for completion – estimate 1-2 weeks) - Consider a timeline of the following: 1.1 Initial Meeting; 1.2 Content Review/Data Retrieval; 1.3 Status Confirmation **Notes/Sensitivity:** This is a high-priority item, representing a significant investment for both the student and UQAM's strategic planning. Ensure all communications are conducted professionally and maintain confidential information within the scope of UQAM’s data. --- **Do you need me to elaborate on anything?** (e.g., suggest specific meeting agendas, highlight potential questions to address during the initial briefing, add a specific weighting to the ‘Priority’ metric)
+  todoist-labels:: #outlook365
+  todoist-status:: ◼️
+- [[2026-02-03]] Sito MODES: primo draft
+  todoist-id:: [6fCrg62G5wXpxXqc](https://todoist.com/showTask?id=6fCrg62G5wXpxXqc)
+  todoist-project:: #📧EmailsToAnswer
+  todoist-due:: 2026-02-03
+  todoist-desc:: From: juri.dirocco@univaq.it Received: 2025-11-05T16:34:03Z ✉: [Web Link](https://outlook.office365.com/owa/?ItemID=AAMkADM1NGNiNjk0LTY0ZGUtNDgzOC04MDM5LWNhODNkYWNjNjU4YwBGAAAAAACT6qp78kRgRKuUMBdWEga%2FBwCOhWlC8F7PRKzlljZYZYQmAAAAAAEMAACOhWlC8F7PRKzlljZYZYQmAAhreqlnAAA%3D&exvsurl=1&viewmodel=ReadMessageItem) --- Ciao a tutti, a tempo perso ho cominciato a buttar giù il sito del laboratorio modes [MODES Lab](https://modes-laboratory.github.io/) E’ parametrizzato in base alle collezioni di dati, quindi possiamo lavorarci sui contenuti senza modificare il sito. Se Alf fa una
   todoist-status:: ◼️