logseq/pages/todoist___2026-01-28.md

• 2026-01-28 Contattare studenti restituzione portatili todoist-id:: 6f82x4WFg69Jmr99 todoist-project:: #🎓 Services-PHDICT todoist-due:: 2026-01-28 todoist-status:: ◼️
• 2026-01-28 R: Info PhD visiting period - GIACOMELLI todoist-id:: 6fhmvW5wJxpXpfc8 todoist-project:: #🎓 Services-PHDICT todoist-due:: 2026-01-28 todoist-desc:: From: stefano.giacomelli@graduate.univaq.it Received: 2026-01-08T09:49:43Z ✉: Web Link --- Okay, let's break down this request and create a detailed, actionable plan. This task involves presenting a proposal to the university regarding a short-term visiting researcher to explore a specific aspect of your research. Here's a breakdown of what needs to be done, with actionable steps and considerations: 1. Understanding the Core Request: The request is to formally request a visiting researcher to explore [Specify the topic here - crucial for tailoring the plan]. This is a high-level request that requires a detailed proposal to justify the investment and ensure it aligns with university guidelines and expectations. 2. Key Action Steps - A Breakdown: * Phase 1: Preliminary Research & Justification (1-2 weeks) * Define the Scope: Precisely define what aspects of the topic you’ll be exploring. Don't just say “explore a topic.” What specific questions or problems do you want to address? * Literature Review: Conduct a preliminary review of existing research related to the topic. This will help you understand current trends, challenges, and potential gaps in knowledge. * Identify Target Audience: Who is this visitor expected to interact with? (Researchers, students, administrators?). This will influence the presentation. * Budget Estimation: Develop a preliminary budget outline – think about travel, accommodation, research expenses, communication, and potential costs associated with the visitor’s work. * University Guidelines: Crucially, Review the university's policies regarding visiting researcher requests, including timelines, required documentation, and approval processes. Find out what they expect in terms of: * Purpose of the Visit: Is it exploratory, data gathering, mentorship, etc.? * Length of Stay: How long will the visitor be based on campus? * Data Management: Will the visitor need access to your datasets? * Intellectual Property: Clarify ownership of any work produced during the visit. * Phase 2: Proposal Development (2-4 weeks) * Draft a Proposal Outline: Create a structured proposal that includes: * Executive Summary: A concise overview of the project and its importance. * Introduction & Background: Contextualize the topic, explaining why it’s relevant to your research. * Research Objectives: Clearly state what you want to achieve. Make them SMART (Specific, Measurable, Achievable, Relevant, Time-bound). * Methodology: Describe how you’ll conduct the research – what data will you collect, which methods will you use (literature review, interviews, surveys, data analysis)? * Timeline & Milestones: A Gantt chart or table showing the planned phases and expected completion dates. * Resources Required: List required equipment, software, and access to datasets/databases. * Budget Breakdown: Detailed breakdown of anticipated costs. * Potential Benefits: Explain how the visit will contribute to your research or university’s goals. * Risk Assessment: Identify potential challenges and mitigation strategies. * Write the Full Proposal: Follow a professional writing style. Ensure clarity, accuracy, and thoroughness. * Phase 3: Formal Submission & Approval (1-2 weeks) * Submit to the Appropriate Department/Committee: Follow the university’s procedures for submitting proposal requests (e.g., research office, department head). * Submit to the University Review Board (if applicable): Some universities require this step. * Seek Feedback: If possible, ask colleagues for feedback on the proposal before submitting it. 3. Specific Considerations for your Topic: * Data Availability: Is there a readily available dataset that the visitor can use? * Accessibility: Can you provide access to relevant documents, software, or databases? * Researcher's Expertise: Does the visitor have expertise related to this topic that could benefit your research? 4. Recommended Next Steps – Actionable Tasks: 1. Schedule a Meeting with [Your Supervisor/Research Team Lead]: Discuss the project scope, budget, and timeline. 2. Research University Guidelines: Thoroughly review the university’s policy on visiting researcher requests. 3. Identify Key Stakeholders: Talk with those involved who will be affected by this visit (e.g., Data Science department, research lab). 4. Start initial literature review. To help me refine this further, could you tell me: * What is the specific topic you're proposing to explore? (e.g., "Sentiment analysis of social media data related to climate change," or "Exploring the impact of a specific intervention on student learning.") * What is the proposed duration of the visit? (e.g., 1 week, 2 weeks, 1 month) * Are there any specific data sources or resources that you'd like to emphasize? --- Buongiorno professore (e buon anno), Le scrivo come richiesto da lei, per ricordarle di inviare l'autorizzazione al settore dottorati, per il mio visiting (dal 1 Marzo al 31 Maggio 2026, al KU di Leuven). Ho già formalizzato tutte le pratiche con il KU todoist-labels:: #followup todoist-status:: ◼️
• 2026-01-28 Manuscript in your Reviewer Center - IEEE Software, SWSI-2026-01-0024 todoist-id:: 6fjh74qpCPV5HJ38 todoist-project:: #📜 REVIEWS todoist-due:: 2026-01-28 todoist-desc:: From: onbehalfof@manuscriptcentral.com Received: 2026-01-12T07:28:14Z ✉: Web Link --- Okay, here’s a synthesis of the email content, transforming it into actionable tasks for completing the task of reviewing the manuscript. I’ve focused on clarity and providing specific steps. Task Summary: Review the IEEE Software manuscript ("SWSI-2026-01-0024") for adherence to peer review guidelines, focusing on confidentiality and providing substantive feedback. Actionable Tasks & Breakdown: 1. Review Policies Understanding (Priority: High): * Action: Thoroughly read the reviewer policies document (link: [https://magazines.ieeeauthorcenter.ieee.org/submit-your-article-for-peer-review/about-the-peer-review-process]) to understand the specific requirements for content, format, and communication. Pay close attention to the emphasis on confidentiality regarding AI-generated feedback. * Deliverable: A concise summary of key policy points – particularly concerning what constitutes acceptable or unacceptable review comments. 2. Manuscript Review & Initial Assessment (Priority: High): * Action: Begin reviewing the manuscript – specifically focusing on the sections related to the agentic system engineering context. Identify key sections: * Abstract: Ensure it accurately summarizes the manuscript's purpose and scope. * Introduction: Evaluate the relevance of the context engineering concept to the manuscript’s topic. * Methodology: Assess the methods used – are they appropriate for the context? * Results & Discussion: Confirm the results are logically supported by the methods. * Conclusion: Assess the final conclusion – is it justified and well-supported? * Deliverable: A brief (1-2 paragraph) summary of initial impressions, highlighting potential areas of concern (e.g., a lack of specific details, unclear methodology). 3. Identify Key Concerns - Confidentiality & AI Feedback (Priority: Medium): * Action: Specifically look for the sections where the reviewer emphasizes caution regarding sharing information about the manuscript with AI platforms for text generation. * Deliverable: A list of 2-3 specific concerns regarding the manuscript's use of AI-generated content, which you will need to address in your review. 4. Content Review & Feedback (Priority: High): * Action: Address the following points based on your concerns: * Referencing: Ensure all citations are accurate and properly formatted. * Specificity: Ensure claims are supported by evidence. * Context: Clarify the agentic system engineering context. Does it adequately demonstrate its significance? * AI Integration: Carefully assess the role and influence of AI. Does it feel like a supplementary tool or integral to the core work? (The reviewer’s concern about shared information is key here.) * Deliverable: Draft review comments addressing each identified concern, focusing on providing specific, constructive feedback. (Focus on the why behind your comments – not just stating the problem.) 5. Review Score Sheet & Submission (Priority: Medium): * Action: Carefully and accurately fill out the review score sheet, ensuring all sections are completed (Confidential Comments, Public Comments, and any other required fields). * Deliverable: Completed review score sheet, with all required fields filled. 6. Communication Protocol (Priority: Medium): * Action: Respond promptly to any questions from the editor or reviewer. Be professional and courteous. * Deliverable: A record of your communication attempts – noting the date, content, and outcome of each communication. 7. Final Review & Submission (Priority: Low): Once you've completed all steps, submit the manuscript for review. Important Note: Document everything – your reasoning behind the feedback, specific examples, and any changes made during the review process. This will provide a clear audit trail for future review decisions. --- Let me know if you'd like me to elaborate on any of these tasks or provide more specific examples! --- IEEE Software, SWSI-2026-01-0024 manuscript type: SWSI: Agentic System Engineering (Sep/Oct 2026) "Context Engineering for Software Engineering Agents" 12-Jan-2026 Dear Prof. Di Ruscio: Thank you for agreeing to review the above reference manus todoist-status:: ◼️
• 2026-01-28 OpenCode | The open source AI coding agent todoist-id:: 6fpPgGfgM48RfhHg todoist-project:: #Inbox todoist-due:: 2026-01-28 todoist-status:: ◼️
• 2026-01-28 PAPERS/J-Collaborative-Development todoist-id:: 6fmMjW88FQ9m8x2g todoist-project:: #✏️ PAPERS todoist-due:: 2026-01-28 todoist-desc:: WebLink: Outlook todoist-labels:: #goal #logseqed todoist-status:: ◼️
• 2026-01-28 Pubblicazione Decreto di rettifica dell'Avviso per la presentazione di Progetti di Ateneo per la Ricerca di Base e Avvio alla Ricerca per l'anno 2026 todoist-id:: 6ffgFx5M2VMWVhQ8 todoist-project:: #🔭 Services-Commissione-Ricerca-DISIM todoist-due:: 2026-01-28 todoist-desc:: From: proget@strutture.univaq.it Received: 2025-12-22T14:22:50Z ✉: Web Link --- Okay, here's a synthesis of the email content, summarized and designed to be actionable, focusing on the key information and suggesting steps: Task Summary: The email is a formal announcement regarding the completion of a project proposal ("Avviso per la presentazione di Progetti..."). It's requesting confirmation of receipt and potentially a preliminary review. Detailed Breakdown & Actionable Steps: 1. Confirmation of Receipt: Immediately confirm you’ve received the email. If you haven’t, contact the sender (Luisa De Matteis) via email. 2. Understand the Content: The email highlights the crucial point that the project proposal ("Progetti di Ateneo") has been published and is awaiting review. The key elements are: * Official Publication: It was published at the Albo ufficiale di Ateneo. * Ricerca - Finanziamenti di Ateneo: It is related to funding and research initiatives within the Ateneo University. * Due Diligence Required: It's essential to review the proposal thoroughly. 3. Recommended Actions - Initial Review & Contact: * Review the Proposal: Carefully read the entire document. Understand the scope, goals, and deliverables. * Contact the Sender (Luisa De Matteis): Send a polite email requesting a brief overview of the proposal. Specifically state your intention to review it and any initial questions you have. Ask for a preliminary assessment of the document’s completeness and relevance to your team. 4. Specific Questions to Ask (Based on the Email's Context - these are crucial): * What is the stated purpose/goal of the project? * What specific areas require the most attention during the review? * Are there any attachments or supplementary materials that are needed? 5. Legal Compliance & Disclaimers: Before proceeding, review the email for the disclaimer concerning data privacy. Ensure your actions comply with all relevant legal requirements regarding the handling of sensitive project information. 6. Documentation: Keep a record of your communication with Luisa De Matteis and the email itself. --- To help me refine this further and tailor it to a specific scenario, could you tell me: * What is the role of the recipient? (e.g., Project Manager, Researcher, Legal Counsel?) * What is the project being reviewed? (A general idea is helpful.) --- Gentilissime e gentilissimi, vi inoltriamo il Decreto di rettifica dell'Avviso per la presentazione di Progetti di Ateneo per la Ricerca di Base e Avvio alla Ricerca per l'anno 2026. Il presente documento è stato pubblicato all'Albo ufficiale di Ateneo todoist-status:: ◼️
• 2026-01-28 Re: Rinnovo Assegni di Ricerca e Nuovi Incarichi di Ricerca su fondi di Ateneo 2026 todoist-id:: 6fphgQWXJxgq2Qp8 todoist-project:: #🏢 Admin todoist-due:: 2026-01-28 todoist-desc:: From: donatella.donatelli@univaq.it Received: 2026-01-20T20:59:52Z ✉: Web Link --- --- Caro Davide, per quanto riguarda la tempistica sui fondi RIA mi sono tenuta prudenzialmente un po’ larga nei tempi considerando che i bandi potrebbero essere tanti e non tutti i colleghi sono efficienti nell’inviare la documentazione alla segreteria. todoist-status:: ◼️
• 2026-01-28 Deliverable D3.2 todoist-id:: 6fVRXMVJWRWQ2fgG todoist-project:: #🚀 Projects-EU-MOSAICO todoist-due:: 2026-01-28 todoist-desc:: MOSAICO D3.2 - Online LaTeX Editor Overleaf todoist-labels:: #goal #logseqed todoist-status:: ◼️
• 2026-01-28 MOSAICO GA: Preparation of partners' mini-interviews todoist-id:: 6fmRFRjqR84GqhF8 todoist-project:: #🚀 Projects-EU-MOSAICO todoist-due:: 2026-01-28 todoist-desc:: WebLink: Outlook Email Content Summary: The partners will be together in Athens on January 29 to film short "mini-interviews" for the project’s communication. Videos will focus on three key questions showcasing the diversity of the consortium. Recording will take place on-site on January 28 and 29, with additional online recordings afterward via video call. The spokesperson for each organization needs to be identified. A GDPR consent form will be shared by the beginning of next week for signing. The questions cover Innovation, Collaboration, and Vision. Subtasks: 1. Schedule on-site video recordings on January 28 and 29. 2. Reach out to partners to identify spokespersons for the mini-interviews. 3. Prepare a calendar for the video recordings (to be shared next week). 4. Plan online video recording sessions after on-site recordings. 5. Share GDPR consent form for signing by the beginning of next week. 6. Remind partners to avoid technical jargon and start sentences by rephrasing the questions for easier editing. 7. Prepare for filming the mini-interviews during breaks at the Athens meeting. Due Date: January 29, 2024 todoist-labels:: #ai-generated #ai-generated-main-task todoist-status:: ◼️
• 2026-01-28 Dottorato di Ricerca - Nuove proposte e rinnovi - XLII ciclo - a.a.2026/2027. todoist-id:: 6fq4jcrv89PW5c78 todoist-project:: #🎓 Services-PHDICT todoist-due:: 2026-01-28 todoist-desc:: From: dot@strutture.univaq.it Received: 2026-01-22T09:36:00Z ✉: Web Link --- The email transmits a note with protocol number 10497 dated January 22, 2026, regarding a specific subject. Task: Forward note prot. n. 10497 of 22/01/2026. Recommended Actions: * Access the email content and locate the attached or referenced note. * Forward the note to the relevant individuals or departments. * Ensure proper documentation or logging of the forwarding action, if required. Deadline: January 22, 2026. --- Trasmettiamo la nota prot. n. 10497 del 22/01/2026 relativa all'oggetto.. Cordiali saluti Simonetta Ricciardi Università degli Studi dell'Aquila Settore Dottorati, Assegni e Borse di Ricerca Palazzo Camponeschi Piazza Santa Margherita, 2 Te todoist-status:: ◼️
• 2026-01-28 fra le università straniere va aggiunta la Aalborg University che ha ospitato Roberta di Fonzo e con cui abbiamo alcune pubblicazioni, anche su IEEE Transactions on Industrial Informatics e on Industry Applications il dottorando Noman Liaqat andrà pres... todoist-id:: 6fG9FrXwcrvMxhp8 todoist-project:: #🎓 Services-PHDICT todoist-due:: 2026-01-28 todoist-desc:: Web Link todoist-labels:: #outlook365 todoist-status:: ◼️
• 2026-01-28 SW-2025-10-0161.R1 - Maor Revision Received todoist-id:: 6fqHgMhJp4pq3pmg todoist-project:: #💺 EditoringChairing todoist-due:: 2026-01-28 todoist-desc:: From: onbehalfof@manuscriptcentral.com Received: 2026-01-23T14:10:29Z ✉: Web Link --- Task Description: Major revision for the manuscript "Explainer Pattern – A Design Pattern for the Integration of Explanations in Code" (SW-2025-10-0161.R1) has been submitted to IEEE Software. Reviewers have been invited, and you will be notified once all re-reviews are received. Recommended Actions: * Wait for Notification: Await notification from IEEE Software regarding the completion of the re-review process. * Review and Recommend: Once notified, access the revised manuscript and provide your recommendation. Deadline: * Implicit Deadline: The submission of re-reviews by reviewers will trigger a notification. While no explicit date is given for your action, the process is dependent on reviewer responses. --- SW-2025-10-0161.R1, "Explainer Pattern – A Design Pattern for the Integration of Explanations in Code" Manuscript Type: Regular IEEE Software 23-Jan-2026 Dear Prof. Davide Di Ruscio, The major revision for the above-referenced manuscript has be todoist-status:: ◼️
• 2026-01-28 Manuscript ID SOSYM-26-00005495 is now in your Editor Center todoist-id:: 6fqqJqV6XmqFHJVg todoist-project:: #💺 EditoringChairing todoist-due:: 2026-01-28 todoist-desc:: From: onbehalfof@manuscriptcentral.com Received: 2026-01-25T14:55:25Z ✉: Web Link --- ## Task Summary: Reviewer Assignment for Manuscript SOSYM-26-00005495 A manuscript titled "Integrating Pretrained Large Language Models and Graph Neural Networks For Model-Driven Engineering: A Graph Language Modeling Framework" (ID SOSYM-26-00005495) has been submitted to the journal Software and Systems Modeling. Professor Davide Di Ruscio is requested to assign reviewers for this manuscript. ## Actionable Task for Professor Davide Di Ruscio: Task Title: Assign Reviewers for Manuscript SOSYM-26-00005495 Description: Assign appropriate reviewers for the submitted manuscript SOSYM-26-00005495. Key Actions: 1. Login: Access the journal's editorial system at https://mc.manuscriptcentral.com/sosym using your credentials (User ID: davide.diruscio@univaq.it). 2. Navigate: Go to your "Editor Center". 3. Locate Manuscript: Click on "Awaiting Reviewer Selection" and then click "Take Action" for manuscript SOSYM-26-00005495. 4. Search & Select Reviewers: Utilize the quick or advanced search fields to find suitable reviewers. Select reviewers using the checkboxes and click "Add". 5. Create New Reviewers (Optional): If necessary, create new reviewer accounts, ensuring no duplicates. 6. Invite Reviewers: Press the "Invite" button in the "Reviewer List". 7. Edit & Send Invitation: Edit the invitation message as desired and then press "Save and Send". 8. Monitor Review Quality: Be vigilant about the quality of reviews provided, considering the potential misuse of Generative AI. 9. Consult Guidelines: Refer to the Editor guidelines at http://www.sosym.org/editor_guidelines/ for additional information. Deadline: As soon as possible. --- 25-Jan-2026 Dear Professor Davide Di Ruscio: Manuscript ID SOSYM-26-00005495 entitled "Integrating Pretrained Large Language Models and Graph Neural Networks For Model-Driven Engineering: A Graph Language Modeling Framework," with Professor Bork as todoist-status:: ◼️
• 2026-01-28 Buongiorno Prof. Dovrei aver concluso il progetto con lo sviluppo dei 4 punti che ci siamo detti sopra durante l'esame. Spiego di seguito: un container per ogni componente: Ogni componente logico (Monitor, Analyzer, Planner, Executor, Knowledge Base) è eseguito in un container Docker dedicato e isolato, garantendo modularità, ognuno con le sue dipendenze. estensibilità rispetto a sensori vs attuatori: ho superato la logica hardcoded come ci eravamo detti in riferimento alla slide 06_Slides-Control-Systems-v2.pdf implementando una gestione basata su Control Loops configurabili. Il sistema ora non conosce a priori le regole, ma istanzia dinamicamente i loop (es. Hydration Loop, Safety Loop) leggendoli dalla configurazione. Questo garantisce la totale estensibilità rispetto a nuovi sensori o nuove regole di adattamento senza ricompilare il codice. configurazione con un container dedicato: ho implementato un container dedicato (config-server) che agisce come Single Source of Truth, iniettando le policy di adattamento e la topologia a runtime. documentazione: È allegato il report PDF strutturato secondo il template fornito, completo di tassonomia dell'adattamento, logica formale e validazione visiva degli scenari tramite Dashboard Grafana.Ho inserito tutto nel repo https://github.com/ocraton/smart-olive-grove todoist-id:: 6fr34W536H4grP9g todoist-project:: #👨‍🏫 Teaching todoist-due:: 2026-01-28 todoist-status:: ◼️
• 2026-01-28 Read: Assessing and Advancing Benchmarks for Evaluating Large Language Models in Software Engineering Tasks (Xing Hu, Feifei Niu, Junkai Chen, Xin Zhou, Junwei Zhang, Junda He, Xin Xia, David Lo) [2026] todoist-id:: 6fmPJm48cHFRGx5g todoist-project:: #🚀 Projects-EU-MOSAICO todoist-due:: 2026-01-28 todoist-desc:: Zotero item: zotero://select/items/UCR492ZE todoist-labels:: #zotero todoist-status:: ◼️
• 2026-01-28 Fare aggiornamento calendario prossimi appelli SE4AS e SE4AIOT todoist-id:: 6fqFP6Vx6g6xPmx7 todoist-project:: #👨‍🏫 Teaching todoist-due:: 2026-01-28 todoist-status:: ◼️
• 2026-01-28 Hi Professor, I just wanted to let you know that we have updated everything based on your feedback for the IoT project. The following major changes are now implemented:- The threshold values used for Telegram notifications are now fully dynamic (loaded from the config).- The Grafana dashboards update automatically whenever a new sensor or threshold is added. - All sensor units are now loaded dynamically from the config file.- The main configuration file has been moved to its own config directory. todoist-id:: 6fqFgJPRQHf9hcGg todoist-project:: #👨‍🏫 Teaching todoist-due:: 2026-01-28 todoist-status:: ◼️
• 2026-01-28 I have compiled the expenses for the Amsterdam mission, finally . They are totaling to 2991. Please let me know if I can proceed with the Refund Request? Thanks todoist-id:: 6fXq8F8cC4Q6JFVg todoist-project:: #🎓 Services-PHDICT todoist-due:: 2026-01-28 todoist-labels:: #followup todoist-status:: ◼️
• 2026-01-28 [Dottorato PNRR] Relazione annuale di sintesi todoist-id:: 6fj3mhqW972xv5c8 todoist-project:: #🎓 Services-PHDICT todoist-due:: 2026-01-28 todoist-desc:: From: alessandra.galassi@graduate.univaq.it Received: 2026-01-09T11:04:30Z ✉: Web Link --- Okay, here’s a synthesized summary of the email, broken down into actionable tasks, based on the content: Task Summary: The email is a formal message from a "Chiar.mo Coordinatore del corso dottorale in ICT prof. Di Ruscio" (Coordination Officer for the PhD in ICT Professor Di Ruscio) to the recipient. The recipient is being sent a completed and signed form outlining a course. Actionable Tasks: 1. Review and Confirm Completeness: Carefully read the completed and signed form to ensure all required information is accurately present. 2. Attach the Form: Attach the completed form to this email. 3. Send the Form: Send the attached form to the recipient. 4. Express Good Wishes: Compose a polite and cordial message to the recipient, wishing them a happy New Year. 5. Verify Sender Information: Ensure the email is sent from a valid and trusted source. Let me know if you'd like me to elaborate on any of these points or add more detail! --- Chiar.mo Coordinatore del corso dottorale in ICT prof. Di Ruscio, come da guida utente, in allegato, invio compilata e firmata quanto specificato in oggetto. Grazie. L’occasione è gradita per porgere i migliori auguri di buon anno! Un saluto cordiale, todoist-status:: ◼️
• 2026-01-28 Richiesta variazione strutture estere mobilità e richiesta autorizzazioni - Giacomelli Stefano todoist-id:: 6fm4v9FRJ485fgv8 todoist-project:: #🎓 Services-PHDICT todoist-due:: 2026-01-28 todoist-desc:: From: stefano.giacomelli@graduate.univaq.it Received: 2026-01-13T21:06:18Z ✉: Web Link --- Task Description: Stefano Giacomelli, a PhD student in ICT, is requesting a change in his mandatory 6-month PNRR mobility program's host institution. He has secured a new host institution in Belgium (KU Leuven) and has obtained an official invitation letter. He is also providing supporting documents, including a letter detailing the reasons for the change, information on the new host institution, and his visiting proposal. Additionally, he is attaching authorization requests for the PhD program coordinator and will soon provide "commitment letters" from the new host institution. Recommended Actions: 1. Review and Process Host Institution Change Request: Evaluate the provided documentation for the change of host institution for Stefano Giacomelli's PNRR mobility. 2. Verify Supporting Documents: Ensure all attached documents (letter of motivation, host institution details, visiting proposal, invitation letters) are complete and accurate. 3. Obtain Commitment Letters: Follow up with Stefano Giacomelli to ensure timely submission of the "commitment letters" from the new host institution. 4. Approve Coordination Request: Review and approve the authorization requests for the PhD program coordinator. 5. Facilitate Ministry Notification: Transmit the approved request, including all necessary details of the new host institution, to the Ministry (MUR) via the CINECA platform as per the instructions. 6. Confirm U-Web Mission Request: Advise Stefano Giacomelli on the process for opening a mission request on the U-Web portal for his visiting period. 7. Provide Additional Guidance: Address any further questions Stefano Giacomelli may have regarding the administrative and bureaucratic procedures for his mobility. Deadline: * The email mentions that any variation to the initial project must be authorized by the Ministry and that this step is "very important and requires urgent action." While no specific date is given, this implies a need for prompt processing. --- Buonasera, Sono Stefano Giacomelli, dottorando DISIM ICT del XXXIX ciclo. A seguito delle informazioni ricevute mediante "Ticket - Help Point" dalla Dr.ssa Valeria Gentile, e in accordo con il mio Tutor (Prof. Fabio Graziosi) e il mio Supervisor (Prof. todoist-labels:: #followup todoist-status:: ◼️
• 2026-01-28 Proposta per Univaq On Air - Dottorandi di Ricerca todoist-id:: 6fmfWgpGcX7V285g todoist-project:: #🎓 Services-PHDICT todoist-due:: 2026-01-28 todoist-desc:: Weblink: Outlook Email Content Summary: Proposal for the Univaq podcast to feature a series of interventions by research PhD students across various scientific areas and schools. The initiative aligns with the goal to narrate the life of an important and dynamic academic community. Seeking opinion and coordination for necessary steps from the coordinator of the podcast. No specific deadlines mentioned. todoist-labels:: #ai-generated #ai-generated-main-task todoist-status:: ◼️
• 2026-01-28 Finalizzare Verbale ultimo Collegio todoist-id:: 6fr6MGrcrjRmjwP9 todoist-project:: #🎓 Services-PHDICT todoist-due:: 2026-01-28 todoist-status:: ◼️
• 2026-01-28 Fwd: Decision on your submission - JSSOFTWARE-D-25-01604 todoist-id:: 6fpXr6XWhhcQWfrc todoist-project:: #📧EmailsToAnswer todoist-due:: 2026-01-28 todoist-desc:: From: disorbo@unisannio.it Received: 2026-01-20T09:03:13Z ✉: Web Link --- 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-01-28 Podcast dottorato todoist-id:: 6fr3FqrHRj6PCjpc todoist-project:: #📧EmailsToAnswer todoist-due:: 2026-01-28 todoist-desc:: From: raffaele.dambrosio@univaq.it Received: 2026-01-26T11:24:01Z ✉: Web Link --- Task: Suggest guests for the PhD podcast. Description: Raffaele is organizing a podcast series about PhD programs and is looking for guests. He has received suggestions from other program coordinators, but he specifically needs recommendations for guests for the PhD in Computer Science. The aim is to showcase diverse stories, including PhD holders working in academia, outside academia, current PhD students, and colleagues. Actions to take: 1. Identify potential guests for the PhD in Computer Science podcast, ensuring a variety of backgrounds and experiences. 2. Compile a list of these individuals and their relevant affiliations/roles. 3. Submit the suggestions to Raffaele. Deadline: None mentioned in the email. --- Caro Davide spero che ogni cosa proceda al meglio per te. Ti scrivo in merito al podcast sul dottorato. Come hai potuto evincere dal carteggio con tutti i coordinatori di programmi di dottorato ad UnivAQ, sono state segnalate alcune persone (dottora todoist-status:: ◼️
• 2026-01-28 INFORMAZIONI ESAME todoist-id:: 6frJFWv6c37QjWcc todoist-project:: #📧EmailsToAnswer todoist-due:: 2026-01-28 todoist-desc:: From: asia.picuti@student.univaq.it Received: 2026-01-27T20:44:57Z ✉: Web Link --- Here's a summary of the email and the actionable task: Task Summary: Asia Picuti, a student in the Education and Social Services program, needs to take the exam for "Multimediality for Educational Sciences" due to a change in her academic track. She is requesting information on the study materials and exam format. Actionable Task: * Task: Provide study materials and exam details for "Multimediality for Educational Sciences." * Details: Respond to Asia Picuti's email with the required information for the "Multimediality for Educational Sciences" exam. * Assignee: (Likely the recipient of the email, the professor or administrator) * Deadline: None specified in the email. --- Buonasera , Sono Asia Picuti e frequento il corso di Scienze della formazione e del servizio sociale. Dovendo cambiare ordinamento, devo sostenere l'esame di " multimedialitá per le scienze dell' educazione". Mi potrebbe dire cortesemente il materiale d todoist-status:: ◼️
• 2026-01-28 Certificazione corsi di dottorato non presenti su ESSE3 todoist-id:: 6frGFmx63Q8xJ478 todoist-project:: #Inbox todoist-due:: 2026-01-28 todoist-desc:: From: leonardo.fazzini1@graduate.univaq.it Received: 2026-01-27T15:58:11Z ✉: Web Link --- Here's a summary of the email and an actionable task description: Task Title: Ensure PhD Course Registrations are Completed on ESSE3 Task Description: Leonardo Fazzini, a second-year ICT PhD student, is requesting assistance with the registration of two PhD courses on the ESSE3 platform. He completed both courses during his first year: * Research Methodology (internal, taught by Prof. Thanh Phuong Nguyen) * Neural Networks and Deep Learning (external, taught by Prof. Giorgio Buttazzo at Scuola Superiore Sant'Anna) Leonardo submitted all required documentation for both courses during the transition from his first to his second year, but neither course is currently registered on ESSE3. Recommended Actions: * Investigate the status of the course registrations on the ESSE3 platform. * Contact the relevant administrative office or individuals responsible for ESSE3 course registration to understand the delay. * Follow up with the professors or departments involved if further information or documentation is required. * Ensure both "Research Methodology" and "Neural Networks and Deep Learning" courses are officially registered for Leonardo Fazzini on ESSE3. * Confirm with Leonardo Fazzini once the registrations are successfully completed. --- Gentili Professori Di Ruscio e Di Mascio, sono Leonardo Fazzini, dottorando in ICT al secondo anno, con supervisor Giacomo Valente e Luigi Pomante (in cc). Vi scrivo per segnalarvi una questione relativa alla registrazione dei corsi di dottorato. Nel co todoist-status:: ◼️
• 2026-01-28 6 days late? IEEE Software, SW-2025-10-0161.R1 todoist-id:: 6frPc34wCFgXX4Rg todoist-project:: #Inbox todoist-due:: 2026-01-28 todoist-desc:: From: onbehalfof@manuscriptcentral.com Received: 2026-01-28T05:48:37Z ✉: Web Link --- Here's a synthesized task description and actionable recommendations based on the email: Task Description: Finalize and send out the re-review for the paper "Explainer Pattern – A Design Pattern for the Integration of Explanations in Code" (IEEE Software, SW-2025-10-0161.R1) to expedite its publication. Actionable Recommendations: * Review and Finalize Paper: Prof. Di Ruscio, please review the paper "Explainer Pattern – A Design Pattern for the Integration of Explanations in Code" and make any necessary final adjustments. * Send Re-review: Once finalized, please send out the re-review of the paper. Deadline: * The email implies urgency, noting that three weeks have passed and a "week late is not a big deal, but it can quickly add up." While no explicit date is given, the context suggests the re-review should be completed as soon as possible. Recommendation: Aim to complete and send the re-review within the next 2-3 days to align with the implied urgency. --- 28-Jan-2026 IEEE Software, SW-2025-10-0161.R1 "Explainer Pattern – A Design Pattern for the Integration of Explanations in Code" Dear Prof. Di Ruscio: Maybe a week late is not a big deal, but you really have had 3 weeks to finalize this, and it todoist-status:: ◼️
• 2026-01-28 Await final scheduling of the thesis defense once thesis reviews are received #ai-generated todoist-id:: 9927961042 todoist-project:: #Inbox todoist-completed:: 2026-01-28 todoist-status:: ✅
• 2026-01-28 CM3 WP3 Presentation todoist-id:: 9912719915 todoist-project:: #Inbox todoist-completed:: 2026-01-28 todoist-status:: ✅