Workflow - Publishing Modification Comments
Should the discussions concerning a suggested modification be published? If so, when and how should they be published?
In some academic workflows, discussions generated by publications are published as commentary articles, co authored by the participants. This can be done for a variety of reasons, such as incentivizing commenting, increasing communal participation and inclusivity, etc. In other workflows, ensuing discussions are left unpublished. It is important for the scientonomic workflow to clearly articulate how and when, if at all, the discussions on suggested modifications should be published.
In the scientonomic context, this question was first formulated by Hakob Barseghyan and Jamie Shaw in 2019. The question is currently accepted as a legitimate topic for discussion by Scientonomy community. At the moment, the question has no accepted answer in Scientonomy.
|Community||Accepted From||Acceptance Indicators||Still Accepted||Accepted Until||Rejection Indicators|
|Scientonomy||22 December 2019||The publication of Shaw and Barseghyan (2019) is and indication of the acceptance of the question.||Yes|
|Publishing Modification Comments (Shaw-Barseghyan-2019)||The discussions concerning a suggested modification are to be published once a communal verdict is available. The discussions are to be published in the journal as special commentary articles co-authored by all participants of the discussion or in special edited collections.||2019|
|Modification||Community||Date Suggested||Summary||Verdict||Verdict Rationale||Date Assessed|
|Sciento-2019-0002||Scientonomy||22 December 2019||Accept that the discussions concerning a suggested modification are to be published once a communal verdict is available. The discussions are to be published in the journal as special commentary articles co-authored by all participants of the discussion or in special edited collections.||Open|
There is currently no accepted answer to this question.
This topic is a sub-topic of Scientonomic Workflow.