|
Size: 5763
Comment:
|
Size: 9491
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| ''Guidelines'' | ---- <<TableOfContents(4)>> ---- |
| Line 3: | Line 5: |
| 1) External collaborations are strongly encouraged, provided there is no overlap and conflict with the interests of consortium members. | '''eROSITA_DE Individual External Collaborators: Guidelines''' |
| Line 5: | Line 7: |
| 2) The responsibility to approve such requests lies with the Project Scientist, on the request and recommendation the relevant Working Group chair(s). Support from the WG chair(s) and approval of the PS are mandatory. Before putting EC requests forward, WG chairs should first inform and ideally discuss such proposals with all the members of the WG, to ensure there are no conflicts. The Steering Committee will review periodically the status of EC and the progress of their activities. | The text below provide a guideline for all potential Individual external collaborators. It is mostly extracted from the official eROSITA Policy Document (signed on 16.04.2019) |
| Line 7: | Line 9: |
| 3) The basic criteria to apply when considering an EC request are a) scientific merit b) the benefit to the eROSITA project and c) benefit to the eROSITA_DE collaboration. | {{{ Individual External Collaborators (IEC) are scientists who are not Consortium members, but who are nonetheless permitted to participate in or lead projects using eROSITA_DE proprietary data in collaboration with Consortium members, contribute to eROSITA-related activities, and author related papers. IECs are approved by the PS upon request and recommendation of the relevant Working Group chair(s) and in consultation with the CCB. |
| Line 9: | Line 13: |
| 4) EC requests are made by an individual investigator (this could be extended to PhD students of the proposing investigator). Group collaborations are dealt with at project level. | An IEC is typically an individual but is understood also to include an individual and a PhD student working under their direct supervision. |
| Line 11: | Line 15: |
| 5) EC requests should be associated with a well defined project, and should not be generic requests to work on eROSITA data or general science topics. They should have defined aims and specific outputs/deliverables, typically a scientific paper or papers. The period of activity should also be defined, initially a maximum of one year, with the possibility of renewal/extension. Collaborative projects of scope greater than this are possible but do not really fit into the EC category and will need special consideration. | IEC requests are evaluated based on a written proposal. These should have defined aims, scope and duration, and specific outputs/deliverables, typically a scientific paper or papers. IEC proposals must also be submitted for non-members of the Consortium who wish to co-author publications led by a consortium member based on eROSITA_DE proprietary data. Proposals may also be submitted for projects initiated by the IEC. |
| Line 13: | Line 17: |
| 6) A consequence of the above guideline is that currently we cannot approve any EC request to work on real eROSITA data, as we are >1 year from launch (and even longer from the acquisition of the first sky map). It is very important that this is made clear to everyone approaching us at this point. |
All IECs must be sponsored by an existing consortium member, who presents the IEC proposal for consideration. The sponsoring member must be involved in the scientific work of the IEC and any resulting publication(s), and is responsible for ensuring the IEC and their project adhere to the consortium rules. IECs may also be submitted without a sponsoring consortium member. In this case the WG chairs will assign an appropriate sponsor or sponsor(s) from within the consortium to work with the IEC. The rights and scientific interests of External Collaborators shall be subordinate to those of Consortium members. |
| Line 16: | Line 19: |
| 7) On the other hand, at this point in time, we should welcome EC requests to work on "pre-launch" activities. These can be interpreted in a broad sense: it can include technical work (for example, writing software), working on simulations, making predictions and forecasting for eROSITA, but also pure scientific projects, either theoretical or observational, for example "pilot surveys" with ROSAT or XMM-Newton surveys or samples. While approved EC requests pre-launch will not guarantee access to eROSITA data later, if an existing pre-launch collaboration is in place, it is clearly more likely that a post-launch EC request will be approved. People who make EC requests asking to work on real data at this could be encouraged to rejig their proposal for pre-launch activities, with this in mind. The WG chairs and the PS should decide whether the pre-launch activity is valuable in itself, however, and clearly if an EC proposes a pre-launch activity which does not deliver any output, this might not be positive for future EC requests for real data. | IEC proposals will be evaluated by the relevant WG Chair(s), in consultation with the WG to ensure there is no conflict of interest. The WG chairs may suggest additional participants or collaborators in the project in addition to the sponsor(s). Other consortium members will be permitted to join the external collaboration project and become an author of any consequent publications should their contribution merit authorship, consistent with the publication policy. The PS grants IEC status upon recommendation of the WG chair(s) and in consultation with the CCB, to ensure there are no remaining conflicts with other Working Groups. |
| Line 18: | Line 21: |
| 8) Approved External Collaborators are not members of the eROSITA_DE consortium. As such ECs should not routinely or automatically be invited to eROSITA_DE consortium meetings. On the other hand there is always the possibility to invite guests to consortium meetings, independent of any EC status, if it is seen as beneficial to the consortium and useful for the meeting. Requests for such attendance should be made to the PI or PS. ECs can be encouraged to visit a eROSITA_DE consortium institution during the collaboration period to discuss and work on the project - though clearly no project resources can be made available to finance this. | The CCB should review periodically the status of IEC and the progress of their activities. When requested to do so, IEC shall submit reports to the PS and the relevant WG chair(s) describing their activities related to the use of eROSITA_DE proprietary data. |
| Line 20: | Line 23: |
| 9) As per general policy, EC may not participate in research project that make use of proprietary eROSITA data outside the eROSITA_DE collaboration (i.e. work at the same time on Russian proprietary data), unless authorized to do so by the PI. | IECs will typically be granted for a period of one year, with the possibility of renewal/extension. Renewal requests are the responsibility of the IEC and/or the sponsoring member and IEC status will lapse by default in the absence of such a renewal proposal. The sponsor may nonetheless apply for renewal of IEC status that has lapsed with the agreement the WG chair(s). Research projects and publications led by IECs will be submitted to the Publication Archive by the sponsoring Consortium member. If he/she has left the Consortium, a new member will act as liaison for the External Collaborator, and will be responsible for uploading and updating EC-led publication in the Publication Archive. As per general policy, IEC may not participate in research projects that make use of proprietary eROSITA data outside the eROSITA_DE collaboration (i.e. work at the same time on Russian proprietary data), unless authorized to do so by the PI. Collaborative projects of scope greater than that described above will need special consideration ('Group External Collaborations'). }}} ==== Practicalities ==== * Sponsoring consortium members are encouraged to discuss IEC possible proposals with their WG chair(s) and with other members of the WG before submission of the proposal. * Between the time a proposal is submitted through the wiki (see below), and the time it is approved by the PS, a typical timescale is a few weeks. This is simply because the WGs need to properly assess the proposals first, then they need to be announced to the CCB (which meets only every second week), and finally approved by the PS. * The procedure to approve simple co-authorship of external scientists in eROSITA_DE papers (i.e., for example, IEC for people who will not work on eROSITA data, but only on ancillary datasets within an eROSITA_DE project/paper) shall be faster and simpler: it will be possible to bundle together multiple IECs for the same paper. A specific template for '''co-authorship IEC request''' is provided below. ==== Proposal Preparation: standard IEC ==== 3 The first step is to identify the relevant Working Group(s) for the project. Within the WG(s) the IEC proposer should contact and define a "sponsoring member". This can be the Chair of the WG, or any full member of the consortium. Once the project is identified and defined, please fill in the [[attachment:eROXXX_ECrequest_LastnameFirstname_ID-3.docx|doc template]] with all relevant information. - A complete proposal will contain: * Name/Affiliation/email of the EC * Name/Affiliation/email of the proposing consortium member; * A detailed description of the scientific proposal; * Expected Outcome (scientific publication(s), a catalog, shared software and/or simulations, resources, etc) * A list of potential collaborators in the eROSITA_DE; * Expected duration of the project After the project is defined and the template form filled in, it is the responsibility of the Sponsoring Member to submit it to the collaboration, following the instructions below. ==== Proposal Preparation: co-authorship IEC requests ==== These must be based on existing approved projects/papers already present in eROPUB. Co-authors IEC are not supposed, under normal circumstances, to work directly on eROSITA data. Once the project leader/PI is identified and defined a list of collaborators who need to be co-authors of the paper (because of their contribution to the followup efforts, or interpretation, she/he should fill in the [[attachment:eROXXX_IECrequestPaper_eroPUB_ID.docx|doc template for co-authors IEC]] with all relevant information. There is no limit to the number of collaborators that can be included in a COA-IEC proposal, provided it is restricted to the collaborators that actually contributed in a way or another, to the paper. For standard papers the request should be submitted as early as possible after eROPUB publication, and in any case before the submission of the paper for the 3 weeks internal review, at the latest. For particularly urgent cases ( Atel, ToOs, DDTs) the request can be submitted for a fast response directly to the PI who will discuss it with the relevant WG chairs. - A complete proposal will contain: * Name/Affiliation/email of the proposing consortium member * Title of paper and Number of eROPUB approved project; * Name/Affiliation/email of the ECs; * A short description of the contribution of each EC to the work After the template form is filled in, it is the responsibility of the Sponsoring Member to submit it to the collaboration, following the instructions below (first approval by Working Group and then CCB). |
| Line 24: | Line 71: |
| HOW to submit EC proposals in the eROSITA_DE Wiki | How to submit EC proposals in the eROSITA_DE Wiki (for sponsoring Consortium members) |
| Line 26: | Line 73: |
| 0. Login into the Wiki | |
| Line 28: | Line 74: |
| 1. edit the URL | |
| Line 30: | Line 75: |
| - example: let's say, the user is member of EroStars; then go to https://wiki.mpe.mpg.de/eRosita/EroStars/ - then the proposal wiki page will have to be named https://wiki.mpe.mpg.de/eRosita/EroStars/EcProposalName (where Name is a unique identifier of the proposal, typically the Name of the External collaborator) |
'''1. Uploading Proposals on the Wiki''' |
| Line 35: | Line 77: |
| 2. Use the Template Form | 1.1 Login into the Wiki |
| Line 37: | Line 79: |
| - You will then presented with a blank page saying: "This page does not exist yet. You can create a new empty page, or use one of the page templates." - On the left column (page templates to be chosen from), click on "EcProposal" |
1.2 Edit the URL |
| Line 40: | Line 81: |
| 3. Edit the template and save page (you might also want to subscribe to this page to get notification when it is evaluated) | * example: let's say, the user is member of EroStars; then go to wiki.mpe.mpg.de/eRosita/EroStars/ * then the proposal wiki page will have to be named wiki.mpe.mpg.de/eRosita/EroStars/EcProposalName (where Name is a unique identifier of the proposal, typically the Name of the External collaborator) |
| Line 42: | Line 84: |
| - Please provide all required infos | 1.3 Use the right [[EcProposalTemplate|Wiki template]] and save the page (you might also want to subscribe to this page to get notification when it is evaluated) with the Name specified in point 1.2 above. |
| Line 44: | Line 87: |
| - A complete proposal will contain: (1) Name/Affiliation/email of the EC; (2) Name/Affiliation/email of the proposing consortium member; (3) a detailed description of the scientific proposal (figures or .pdf files, max. 2 pages can be attached); (3) Expected Outcome (scientific publication(s); a catalog; shared software and/or simulations; resources; etc); (4) A list of potential collaborators in the eROSITA_DE; (5) Expected duration of the project |
|
| Line 47: | Line 88: |
| 4. Proposal Evaluation | '''2. Proposals Submission and Evaluation''' |
| Line 49: | Line 90: |
| - At this point, I will be receiving an automatic notification message. - I will collect the list of all proposals in the Wiki page: https://wiki.mpe.mpg.de/eRosita/EcProposalList, including the relevant status (pending/approved/terminated, etc.) - I will notify the relevant WG chair(s), asking for a first evaluation of the proposal by the WG (a general discussion among WG members will be very welcome). Once a decision is taken by the WG+PS, I will modify the status of the proposal (into accepted until...) |
* The eROSITA_DE sponsoring member loads a proposal to the wiki, and add it to the list in the page EcProposalList. This act constitutes the official "submission" of the proposal * The whole CCB is notified automatically of any change of the EcProposalList page, and so are the relevant WG chair(s) represented in the CCB. Other members of the collaboration are free to subscribe to the wiki page containing the list of IEC proposal, so they also get a notification. * The relevant WG chair(s) collect comments & concerns from the WG(s) (possible scientific conflicts) within a time period of 2 weeks. * If the above process ends up with a positive recommendation of the WG, the relevant WG chair(s) contact the chair of CCB notifying that the proposal is ready to be discussed at the next CCB. This goes into the CCB agenda. * At the next CCB meeting, IEC proposal is approved or rejected by the CCB * The PS informs the sponsoring eROSITA_DE collaboration member about the outcome and modify the status of the proposal on the wiki (pending/approved/terminated, etc.) accordnigly. |
Contents
eROSITA_DE Individual External Collaborators: Guidelines
The text below provide a guideline for all potential Individual external collaborators. It is mostly extracted from the official eROSITA Policy Document (signed on 16.04.2019)
Individual External Collaborators (IEC) are scientists who are not Consortium members, but who are nonetheless permitted to participate in or lead projects using eROSITA_DE proprietary data in collaboration with Consortium members, contribute to eROSITA-related activities, and author related papers.
IECs are approved by the PS upon request and recommendation of the relevant Working Group chair(s) and in consultation with the CCB.
An IEC is typically an individual but is understood also to include an individual and a PhD student working under their direct supervision.
IEC requests are evaluated based on a written proposal. These should have defined aims, scope and duration, and specific outputs/deliverables, typically a scientific paper or papers. IEC proposals must also be submitted for non-members of the Consortium who wish to co-author publications led by a consortium member based on eROSITA_DE proprietary data. Proposals may also be submitted for projects initiated by the IEC.
All IECs must be sponsored by an existing consortium member, who presents the IEC proposal for consideration. The sponsoring member must be involved in the scientific work of the IEC and any resulting publication(s), and is responsible for ensuring the IEC and their project adhere to the consortium rules. IECs may also be submitted without a sponsoring consortium member. In this case the WG chairs will assign an appropriate sponsor or sponsor(s) from within the consortium to work with the IEC. The rights and scientific interests of External Collaborators shall be subordinate to those of Consortium members.
IEC proposals will be evaluated by the relevant WG Chair(s), in consultation with the WG to ensure there is no conflict of interest. The WG chairs may suggest additional participants or collaborators in the project in addition to the sponsor(s). Other consortium members will be permitted to join the external collaboration project and become an author of any consequent publications should their contribution merit authorship, consistent with the publication policy. The PS grants IEC status upon recommendation of the WG chair(s) and in consultation with the CCB, to ensure there are no remaining conflicts with other Working Groups.
The CCB should review periodically the status of IEC and the progress of their activities. When requested to do so, IEC shall submit reports to the PS and the relevant WG chair(s) describing their activities related to the use of eROSITA_DE proprietary data.
IECs will typically be granted for a period of one year, with the possibility of renewal/extension. Renewal requests are the responsibility of the IEC and/or the sponsoring member and IEC status will lapse by default in the absence of such a renewal proposal. The sponsor may nonetheless apply for renewal of IEC status that has lapsed with the agreement the WG chair(s).
Research projects and publications led by IECs will be submitted to the Publication Archive by the sponsoring Consortium member. If he/she has left the Consortium, a new member will act as liaison for the External Collaborator, and will be responsible for uploading and updating EC-led publication in the Publication Archive.
As per general policy, IEC may not participate in research projects that make use of proprietary eROSITA data outside the eROSITA_DE collaboration (i.e. work at the same time on Russian proprietary data), unless authorized to do so by the PI.
Collaborative projects of scope greater than that described above will need special consideration ('Group External Collaborations').
Practicalities
- Sponsoring consortium members are encouraged to discuss IEC possible proposals with their WG chair(s) and with other members of the WG before submission of the proposal.
- Between the time a proposal is submitted through the wiki (see below), and the time it is approved by the PS, a typical timescale is a few weeks. This is simply because the WGs need to properly assess the proposals first, then they need to be announced to the CCB (which meets only every second week), and finally approved by the PS.
The procedure to approve simple co-authorship of external scientists in eROSITA_DE papers (i.e., for example, IEC for people who will not work on eROSITA data, but only on ancillary datasets within an eROSITA_DE project/paper) shall be faster and simpler: it will be possible to bundle together multiple IECs for the same paper. A specific template for co-authorship IEC request is provided below.
Proposal Preparation: standard IEC
3 The first step is to identify the relevant Working Group(s) for the project. Within the WG(s) the IEC proposer should contact and define a "sponsoring member". This can be the Chair of the WG, or any full member of the consortium. Once the project is identified and defined, please fill in the doc template with all relevant information.
- A complete proposal will contain:
- Name/Affiliation/email of the EC
- Name/Affiliation/email of the proposing consortium member;
- A detailed description of the scientific proposal;
- Expected Outcome (scientific publication(s), a catalog, shared software and/or simulations, resources, etc)
- A list of potential collaborators in the eROSITA_DE;
- Expected duration of the project
After the project is defined and the template form filled in, it is the responsibility of the Sponsoring Member to submit it to the collaboration, following the instructions below.
Proposal Preparation: co-authorship IEC requests
These must be based on existing approved projects/papers already present in eROPUB. Co-authors IEC are not supposed, under normal circumstances, to work directly on eROSITA data. Once the project leader/PI is identified and defined a list of collaborators who need to be co-authors of the paper (because of their contribution to the followup efforts, or interpretation, she/he should fill in the doc template for co-authors IEC with all relevant information. There is no limit to the number of collaborators that can be included in a COA-IEC proposal, provided it is restricted to the collaborators that actually contributed in a way or another, to the paper. For standard papers the request should be submitted as early as possible after eROPUB publication, and in any case before the submission of the paper for the 3 weeks internal review, at the latest. For particularly urgent cases ( Atel, ToOs, DDTs) the request can be submitted for a fast response directly to the PI who will discuss it with the relevant WG chairs.
- A complete proposal will contain:
- Name/Affiliation/email of the proposing consortium member
- Title of paper and Number of eROPUB approved project;
- Name/Affiliation/email of the ECs;
- A short description of the contribution of each EC to the work
After the template form is filled in, it is the responsibility of the Sponsoring Member to submit it to the collaboration, following the instructions below (first approval by Working Group and then CCB).
How to submit EC proposals in the eROSITA_DE Wiki (for sponsoring Consortium members)
1. Uploading Proposals on the Wiki
1.1 Login into the Wiki
1.2 Edit the URL
example: let's say, the user is member of EroStars; then go to wiki.mpe.mpg.de/eRosita/EroStars/
- then the proposal wiki page will have to be named wiki.mpe.mpg.de/eRosita/EroStars/EcProposalName (where Name is a unique identifier of the proposal, typically the Name of the External collaborator)
1.3 Use the right Wiki template and save the page (you might also want to subscribe to this page to get notification when it is evaluated) with the Name specified in point 1.2 above.
- Do not forget to set the appropriate EroXxx group in ACL and Title etc.
2. Proposals Submission and Evaluation
The eROSITA_DE sponsoring member loads a proposal to the wiki, and add it to the list in the page EcProposalList. This act constitutes the official "submission" of the proposal
The whole CCB is notified automatically of any change of the EcProposalList page, and so are the relevant WG chair(s) represented in the CCB. Other members of the collaboration are free to subscribe to the wiki page containing the list of IEC proposal, so they also get a notification.
The relevant WG chair(s) collect comments & concerns from the WG(s) (possible scientific conflicts) within a time period of 2 weeks.
- If the above process ends up with a positive recommendation of the WG, the relevant WG chair(s) contact the chair of CCB notifying that the proposal is ready to be discussed at the next CCB. This goes into the CCB agenda.
- At the next CCB meeting, IEC proposal is approved or rejected by the CCB
- The PS informs the sponsoring eROSITA_DE collaboration member about the outcome and modify the status of the proposal on the wiki (pending/approved/terminated, etc.) accordnigly.