transnational_access:transnational_access:research_visits
Differences
This shows you the differences between two versions of the page.
| transnational_access:transnational_access:research_visits [2026/02/13 09:56] – created fincons | transnational_access:transnational_access:research_visits [2026/02/13 10:06] (current) – fincons | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ==== Management | + | ====== Visit Management |
| - | === Overview of Research Visits === | + | ===== Overview of Research Visits |
| The research visit represents the operational phase of the Transnational Access programme and takes place after the acceptance of a Research Proposal. | The research visit represents the operational phase of the Transnational Access programme and takes place after the acceptance of a Research Proposal. | ||
| - | Through the WP11 TNA platform, visits are planned, monitored, and completed according to a structured lifecycle that ensures traceability and control of all activities performed. | + | Through the WP11 TNA platform, visits are planned, monitored, and completed according to a structured lifecycle that ensures traceability and control of the activities performed. |
| - | The management | + | Visit management primarily involves the Host Coordinator and the Fellow, each acting |
| - | === Creation of the Visit === | + | ---- |
| - | A visit is automatically | + | ===== Creation of the Visit ===== |
| + | |||
| + | A visit is generated following the acceptance of a Research Proposal. | ||
| At the time of creation: | At the time of creation: | ||
| - | * the visit is automatically set to the status '' | + | * the visit is automatically set to the Draft status; |
| - | * the main information | + | * the main information |
| * the visit becomes visible to the involved actors. | * the visit becomes visible to the involved actors. | ||
| - | The '' | + | The Draft status allows completion and verification of the required |
| - | === Planning of the Visit === | + | ---- |
| - | The planning | + | ===== Planning |
| + | |||
| + | Planning | ||
| During this phase, the Host Coordinator may: | During this phase, the Host Coordinator may: | ||
| * define the visit period; | * define the visit period; | ||
| - | * confirm the availability of the hosting facilities; | + | * confirm the availability of hosting facilities; |
| - | * update the operational information | + | * update the operational information |
| - | Once planning is completed, the visit changes | + | Once planning is completed, the visit transitions |
| - | === Execution of the Visit === | + | ---- |
| - | During the execution phase: | + | ===== Execution of the Visit ===== |
| + | |||
| + | During the visit: | ||
| * the Fellow carries out the planned research activities; | * the Fellow carries out the planned research activities; | ||
| - | * the Host Coordinator provides institutional support | + | * the Host Coordinator provides |
| - | * visit information remains | + | * visit information remains |
| - | The platform allows monitoring of the visit status in accordance | + | The platform allows monitoring of the visit status in alignment |
| - | === Completion of the Visit === | + | ---- |
| - | At the end of the research activities, the Host Coordinator updates the visit status by selecting the action '' | + | ===== Completion |
| - | With this action: | + | At the end of the research activities, the Host Coordinator selects the Finish |
| - | | + | As a result: |
| - | * the operational phase of the visit is considered | + | |
| - | * it becomes possible to proceed with reporting | + | |
| + | * the operational phase of the visit is formally | ||
| + | * post-visit | ||
| A completed visit is no longer editable. | A completed visit is no longer editable. | ||
| - | === Cancellation of the Visit === | + | ---- |
| - | If the Fellow is unable to carry out the visit or if conditions | + | ===== Cancellation of the Visit ===== |
| + | |||
| + | If the Fellow is unable to carry out the visit or circumstances | ||
| In case of cancellation: | In case of cancellation: | ||
| - | * the visit changes | + | * the visit transitions |
| * the visit does not proceed to completion; | * the visit does not proceed to completion; | ||
| - | * the cancellation is recorded by the system for traceability purposes. | + | * all involved actors are informed through notification. |
| + | |||
| + | The cancellation is recorded by the system for historical | ||
| + | |||
| + | ---- | ||
| + | |||
| + | ===== Operational Restrictions and Permissions ===== | ||
| - | === Operational Restrictions and Permissions === | + | The actions allowed on a visit depend on its current status: |
| - | The actions | + | * in the Draft status, the visit can be modified; |
| + | * in the Planned status, information is available for consultation; | ||
| + | * in the Finished and Cancelled statuses, the visit is read-only. | ||
| - | * in the '' | + | This mechanism ensures compliance with the visit lifecycle |
| - | * in the '' | + | |
| - | * in the '' | + | |
| - | This mechanism ensures compliance with the defined lifecycle and prevents unauthorised modifications. | + | ---- |
transnational_access/transnational_access/research_visits.1770972994.txt.gz · Last modified: by fincons
