[logseq-plugin-git:commit] 2026-02-01T14:09:35.322Z
This commit is contained in:
@@ -1,89 +1,84 @@
|
||||
-
|
||||
- [[2026-02-01]] [🔁 Controllorrare Followup mails](https://mail.google.com/mail/u/0/#label/_GTD%2FFollowup)
|
||||
todoist-id:: [662FP6vPFXgCmWWV](https://todoist.com/showTask?id=662FP6vPFXgCmWWV)
|
||||
todoist-project:: #👷 WORK
|
||||
todoist-due:: 2026-02-01
|
||||
todoist-labels:: #routine
|
||||
todoist-status:: ◼️
|
||||
- [[2026-02-01]] [🔁Controllare Starred emails](https://mail.google.com/mail/u/0/#starred)
|
||||
todoist-id:: [662Fp5FGCprMXP7V](https://todoist.com/showTask?id=662Fp5FGCprMXP7V)
|
||||
todoist-project:: #👷 WORK
|
||||
todoist-due:: 2026-02-01
|
||||
todoist-labels:: #routine
|
||||
todoist-status:: ◼️
|
||||
- [[2026-02-01]] [mosaico-all] [MOSAICO] Exploitation Workshop: Consolidated Inputs & Next Steps
|
||||
todoist-id:: [6frh6HQhh7MGjwvg](https://todoist.com/showTask?id=6frh6HQhh7MGjwvg)
|
||||
todoist-project:: #🚀 Projects-EU-MOSAICO
|
||||
todoist-due:: 2026-02-01
|
||||
todoist-desc:: From: mosaico-all@imt-atlantique.fr Received: 2026-01-29T09:18:13Z ✉: [Web Link](https://outlook.office365.com/owa/?ItemID=AAMkADM1NGNiNjk0LTY0ZGUtNDgzOC04MDM5LWNhODNkYWNjNjU4YwBGAAAAAACT6qp78kRgRKuUMBdWEga%2FBwCOhWlC8F7PRKzlljZYZYQmAAAAAAEMAACOhWlC8F7PRKzlljZYZYQmAAii1IdlAAA%3D&exvsurl=1&viewmodel=ReadMessageItem) --- Okay, here's a breakdown of the email content, summarizing it and suggesting actionable tasks based on the provided text, formatted for a Todoist task creation: **Summary of Email Content:** The email is a follow-up message from Anastasia Marangou to the participating partners in the MOSAICO CM3 exploitation workshop. It outlines the workshop's focus, the Miro integration, and requests collaboration and contribution. Key points include: * **Workshop Overview:** A 3-day workshop focused on exploiting the "MOSAICO KERs Exploitation Inputs" file on SharePoint. * **Miro Integration:** The workshop will utilize Miro for a live, collaborative exploration of the exploitation results. * **Contribution Request:** Partners are encouraged to create a Miro account, participate in the Miro team, and offer their input on the workshop. * **Actionable Items:** Encourage the creation of a Miro account and offer to schedule a quick meeting. **Actionable Tasks for Todoist:** 1. **Create a Task:** "MOSAICO Exploitation Workshop - Miro Account & Contribution" 2. **Task Type:** "Collaboration" - This represents the interaction with Miro and the shared exploration. 3. **Due Date:** "Immediately" - To facilitate the Miro account creation. 4. **Priority:** Medium - Given the workshop's purpose, this is a suitable priority. 5. **Status:** To Do - The email has already created this. 6. **Description:** "Lead the MOSAICO workshop to be useful. Invite partners, provide Miro tutorial, facilitate Miro session." 7. **Assignee:** "Anastasia Marangou" – Since this is a direct communication. 8. **Tags:** “Exploitation”, “Miro”, “Workshop” **Additional Notes & Considerations (Based on the Email):** * **Miro Account:** The email emphasizes the need to create a Miro account. * **Collaboration Focus:** The mention of Miro and a live workshop indicates a collaborative approach. Let me know if you’d like me to elaborate on any of these tasks or add more detail! --- Dear all, Following yesterday’s Exploitation Workshop (Day 1 of MOSAICO CM3), we have consolidated all the inputs you shared into the “MOSAICO KERs Exploitation Inputs” file on our SharePoint. The file follows the same structure as the Miro board.
|
||||
todoist-status:: ◼️
|
||||
- [[2026-02-01]] [mosaico-all] MOSAICO CM3
|
||||
todoist-id:: [6f67vMc5RgHcgVR8](https://todoist.com/showTask?id=6f67vMc5RgHcgVR8)
|
||||
todoist-project:: #✈ Missioni
|
||||
todoist-due:: 2026-02-01
|
||||
todoist-desc:: From: zhanna.zhussupova@imt-atlantique.fr Received: 2025-10-16T14:25:53Z ✉: [Web Link](https://outlook.office365.com/owa/?ItemID=AAMkADM1NGNiNjk0LTY0ZGUtNDgzOC04MDM5LWNhODNkYWNjNjU4YwBGAAAAAACT6qp78kRgRKuUMBdWEga%2FBwCOhWlC8F7PRKzlljZYZYQmAAAAAAEMAACOhWlC8F7PRKzlljZYZYQmAAhdt23FAAA%3D&exvsurl=1&viewmodel=ReadMessageItem) --- Dear all, We are pleased to confirm that the MOSAICO CM3 will be kindly hosted by Netcompany-Intrasoft at its Athens headquarters, located at 13 Fragkokklisias Street, Maroussi, Greece. Please find attached the directions to the venue and the list of
|
||||
todoist-status:: ◼️
|
||||
- [[2026-02-01]] Re: Request for 50% increase in scholarship amount
|
||||
todoist-id:: [6frm2fGJpMRx9cRg](https://todoist.com/showTask?id=6frm2fGJpMRx9cRg)
|
||||
todoist-project:: #Inbox
|
||||
todoist-project:: #🎓 Services-PHDICT
|
||||
todoist-due:: 2026-02-01
|
||||
todoist-desc:: [Web Link](https://outlook.office365.com/owa/?ItemID=AAkALgAAAAAAHYQDEapmEc2byACqAC%2FEWg0AjoVpQvBez0Ss5ZY2WGWEJgAIotZmYQAA&exvsurl=1&viewmodel=ReadMessageItem) Given the email subject line "Re: Request for 50% increase in scholarship amount," the task is to address this request. Since it's a "Re:" email, it implies a previous communication where the request was made. Here's the description of the task for Outlook: --- **Task Title:** Review and Respond to Request for 50% Scholarship Increase **Priority:** High **Due Date:** [Suggest 5-7 business days from today's date] **Task Details:** This task originates from an email with the subject "Re: Request for 50% increase in scholarship amount." It requires you to address a student's or applicant's formal request to increase their existing scholarship funding by 50%. The goal is to evaluate the request, make an informed decision based on policy and available funds, and communicate the outcome clearly and professionally. **Actionable Steps to Accomplish this Task:** 1. **Locate Original Request & Gather Information:** * Find the original email or application that initiated the request for the 50% increase. * Identify the student/applicant's name, ID, current scholarship details (amount, duration, terms), and the specific reasons/justification provided for the requested increase. 2. **Review Scholarship Policies & Criteria:** * Consult the relevant scholarship guidelines, institutional policies, and financial aid regulations concerning scholarship increases or modifications. * Determine if there are specific criteria (e.g., academic performance, financial need changes, extraordinary circumstances) that must be met for an increase to be considered. 3. **Assess Justification & Financial Impact:** * Evaluate the provided justification against the established criteria. * Determine the financial implications of a 50% increase on the scholarship budget. * Verify the current budget availability for scholarship adjustments. 4. **Consult with Relevant Stakeholders (if necessary):** * If the decision requires approval or input from a scholarship committee, financial aid office, or specific department head, initiate that consultation. * Present the case, including the student's justification and your findings. 5. **Formulate Decision & Rationale:** * Based on your review, policy, budget, and consultations, decide whether to: * Approve the 50% increase. * Approve a partial increase (e.g., less than 50%). * Deny the request. * Clearly document the rationale for the decision. 6. **Draft and Send Response:** * Prepare a formal response to the student/applicant. * Clearly state the decision. * If approved, outline the new scholarship amount, effective date, and any adjusted terms. * If denied or partially approved, provide a concise and empathetic explanation for the decision, referencing policies or criteria as appropriate, and suggest alternative resources if available. * Ensure the tone is professional and supportive. 7. **Update Records:** * If the scholarship amount is adjusted, ensure all internal records, financial aid systems, and student profiles are updated accordingly. * File all relevant communication and documentation. ---
|
||||
todoist-labels:: #outlook365
|
||||
todoist-status:: ◼️
|
||||
- [[2026-02-01]] [| Jordi Cabot](https://www.linkedin.com/feed/update/urn:li:activity:7422002182599675904/?utm_source=share&utm_medium=member_desktop&rcm=ACoAAACaoXoBMvdj060syLix4vC3rwOgjAE9MpU)
|
||||
todoist-id:: [6frV24FXCHJrJjJ8](https://todoist.com/showTask?id=6frV24FXCHJrJjJ8)
|
||||
todoist-project:: #Inbox
|
||||
todoist-due:: 2026-02-01
|
||||
todoist-status:: ◼️
|
||||
- [[2026-02-01]] Fonte: Kaggle - [search.app](https://search.app/?link=https://www.kaggle.com/learn-guide/5-day-agents&utm_source=dsdf,sharefoc,,sh/x/discover/m1/4&utm_campaign=dsdf,sharefoc,,sh/x/discover/m1/4)
|
||||
todoist-id:: [6fH4gRgHwQF8Mm5g](https://todoist.com/showTask?id=6fH4gRgHwQF8Mm5g)
|
||||
todoist-project:: #🔥 CV Empower
|
||||
todoist-due:: 2026-02-01
|
||||
todoist-status:: ◼️
|
||||
- [[2026-02-01]] Registrazione contratto Corsigani
|
||||
todoist-id:: [6fjWHCmHqGFFvMvF](https://todoist.com/showTask?id=6fjWHCmHqGFFvMvF)
|
||||
todoist-project:: #📗 Personal
|
||||
todoist-due:: 2026-02-01
|
||||
todoist-status:: ◼️
|
||||
- [[2026-02-01]] Aggiornare sito con gli ultimi due corsi aggiuntivi
|
||||
todoist-id:: [6frwc82JfjrWXH2h](https://todoist.com/showTask?id=6frwc82JfjrWXH2h)
|
||||
todoist-project:: #🎓 Services-PHDICT
|
||||
todoist-due:: 2026-02-01
|
||||
todoist-status:: ◼️
|
||||
- [[2026-02-01]] I: PRIN 2022 e PRIN 2022 PNRR - FAQ VIII elenco
|
||||
todoist-id:: [6fpqJRPHvj4MCXQg](https://todoist.com/showTask?id=6fpqJRPHvj4MCXQg)
|
||||
todoist-project:: #🚀 Projects-PRIN2022-FRINGE
|
||||
todoist-due:: 2026-02-01
|
||||
todoist-desc:: From: disim.sac@strutture.univaq.it Received: 2026-01-21T09:40:01Z ✉: [Web Link](https://outlook.office365.com/owa/?ItemID=AAMkADM1NGNiNjk0LTY0ZGUtNDgzOC04MDM5LWNhODNkYWNjNjU4YwBGAAAAAACT6qp78kRgRKuUMBdWEga%2FBwCOhWlC8F7PRKzlljZYZYQmAAAAAAEMAACOhWlC8F7PRKzlljZYZYQmAAieJ1KxAAA%3D&exvsurl=1&viewmodel=ReadMessageItem) --- This email is a notification regarding the final reporting for PRIN 2022 and PRIN 2022 PNRR projects. **Key information:** * Expenses for "Acquisti e/o personale a costo reale" (Purchases and/or real-cost personnel) paid in **February 2025** will **not be eligible** for the final report. * The email also forwards the latest FAQs from the Ministry for final reporting. **Task Recommendation:** **Task:** Review PRIN 2022 and PRIN 2022 PNRR project expenses and ensure compliance with reporting guidelines. **Actions:** 1. **Review expenditure records:** Carefully examine all project expenses, particularly those related to "Acquisti e/o personale a costo reale." 2. **Identify ineligible expenses:** Flag any expenses paid in February 2025 for purchases or real-cost personnel. 3. **Consult FAQs:** Read the provided Ministry FAQs for PRIN 2022 and PRIN 2022 PNRR to ensure a thorough understanding of all reporting requirements. 4. **Adjust financial reporting:** Make necessary adjustments to the financial reports to exclude any ineligible expenses identified. 5. **Communicate with project teams:** Inform relevant project teams about the exclusion criteria and ensure they are aware of the reporting deadlines and requirements. **Deadline:** N/A (No explicit deadline mentioned for this specific action, but it's crucial for the overall project reporting which will have deadlines). --- Buongiorno, vi invio per opportuna conoscenza l'ultima nota dell'ufficio PRIN per quanto riguarda la chiusura delle rendicontazione dei progetti PRIN 2022 e PRIN 2022 PNRR. Nello specifico vi segnalo che non saranno ammissibili alla rendicontazione fi
|
||||
todoist-status:: ◼️
|
||||
- [[2026-02-01]] [grin-list] questionario sulla nuova ASN
|
||||
todoist-id:: [6cR9PX3pvWxwQPQg](https://todoist.com/showTask?id=6cR9PX3pvWxwQPQg)
|
||||
todoist-project:: #👷 WORK
|
||||
todoist-due:: 2026-02-01
|
||||
todoist-desc:: From: fabio.gadducci@unipi.it Received: 2025-07-23T09:00:54Z ✉: [Web Link](https://outlook.office365.com/owa/?ItemID=AQMkADM1NGNiNjk0LTY0ZGUtNDgzOC04MDM5LWNhODNkYWNjADY1OGMARgAAA5PqqnvyRGBEq5QwF1YSBr8HAI6FaULwXs9ErOWWNlhlhCYAAAIBDAAAAI6FaULwXs9ErOWWNlhlhCYACCTvfwAAAQ%3D%3D&exvsurl=1&viewmodel=ReadMessageItem) --- Cari tutti e care tutte, come sapete, e’ al momento in discussione al Parlamento un disegno di legge che riscrive le regole dell’ASN. Nella versione attuale viene abolita la commissione, e i candidati semplicemente auto-certificheranno i propri tito
|
||||
todoist-status:: ◼️
|
||||
- [[2026-02-01]] Re: Seduta Senato Accademico - 25 novembre 2025
|
||||
todoist-id:: [6fWQGqhWfCMRvqV8](https://todoist.com/showTask?id=6fWQGqhWfCMRvqV8)
|
||||
todoist-project:: #👷 WORK
|
||||
todoist-due:: 2026-02-01
|
||||
todoist-desc:: [Web Link](https://outlook.office365.com/owa/?ItemID=AAkALgAAAAAAHYQDEapmEc2byACqAC%2FEWg0AjoVpQvBez0Ss5ZY2WGWEJgAIhQcoFgAA&exvsurl=1&viewmodel=ReadMessageItem) Okay, here's a task description created based on the provided email content, designed for actionable completion: **Task Title:** Schedule and Prepare for 25 November 2025 Senate Sedat Education Confer ence **Task Description:** This email requests the scheduling and preliminary preparation for a Senate Education Conference scheduled for November 25th, 2025. As the lead organizer, your primary responsibility is to secure the space, confirm logistics, and ensure a productive experience for participating senators. **Suggested Action Items & Deliverables:** * **Confirm Attendance & Confirm Seats:** Verify with the Senator involved and confirm the number of attendees for the conference. Confirm that seats are pre-allocated for the necessary number of senators. * **Venue Space:** Contact the university/location providing the venue space and ascertain the room capacity, accessibility features, and available resources needed. Determine the best date and time for the conference, considering student schedules. * **Abstract/Presentation Material Review:** Quickly review the submitted abstract(s) or presentation materials to ensure they are presented professionally and are prepared in a standard format. This is crucial for a smooth and professional experience. * **Virtual/Hybrid Logistics:** Determine if the conference will be held virtually or in-person. If virtual, initiate preparation for platform setting (Zoom/Teams/Similar), ensuring a strong Wi-Fi and technical support option. For in-person, create a detailed logistics schedule - guest list, registration, parking information. * **Budget Considerations (Initial Stage):** Begin preliminary estimation for potential costs related to venue rental/facilities, catering (lunch/dinner), equipment (projectors/whiteboards), digital platform fees (if applicable). A rough budget should be created ASAP. **Next Steps:** Please provide a status update by Friday. Let me know if you need any further information/support. --- **To help me refine this further (if needed), could you tell me:** * What is the overall goal of this conference? Is it about showcasing new research, policy discussions, or something else? * Do you have any existing meeting schedules or logistical concerns within the email context?
|
||||
todoist-labels:: #outlook365
|
||||
todoist-status:: ◼️
|
||||
- [[2026-02-01]] Fw: [WG SSQ] - Riunione dei Nodi 22 Dicembre 2026 h 15 - Wshop QuCS
|
||||
todoist-id:: [6ffmwgH5mR3XFXM8](https://todoist.com/showTask?id=6ffmwgH5mR3XFXM8)
|
||||
todoist-project:: #👷 WORK
|
||||
todoist-due:: 2026-02-01
|
||||
todoist-desc:: From: salvatore.distefano@unime.it Received: 2025-12-30T16:33:44Z ✉: [Web Link](https://outlook.office365.com/owa/?ItemID=AAMkADM1NGNiNjk0LTY0ZGUtNDgzOC04MDM5LWNhODNkYWNjNjU4YwBGAAAAAACT6qp78kRgRKuUMBdWEga%2FBwCOhWlC8F7PRKzlljZYZYQmAAAAAAEMAACOhWlC8F7PRKzlljZYZYQmAAiQFox%2FAAA%3D&exvsurl=1&viewmodel=ReadMessageItem) --- Okay, let's break down this document and create a detailed action plan to complete the task. The document is a web page displaying a meeting invitation for a Google Group called "Quantitative Methods in Informatics." Here's a breakdown of what it’s saying and what needs to be done to follow through: **1. Understanding the Purpose & Context** * **Meeting Invitation:** The document is a notification about a meeting scheduled within Google Groups dedicated to quantitative methods. * **Key Attendees:** The group is likely comprised of researchers, analysts, and others interested in this topic. * **Action Required:** The user needs to respond to the meeting invitation and confirm their attendance. **2. Action Plan - Step-by-Step** Here’s a breakdown of what to do, prioritized by urgency: **Phase 1: Immediate Response (Within 24 Hours)** 1. **Read the Invitation Carefully:** Thoroughly understand the meeting details: * **Date & Time:** Confirm the exact time. * **Location:** Where is the meeting held? (Zoom link, Google Meet URL, etc.) * **Agenda:** What topics will be discussed? (This helps prepare.) * **Required Materials/Preparation:** Are there any documents to review beforehand? 2. **Respond to the Meeting Invitation:** * **Confirm Attendance:** Reply immediately: “Yes, I’m coming!” or “I’ll be there.” * **Briefly Confirm:** A short, polite acknowledgement is sufficient (e.g., "Great, looking forward to it!") 3. **Check Your Calendar:** Ensure your schedule doesn’t conflict with the meeting. **Phase 2: Preparation & Engagement (1-2 Days Before)** 4. **Review Materials (If Applicable):** If the agenda includes documents, pre-read them. 5. **Prepare Questions/Contributions:** Think about what you want to discuss. Jot down some initial thoughts or questions. This demonstrates engagement. 6. **Join the Discussion (Optional):** Consider participating in the discussion if you have relevant expertise or insights. **Phase 3: Confirmation & Attendance (Day of Meeting)** 7. **Confirm Attendance (via Group Chat):** If it’s a Google Meet, reply to the chat and confirm your participation. (e.g., “I'm in!”) 8. **Review the Agenda:** Quickly glance at the agenda again to make sure you're prepared. 9. **Prepare for the Meeting:** If you're contributing, think about what you'll share. 10. **Join the Meeting:** Log in to the meeting link. **Phase 4: Post-Meeting (Immediately After)** 11. **Note Key Takeaways:** Shortly after the meeting, jot down any key takeaways, decisions made, or action items assigned. 12. **Follow Up (If Needed):** If you have specific questions or feedback, reach out to the organizers or attendees. **3. Tools & Resources (Useful for the Action Plan)** * **Google Calendar:** For scheduling and calendar visibility. * **Google Groups:** To find relevant meetings and communication within the group. * **Zoom/Google Meet/Other Meeting Platform:** For the actual meeting. **4. Important Considerations** * **Respect Group Rules:** Follow any guidelines or etiquette established within the Google Group. * **Be Professional:** Maintain a polite and respectful tone in your communication. --- **To help me refine this further, could you tell me:** * What specifically are you hoping to do *after* responding to the invitation? (e.g., do you need to provide specific details, share a thought, or take a particular action?) --- Cari, mando a un ristretto gruppo di amici un reminder per il Wshop QuCS su quantitative CyberSec per ItaSec. Tutti noi siamo stati coinvolti, direttamente o indirettamente in SERICS, e potrebbe essere una buona venue per interagire con la comunità di c
|
||||
todoist-status:: ◼️
|
||||
- [[2026-02-01]] Fare rinnovo contratto via Zara
|
||||
todoist-id:: [6fhrmQrx8rwwwWFm](https://todoist.com/showTask?id=6fhrmQrx8rwwwWFm)
|
||||
todoist-project:: #📗 Personal
|
||||
todoist-due:: 2026-02-01
|
||||
todoist-status:: ◼️
|
||||
- [[2026-02-01]] Proposta per Univaq On Air - Dottorandi di Ricerca
|
||||
todoist-id:: [6fmfWgpGcX7V285g](https://todoist.com/showTask?id=6fmfWgpGcX7V285g)
|
||||
todoist-project:: #🎓 Services-PHDICT
|
||||
todoist-due:: 2026-02-01
|
||||
todoist-desc:: Weblink: [Outlook](https://outlook.office365.com/owa/?ItemID=AAMkADM1NGNiNjk0LTY0ZGUtNDgzOC04MDM5LWNhODNkYWNjNjU4YwBGAAAAAACT6qp78kRgRKuUMBdWEga%2FBwCOhWlC8F7PRKzlljZYZYQmAAAAAAEMAACOhWlC8F7PRKzlljZYZYQmAAiamtsPAAA%3D&exvsurl=1&viewmodel=ReadMessageItem) 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:: ◼️
|
||||
todoist-status:: ◼️
|
||||
- [[2026-02-01]] Rivedere Composizione Collegio
|
||||
todoist-id:: [6X4Jp7W4VW84FHqh](https://todoist.com/showTask?id=6X4Jp7W4VW84FHqh)
|
||||
todoist-project:: #🎓 Services-PHDICT
|
||||
todoist-due:: 2026-02-01
|
||||
todoist-labels:: #goal
|
||||
todoist-status:: ◼️
|
||||
- [[2026-02-01]] [[TOOL DEMO TRACK - MODELS 2026 Organizing Committee]]
|
||||
todoist-id:: [6fQ7HCGxPvcHGHgg](https://todoist.com/showTask?id=6fQ7HCGxPvcHGHgg)
|
||||
todoist-project:: #💺 EditoringChairing
|
||||
todoist-due:: 2026-02-01
|
||||
todoist-desc:: From: lolaburgueno@uma.es
|
||||
todoist-labels:: #goal #logseqed
|
||||
todoist-status:: ◼️
|
||||
- [[2026-02-01]] Manuscript ID SOSYM-26-00005495 is now in your Editor Center
|
||||
todoist-id:: [6fqqJqV6XmqFHJVg](https://todoist.com/showTask?id=6fqqJqV6XmqFHJVg)
|
||||
todoist-project:: #💺 EditoringChairing
|
||||
todoist-due:: 2026-02-01
|
||||
todoist-desc:: From: onbehalfof@manuscriptcentral.com Received: 2026-01-25T14:55:25Z ✉: [Web Link](https://outlook.office365.com/owa/?ItemID=AAMkADM1NGNiNjk0LTY0ZGUtNDgzOC04MDM5LWNhODNkYWNjNjU4YwBGAAAAAACT6qp78kRgRKuUMBdWEga%2FBwCOhWlC8F7PRKzlljZYZYQmAAAAAAEMAACOhWlC8F7PRKzlljZYZYQmAAihJn7SAAA%3D&exvsurl=1&viewmodel=ReadMessageItem) --- ## 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-02-01]] Re: Follow-up: Invitation to Review for Software and Systems Modeling
|
||||
todoist-id:: [6frxPVRrX2Wwjwrg](https://todoist.com/showTask?id=6frxPVRrX2Wwjwrg)
|
||||
todoist-project:: #💺 EditoringChairing
|
||||
todoist-due:: 2026-02-01
|
||||
todoist-desc:: From: lissette.almonte@uam.es Received: 2026-01-30T11:55:12Z ✉: [Web Link](https://outlook.office365.com/owa/?ItemID=AAMkADM1NGNiNjk0LTY0ZGUtNDgzOC04MDM5LWNhODNkYWNjNjU4YwBGAAAAAACT6qp78kRgRKuUMBdWEga%2FBwCOhWlC8F7PRKzlljZYZYQmAAAAAAEMAACOhWlC8F7PRKzlljZYZYQmAAikQGIKAAA%3D&exvsurl=1&viewmodel=ReadMessageItem) --- --- Dear Professor Di Ruscio, Thank you for your message. Unfortunately, I am unable to review the manuscript at this time, but I would like to suggest Lola Burgueño and Juan de Lara Jaramillo as potential alternative reviewers, as they are highly qualified
|
||||
todoist-status:: ◼️
|
||||
- [[2026-02-01]] [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.](https://teams.microsoft.com/l/message/19:e8e48abcf7934e2b90680ff9c1d56b99@thread.v2/1769154556182?context=%7B%22contextType%22:%22chat%22%7D)
|
||||
todoist-id:: [6fqFgJPRQHf9hcGg](https://todoist.com/showTask?id=6fqFgJPRQHf9hcGg)
|
||||
todoist-project:: #👨🏫 Teaching
|
||||
todoist-due:: 2026-02-01
|
||||
todoist-status:: ◼️
|
||||
- [[2026-02-01]] Nominare nuovo rappresentante studenti
|
||||
todoist-id:: [6fWVrV7q926WxpGh](https://todoist.com/showTask?id=6fWVrV7q926WxpGh)
|
||||
todoist-project:: #🎓 Services-PHDICT
|
||||
todoist-due:: 2026-02-01
|
||||
todoist-status:: ◼️
|
||||
- [[2026-02-01]] [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](https://teams.microsoft.com/l/message/19:afb6a496-7b16-4b74-8c53-1cd450e586f9_c2787b22-cc39-410e-a383-56cbdb9b69c9@unq.gbl.spaces/1769424079721?context=%7B%22contextType%22:%22chat%22%7D)
|
||||
todoist-id:: [6frVX6QM6Jp4jRw8](https://todoist.com/showTask?id=6frVX6QM6Jp4jRw8)
|
||||
todoist-project:: #👨🏫 Teaching
|
||||
todoist-due:: 2026-02-01
|
||||
todoist-status:: ◼️
|
||||
- [[2026-02-01]] SE4IOT Final Project Update - Team 7
|
||||
todoist-id:: [6frhPXP6xcPW7gF8](https://todoist.com/showTask?id=6frhPXP6xcPW7gF8)
|
||||
todoist-project:: #👨🏫 Teaching
|
||||
todoist-due:: 2026-02-01
|
||||
todoist-desc:: From: meteharun.akcay@student.univaq.it Received: 2026-01-29T10:13:50Z ✉: [Web Link](https://outlook.office365.com/owa/?ItemID=AAMkADM1NGNiNjk0LTY0ZGUtNDgzOC04MDM5LWNhODNkYWNjNjU4YwBGAAAAAACT6qp78kRgRKuUMBdWEga%2FBwCOhWlC8F7PRKzlljZYZYQmAAAAAAEMAACOhWlC8F7PRKzlljZYZYQmAAii1IdqAAA%3D&exvsurl=1&viewmodel=ReadMessageItem) --- Okay, here's a summary of the email content, followed by actionable task recommendations: **Summary of Email Content:** The email is a follow-up to a feedback discussion regarding a Smarthouse project. It details the following: * **Implemented Updates:** The code has been updated and is available in the GitHub repository at `https://github.com/phuc-tr/smarthouse`. * **Changes Summarized:** * Room profiles are now configurable within the simulator/config.yaml. * A .env file has been added for the required environment variables. * Altering the alerting logic is now possible without Node-RED changes. * **Request for Review:** The author requests review and feedback on the updated code. * **Actionable Task Recommendation:** The author suggests reviewing the changes and notifying them about any further adjustments needed. **Actionable Task Recommendations (Todoist Task Creation):** 1. **Create a Task:** "Review Smarthouse Project Updates - GitHub" 2. **Assign Priority:** High (As this is a follow-up and requires verification) 3. **Due Date:** Ideally, within 24-48 hours (to allow for review and testing) 4. **Include Details:** Add: “Investigate the .env file configuration. Confirm the environment variable loading mechanism is working as expected." 5. **Consider:** "Check if any further configuration changes are needed in the YAML configuration files." Let me know if you'd like me to refine this further! --- Dear Professor, Following your feedback on our Smarthouse project, we implemented the requested improvements. The updated version is now available in our GitHub repository: [GitHub - phuc-tr/smarthouse](https://github.com/phuc-tr/smarthouse) The changes are summarized below: *
|
||||
todoist-status:: ◼️
|
||||
- [[2026-02-01]] Final version of the Autonomous Systems project
|
||||
todoist-id:: [6fv73MCMFv963736](https://todoist.com/showTask?id=6fv73MCMFv963736)
|
||||
todoist-project:: #👨🏫 Teaching
|
||||
todoist-due:: 2026-02-01
|
||||
todoist-desc:: From: alejandro.munozmorillo@student.univaq.it Received: 2026-01-30T16:07:42Z ✉: [Web Link](https://outlook.office365.com/owa/?ItemID=AAMkADM1NGNiNjk0LTY0ZGUtNDgzOC04MDM5LWNhODNkYWNjNjU4YwBGAAAAAACT6qp78kRgRKuUMBdWEga%2FBwCOhWlC8F7PRKzlljZYZYQmAAAAAAEMAACOhWlC8F7PRKzlljZYZYQmAAik14mrAAA%3D&exvsurl=1&viewmodel=ReadMessageItem) --- Okay, here's a summary of the email, focusing on actionable tasks, and including a deadline (as assigned to Todoist): **Summary:** The email is a follow-up to a course project, specifically regarding architectural changes. The author, Alejandro Muñoz Morillo, has implemented modularity and containerization (Docker/Docker Compose) to improve the system's architecture. They've attached the final project version and GitHub link for review. The key action recommended is to thoroughly review the project and ensure coherence between implementation and documentation. **Actionable Tasks:** 1. **Review the Project:** Carefully examine the finalized project version for accuracy and alignment with the original objectives and guidelines. 2. **GitHub Link Verification:** Confirm the GitHub link is accurate and leads to the correct repository. 3. **Update Todoist Task:** Assign this task to Todoist to ensure timely completion. (Deadline: Today) Let me know if you'd like me to refine this summary further! --- Dear Professor, I hope you are doing well. We are writing to inform you that we have implemented the changes and improvements you suggested for our project in the course Software Engineering for Autonomous Systems. In particular, we have focused on impr
|
||||
todoist-status:: ◼️
|
||||
- [[2026-02-01]] ECMFA 2026 submission assignment
|
||||
todoist-id:: [6ffWC97GGvHG4qG8](https://todoist.com/showTask?id=6ffWC97GGvHG4qG8)
|
||||
todoist-project:: #📜 REVIEWS
|
||||
todoist-due:: 2026-02-01
|
||||
todoist-desc:: [Web Link](https://outlook.office365.com/owa/?ItemID=AAkALgAAAAAAHYQDEapmEc2byACqAC%2FEWg0AjoVpQvBez0Ss5ZY2WGWEJgAIjj4wRQAA&exvsurl=1&viewmodel=ReadMessageItem) Okay, here’s a task description based on the email content "ECMFA 2026 submission assignment," designed to be actionable and clearly outlined: **Task Title:** Complete ECMFA 2026 Submission – [Specify Document Name/Format - e.g., Final Report, Presentation, etc.] **Description:** This task requires you to finalize and submit the ECMFA 2026 submission, specifically [State the specific document/deliverable - e.g., the final report, the presentation slides, the data analysis]. This is a crucial step in ensuring the successful completion of the ECMFA 2026 project. **Actionable Steps:** 1. **Review Submission Guidelines:** Thoroughly review the official ECMFA 2026 submission guidelines document located at [Insert Link to Document Here – VERY IMPORTANT]. Pay close attention to formatting requirements, data sources, and required elements. 2. **Gather Required Data:** Collect all necessary data and information as outlined in the guidelines. This may involve [List specific data sources - e.g., accessing the database, reviewing reports, performing specific calculations]. 3. **Format and Organize Content:** Organize your submission content in a clear, logical, and consistent format. Ensure all sections are properly labeled and aligned. 4. **Proofread and Edit:** Carefully proofread your entire submission for any grammatical errors, typos, or inconsistencies. Check formatting for consistency. 5. **Submit the Submission:** Submit the completed document through [Specify Submission Method - e.g., Outlook, SharePoint, designated portal]. 6. **[Optional - If applicable] - Submit Feedback:** If you have any questions or require clarification on any part of the submission, please send a brief email to [Your Email Address] within 24 hours of submitting. **Deadline:** [Insert Deadline – Be realistic!] **Priority:** [High/Medium/Low - Assign a priority level.] **Assigned To:** [Your Name/Team Name] **Notes:** If you encounter any roadblocks or require assistance, please don’t hesitate to reach out to [Contact Person/Team for Support - e.g., your supervisor, the ECMFA team]. --- **To help me refine this further and make it even more tailored, could you tell me:** * **What kind of document is this submission for?** (Report, presentation, data analysis, etc.?) * **Are there any specific guidelines or requirements you want to highlight?** (e.g., specific data sources, format requirements, length restrictions?)
|
||||
todoist-labels:: #outlook365
|
||||
todoist-status:: ◼️
|
||||
- [[2026-02-01]] [mosaico-all] [MOSAICO] Exploitation Workshop: Consolidated Inputs & Next Steps
|
||||
todoist-id:: [9964588992](https://todoist.com/showTask?id=9964588992)
|
||||
todoist-project:: #Inbox
|
||||
todoist-completed:: [[2026-02-01]]
|
||||
todoist-status:: ✅
|
||||
Reference in New Issue
Block a user