Agenda190212

From Publication Committee

TIME


Tuesday, February 12: 12:00 PM Hawaii; 5:00 PM Eastern US; 10:00 PM UK; 11:00 PM Germany;

Wednesday, February 13: 6:00 AM Beijing


CONNECTION


Let's try using the same method as before: From a web browser (only Chrome works reliably), go to https://bridge.iu.edu, enter 230267 and your name, then click Connect.


AGENDA



(1) Status of the PubComm reviews. Thoughts on the current PubComm procedures? Suggestions?


(2) New policy for publications using BESIII software. Here is the latest version of a proposed addition to the publication policy:

Publications using BESIII software (BESIII Monte Carlo or reconstruction packages, etc.), but not including the full BESIII author list, are generally discouraged. There are two primary reasons: first, such publications do not give due credit to the authors of the BESIII software; second, the publication quality reflects on the credibility of the BESIII experiment even though the publication has not passed the BESIII publication procedures. Exceptions to this rule can be granted by the spokespersons. For example, sensitivity studies for a future super tau-charm factory could greatly benefit from the BESIII software and these studies should be permitted. Authors are encouraged to discuss possible studies with the spokespersons at an early stage of the process in order to check that the studies are appropriate. A few guidelines should be followed:

  • The publication of sensitivity studies using BESIII software for measurements that could be improved with current BESIII data, including first measurements, are not allowed.
  • "BESIII" should not be included in the title of the publication.
  • The BESIII software group should be acknowledged.
  • The following should be included: "The results presented in this paper are those of the authors alone, and are not endorsed by the BESIII collaboration; however, we thank our colleagues for allowing us to make use of the BESIII simulation and software environment."


(3) New policy for making data public. More details on HEPData are below. Here is a draft guideline for the publication policy:

Authors and the review committee are encouraged to think about how published data and results might be used by theorists after publication. In some cases it may be beneficial to supply efficiencies or resolutions as supplementary information to a publication. Including this information as part of the review process would help ensure the quality of the information that might later be used in external analyses. Published results should also be submitted to the HEPData database. A BESIII Data Coordinator will be responsible for initiating submissions to the HEPData database.

Further information on the HEPData database:

HEPData (http://www.hepdata.net, formerly the Durham reaction database) is a site that collects published data and distributions (plus supplementary data like efficiencies and resolutions) and makes them available to the public (e.g. theorists).

Uploading to HEPData has two advantages:

  • In the situation where theorists are asking for data from a published plot, we can direct them to the HEPData entry. That way everyone has access to the same information.
  • During a paper review, authors and reviewers can think about what, specifically, they would like to upload to HEPData. That way those data (including efficiencies, resolutions, etc.) can be reviewed for that purpose. This would then remove some of our current difficulties -- deciding whether or not some data is public -- since that decision would be part of the paper review process.

To upload data to HEPData, three people need to be involved: (1) Coordinator: this would be the HEPData coordinator from BESIII (a future "Data Coordinator"?). The coordinator initiates a data submission. (2) Uploader: this is usually the primary author of the paper. The uploader prepares and submits the actual data. (3) Reviewer: this is someone else related to the paper who can review the accuracy of the submission. In our case, the chair of the review committee would work.

Practically, to get this going, I think we need to do two things:

  • form a new "Data Coordinator" position to interface with HEPData;
  • put something in the publication policy about keeping submissions to HEPData in mind when reviewing papers.