Publication Policy
There are broadly two types of outputs expected resulting from CIRADA activity: releases of data, software, catalogues and tools, and journal publications. The process for each is different.
Data Releases
A crucial part of CIRADA is quality control and quality assurance. The project office will provide internal processes for this.
- Product releases: Advance approval from the CIRADA director and deputy director must be obtained before submission/release of all CIRADA products. Please submit such requests to the project manager. Turnaround will usually be within 5 business days.
- Output tracking: The project management office needs to know when a paper is submitted, then accepted, then published, so that the relevant publication list can be kept up to date. Please keep the project manager up to date on the progress of all publications.
All releases and publications must be either hosted or linked to from the CIRADA portal.
Journal Publications
Journal publications cannot be produced using CFI funding, so if you’re doing any time- or effort-tracking, the actual writing/submitting of the paper plus any astrophysics/science in the paper both need to be on non-CIRADA time. (But all the non-science work leading up to the paper, anything in the paper which is actually documentation, and the catalogue itself, can all be worked on within CIRADA.)
All CIRADA publications/outputs/releases outside of time-critical, time-domain science should be circulated to all@cirada.groups.io two weeks before submission or release. This has three purposes:
- general info, so everyone in CIRADA knows what is being done and being distributed
- opportunity for people to provide feedback
- opportunity to identify issues around authorship, quality control, etc
For time-critical, time-domain science (e.g., Astronomer's Telegrams, Gamma-ray Coordinates Network Circulars, VOEvents), template documents must be circulated to all@cirada.groups.io for a 2-week comment period. In cases where a template document does not exist, these publications/outputs must be circulated to all@cirada.groups.io 24 hours before submission or release.
CIRADA members and investigators may request authorship on a CIRADA product if they have made a meaningful contribution to the work circulated.
Disputes
Any concerns or disputes should be brought to the attention of the CIRADA PI and Project Manager, who will aim to provide a prompt resolution.
Standard CIRADA Acknowledgement
The following acknowledgement should be included in all publications and products resulting from CIRADA work, in addition to any other acknowledgements specific to individuals, departments or institutions as appropriate:
Additional acknowledgement for working coming out of the transient group project (excludes cutout server):