/ismir2016-lbd

ISMIR 2016 Late-Breaking/Demo Submission

Thanks for your interest in submitting a late breaking/demo (LBD) paper for ISMIR 2016. The submission guidelines for this year are as follows:

  • A submission should be an extended abstract describing a preliminary result, idea, application, or a demo of a new product or technology.
  • Submissions should have one page (preferred) or two pages (maximum) of content, with no limit on the size of the bibliography (i.e. all pages past the second must only contain references).
  • All LBD papers are required to be presented by one of the authors as a poster (and optionally a live demo) on the final day (August 11th) of ISMIR 2016. Posters must use portrait orientation and be no larger than A0 or 36 x 48 inch. LBD presenters can take advantage of the on-site poster printing service, but note that orders must be placed before 7/24 at 6:30PM EST!
  • This year, the LBD session will be open to the public, so we particularly encourage submission of projects of interest to a broad/nonscientific audience.
  • Submission will be open until August 10th, 2016. Please note that if you are submitting something which is very late-breaking, you will still be expected to present it as a poster during the LBD session.
  • Submissions should not be anonymized.
  • All submissions will undergo a light peer review. Note that all submissions and review will all be completely viewable by the public.
  • Templates are available for LaTeX and Word.

This year, we are handling submissions through GitHub! If you don't have experience with git/GitHub, don't worry, you can do everything from your browser; see below for a tutorial. If you are comfortable with using git, please follow these steps to create a submission:

  1. Fork this repository.
  2. In your fork, add a PDF of your paper to the submissions folder. The PDF should be named (first author's last name)-(first word of title).pdf; for example, if the first author is Joe Shmoe, and the paper's title is "Music is Cool", the PDF should be called shmoe-music.pdf.
  3. Create a pull request to merge your fork. Make the title of the pull request the title of the paper.
  4. Review will take place within the pull request; after any necessary revisions the paper will be accepted when the pull request is merged.

Submission Tutorial

Fortunately, GitHub is easy to use even if you have no experience with git or the command line. The following steps will create a new submission; if you have any issues, please don't hesitate to email craffel@gmail.com.

  1. Download the LaTeX or Word template and write your LBD extended abstract.

  2. If you're using Word, save the Word document as a PDF. If you're using LaTeX, you should have a PDF already.

  3. Rename your PDF (first author's last name)-(first word of title).pdf; for example, if the first author is Joe Shmoe, and the paper's title is "Music is Cool", the PDF should be called shmoe-music.pdf.

  4. If you aren't signed up for GitHub, sign up here. You don't need a paid account.

  5. Create a fork of this repository by clicking on the "Fork" button at the top of this page, which looks like this:

    fork

  6. In your new repository, navigate to the submissions directory (after navigating, the URL should be something like https://github.com/your-github-username/ismir2016-lbd/tree/master/submissions):

    submissions

  7. Click the "Upload files" button:

    upload

  8. Upload your correctly-named PDF, and hit "Commit changes" at the bottom of the page:

    commit-changes

  9. Click the "New Pull Request" button:

    new-pull-request

  10. You should see a page which looks like this; click the "Create Pull Request" button:

    create-pull-request

  11. Make the pull request title the title of your paper, and click the "Create Pull Request" button:

    title-create-pull-request

  12. This will take you the pull request page for your paper, with a URL like ismir#2. Save this URL for future reference. At this point, you have submitted your extended abstract; don't close the pull request.

  13. The paper will be reviewed within the pull request. You may be instructed to update your PDF with a few changes. To do so, simply follow steps 6-8 again with your updated PDF (i.e. navigate to the submissions directory in your fork and upload your new updated PDF). The pull request will be updated automatically.

  14. Your pull request will be merged (i.e. your PDF will be included in the main repository) once the review is over. That's it!

If you have any questions or problems, feel free to email craffel@gmail.com.