From 4b093b0dcf9bbf65516ac02b124152aae5b33a64 Mon Sep 17 00:00:00 2001 From: Keith Bechtol Date: Mon, 8 Jan 2024 11:34:53 -0600 Subject: [PATCH] Clarify policies for circulating drafts of science papers within Project team --- SITCOMTN-076.tex | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/SITCOMTN-076.tex b/SITCOMTN-076.tex index 4be657b..4282091 100644 --- a/SITCOMTN-076.tex +++ b/SITCOMTN-076.tex @@ -334,9 +334,9 @@ \section{Peer-reviewed Journal Publications} %Members of the Project team are free to collaborate with others beyond the Project team on science papers that use Early Science data. %Science paper processes, including reviews and approvals, are in the purview of the LSST Science Collaborations. -Science papers that rely only on \emph{released} Early Science data products are NOT covered by the Project Publication Policy.\footnote{Authors should consult with the Rubin Observatory Publication Board if they are uncertain whether a manuscript in preparation would be classified as infrastructure work covered by the Project Publication Policy.} +Science papers that rely only on \emph{released} Early Science data products are NOT covered by the Project Publication Policy; authors should consult with the Rubin Observatory Publication Board if they are uncertain whether a manuscript in preparation would be classified as infrastructure work covered by the Project Publication Policy. %Science paper processes, including reviews and approvals, are in the purview of the LSST Science Collaborations. -However, for science papers that include members of the Project team as authors, we suggest the following guidelines to promote transparency: +For science papers that include members of the Project team as authors, we suggest the following guidelines to promote transparency: %and that describe work that began prior to the release of the Early Science data products, %For science papers that include members of the Project team as co-authors and that @@ -375,7 +375,11 @@ \section{Peer-reviewed Journal Publications} %While commissioning data products may NOT be shared prior to release, derived data products may be shared via approved technotes that can then be openly discussed. \item The authors are encouraged to circulate a draft within the Project team for comments several weeks in advance of submission / public posting. - Since these non-infrastructure publications are not covered by the Project Publication Policy, there is no formal review by Rubin Observatory. + If a science paper does not contain any new Observatory science performance results, and cites appropriate references on the data products and Observatory performance, then it would not covered by the Project Publication Policy and there is no formal review by Rubin Observatory. + %Since these non-infrastructure publications are not covered by the Project Publication Policy, there is no formal review by Rubin Observatory. + If a science paper that would use released data products includes new results on Observeratory science performance, the review process described in ``Science Papers Based on LSST Products'' from the Project Publication Policy \citedsp{LPM-162} is recommended. + The benefit to the authors is the engagement of Project team members with relevant expertise. + Circulating the draft within the Project team in advance would help to ensure that the data products are used appropriately. \item The authors should encourage co-authorship as appropriate to recognize the contributions of other Project team members. No one may be listed as a co-author without their explicit permission.