19 lines
11 KiB
Markdown
19 lines
11 KiB
Markdown
-
|
||
- [[2026-01-28]] R: Info PhD visiting period - GIACOMELLI
|
||
todoist-id:: [6fhmvW5wJxpXpfc8](https://todoist.com/showTask?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](https://outlook.office365.com/owa/?ItemID=AAMkADM1NGNiNjk0LTY0ZGUtNDgzOC04MDM5LWNhODNkYWNjNjU4YwBGAAAAAACT6qp78kRgRKuUMBdWEga%2FBwCOhWlC8F7PRKzlljZYZYQmAAAAAAEMAACOhWlC8F7PRKzlljZYZYQmAAiVbuRCAAA%3D&exvsurl=1&viewmodel=ReadMessageItem) --- 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]] Contattare studenti restituzione portatili
|
||
todoist-id:: [6f82x4WFg69Jmr99](https://todoist.com/showTask?id=6f82x4WFg69Jmr99)
|
||
todoist-project:: #🎓 Services-PHDICT
|
||
todoist-due:: 2026-01-28
|
||
todoist-status:: ◼️
|
||
- [[2026-01-28]] Manuscript in your Reviewer Center - IEEE Software, SWSI-2026-01-0024
|
||
todoist-id:: [6fjh74qpCPV5HJ38](https://todoist.com/showTask?id=6fjh74qpCPV5HJ38)
|
||
todoist-project:: #📜 REVIEWS
|
||
todoist-due:: 2026-01-28
|
||
todoist-desc:: From: onbehalfof@manuscriptcentral.com Received: 2026-01-12T07:28:14Z ✉: [Web Link](https://outlook.office365.com/owa/?ItemID=AAMkADM1NGNiNjk0LTY0ZGUtNDgzOC04MDM5LWNhODNkYWNjNjU4YwBGAAAAAACT6qp78kRgRKuUMBdWEga%2FBwCOhWlC8F7PRKzlljZYZYQmAAAAAAEMAACOhWlC8F7PRKzlljZYZYQmAAiX6FN1AAA%3D&exvsurl=1&viewmodel=ReadMessageItem) --- 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:: ◼️ |