The Lasair project is funded within LSST:UK Phase B and C awards to deliver a working platform for the scientific exploitation of time domain data from the Rubin Observatory. As part of this development we exploit the Zwicky Transient Facility data stream. Access to the ZTF and Rubin data is fully public, world-wide and there is no restriction to the data access and scientific use, nor any formal further requirement. Science users in the UK, within the Rubin community (i.e. data rights holders) and world-wide can access scientific data and publish papers based on the results with no additional requirement or permission from the Lasair team. We do request proper acknowledgement, citations and credit as is standard good practice in scientific publishing.
...
Lasair is supported by the UKRI Science and Technology Facilities Council and is a collaboration between the University of Edinburgh (grant ST/N002512/1) and Queen’s University Belfast (grant ST/N002520/1) within the LSST:UK Science Consortium
TO DO : UPDATE THE ABOVE WITH NEW PHASE C GRANT NUMBERS
Lasair system papers written by, or with, the Lasair team
...
The Lasair Builders acknowledge that they must explicitly agree to co-authorship and their name appearing on the paper. If any of the Builders do not respond explicitly by the deadline requested, then the author of the paper should progress without those co-author names i.e. the Lasair policy is one of explicitly opting in and Builders must abide by this.
Science papers written with the assistance of the Lasair team
Generally, there is no need for science papers to include the Lasair builder team if the users have simply exploited the Lasair platform. The Lasair team are also happy to advise, help and assist users in using Lasair to enable scientific exploitation of the LSST and ZTF data. There is no need for co-authorship in this case. Although papers should cite the Lasair definition paper(s) listed above and include an acknowledgement.
If users have significant interaction with the Lasair team and new features and new functionality are developed or significant new code (e.g. SQL or python queries) are produced by the Lasair team then we encourage normal scientific collaboration practice to ensue. In that case, co-authorship requests should be extended to the Lasair Builder team. It may be more appropriate that only one or two of the builder team co-author the paper, if they