CLICdp Publication Committee (PubCom)

PubCom is responsible for implementing policy with regards to all types of publications from CLICdp.

Details concerning this committee, the different types of publications, as well as the publication rules are given Annex 4 of the MoC.

If you have any questions, please contact us using clicdp-pubcom@cernNOSPAMPLEASE.ch (remove NOSPAM)

Drafts

List of CLICdp draft notes for review by Collaboration

After the deadline is passed and all comments have been implemented, drafts are marked as finished in this table.

Please assign a CLICdp-Draft number, next in sequence, when you add a new document to this table, for use in circulating to the Collaboration/entering in CDS.

This Twikisheet works behaves like googledocs, click in a cell and edit directly from the web page.

Hints and Tips

This section contains some helpful hints concerning CLICdp notes, proceedings, journal publications and presentations.

General hints and tips

  • It is suggested that you follow the guidelines of CERN's Scientific Text Processing Service
  • Please also take a look at the English language style guide from the CERN translation/minutes service
  • You are encouraged to use the CLICdp ROOT template for your plots (in particular for public notes and publications)
  • The publication procedures for CLICdp are described in the Memorandum on Cooperation in Annex 4.
  • If you have used the grid for your work (ILC VO), please acknowledge the use of LCG and OSG resources using the following acknowledgements:
This work benefited from services provided by the ILC Virtual Organisation, supported by the national resource providers of the EGI Federation. This research was done using resources provided by the Open Science Grid, which is supported by the National Science Foundation and the U.S. Department of Energy's Office of Science.
  • Tip for decreasing the image size to reduce the size of the pdf document: Run this command on the .pdf file you have produced (big.pdf): gs -sDEVICE=pdfwrite -dCompatibilityLevel=1.4 -dPDFSETTINGS=/printer -dNOPAUSE -dQUIET -dBATCH -sOutputFile=small.pdf big.pdf

I'm giving a talk at a conference/workshop, what do I do?

  • Make sure the Speakers Committee has your talk and abstract listed on the TWiki
  • Label your plots appropriately (work in progress, preliminary, CLICdp)
  • If appropriate, your talk should be marked "On behalf of the CLICdp collaboration"
  • You are encouraged to use the CLIC logo on your slides
  • You are expected to make slides available for comments two days before the talk will be given
  • The Speakers Committee may organise a rehearsal for your talk

I'm making a poster for a conference/workshop, what do I do?

  • Make sure the Speakers Committee has your poster listed on the TWiki
  • If appropriate, your poster should be marked "On behalf of the CLICdp collaboration"
  • You are encouraged to use the CLIC logo on your poster
  • Your poster should contain the name and date of the conference at which it was presented

I'm writing proceedings for a conference talk I gave, what do I do?

General remarks

  • Make sure you allow enough time for the review process (see below)
  • If possible inform PubCom well before the expected draft submission date and the conference deadline
  • It is the responsibility of the author to inform the publications committee about the intended submission to a non-open access journal
  • Write the proceedings using the template provided by the conference organisers
  • If appropriate, your proceedings should be marked "On behalf of the CLICdp collaboration".
    • The statement "This work was carried out in the framework of the CLICdp collaboration." should be removed in such a case.
  • Make sure the figures are marked "CLICdp"
  • Create a CLICdp front page using the template available in gitlab
  • Submit the document (including front page) to PubCom - you will receive comments within 1-2 days
  • Your proceedings will be added to CDS and circulated for collaboration review on CDS for seven days
  • Submit the final copy to both PubCom and to the conference organisers
  • If the conference has a review process, please submit the final version to PubCom
  • You are encouraged to upload the final version of your proceedings to the arXiv (check conference permission) using the licence CC-BY-4.0.

Detailed information

  • You will receive comments within 1-2 days
  • Notify PubCom when you have implemented the suggested changes
  • PubCom will then provide you with a draft number (CLICdp-Draft-2018-xxx) that you add to the CLICdp front page
  • Your proceedings will be opened for collaboration review on CDS for 7 days - you can see the deadline, etc. on this twiki page
  • Please add line numbers for the review process!
  • After you have implemented the comments, notify PubCom to receive the final number for your proceedings (CLICdp-Conf-2018-xxx)
  • Submit the final copy to PubCom (incl. updated CLICdp front page) as well as to the conference organisers (excl. CLICdp front page)
  • Don’t forget to remove the line numbers at this stage
  • If you have problems with uploading your contribution to arXiv, see here for some hints concerning new TeX Live version.
    • If you are using Overleaf, there is a direct "submit to arXiv" feature

I'm writing a CLICdp note, what do I do?

General remarks

  • Make sure you allow enough time for the review process (see below)
  • Write the note using the CLICdp LaTeX template available in gitlab
  • This document contains many helpful examples and guidelines
  • Submit the document to PubCom - you will receive comments within 1-2 days
  • Your note will be opened for collaboration review on CDS for two weeks
  • Submit the final copy to PubCom
  • You are encouraged to put the folder containing all files of the note to the CLICdp gitlab of released documents. Please contact the CLICdp gitlab admins to create a repository.
  • You are encouraged to upload the final version of your note to the arXiv in which case you should include the follwing sentence on the title page: "This work was carried out in the framework of the CLICdp collaboration." and use the licence CC-BY-4.0.

Detailed information

  • You will receive comments within 1-2 days
  • Notify PubCom when you have implemented the suggested changes
  • PubCom will then provide you with a draft number (CLICdp-Draft-2018-xxx) that you add to the front page of the template
  • Your note will be opened for collaboration review on CDS for two weeks
  • Please add line numbers for the review process!
  • After you have implemented the comments, notify PubCom to receive the final number for your note (CLICdp-Note-2018-xxx)
  • Submit the final copy to PubCom
  • Don’t forget to remove the line numbers at this stage
  • If you have problems with uploading your contribution to arXiv, see here for some hints concerning new TeX Live version
  • Additional information on writing CLICdp notes

I'm writing a journal publication, what do I do?

  • Make sure you allow enough time for the review process (see below)
  • Write the publication using the templates of the journal. For the collaboration review, please add a front page based on the CLICdp LaTeX template available in gitlab
  • Submit the document to PubCom - you will receive comments within 1-2 days
  • Your paper will be opened for collaboration review on CDS for two weeks
  • In addition, PubCom will assign two internal reviewers who will review the paper within the review period
  • Implement all comments and submit the final copy to PubCom
  • Once PubCom has given you the approval, you can submit the paper to the journal
  • You are encouraged to put the folder containing all files of the paper in the CLICdp gitlab of released documents. Please contact the CLICdp gitlab admins to create a repository.
  • You are encouraged to upload the final version of your note to the arXiv in which case you should include the follwing sentence on the title page: "This work was carried out in the framework of the CLICdp collaboration." and use the licence CC-BY-4.0.

-- LarsRickardStrom - 2017-03-09

Edit | Attach | Watch | Print version | History: r88 < r87 < r86 < r85 < r84 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r88 - 2018-12-14 - SimonSpannagel
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    CLIC All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright &© 2008-2018 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback