iPres 2018 Submission Instructions

---

• All contributions should be submitted through Easy Chair.
• EasyChair accepts PDF files. 
• All Contributions are due by April 15.
• All peer-reviewed contributions will be reviewed by at least two reviewers, three for papers.
• Non peer-reviewed contributions will not go through Easy Chair - watch for updates beginning in May. 
• All accepted contributions will be published in the conference proceedings (in digital form).

*Specific instructions for individual submission types below.*

General Acceptance Criteria

The reviewers will apply the following guidelines to assess the quality of the submissions. They are provided here to provide authors with an indication of what is expected from their submissions.

Is the length appropriate (ex. short papers 3–5 pages, long papers 8–10 pages)?

• Does the contribution make a significant and original addition to the digital preservation practices or research?
• Is the contribution clearly written?
• Does it fall under one of the conference themes [See https://ipres2018.org/call-for-contributions for Themes]
• Has the work been published/presented in some form before?

Content and Quality Evaluation

• Does the work significantly advance digital preservation knowledge?
• Does the work adequately build on or contextualize previous work?
• Is there sufficient evidence for the claims presented by the author(s)?
• Are the references and/or citations appropriate?
• Are there outcomes that others working in digital preservation can benefit from?
• Does the topic extend and/or enhance digital preservation discourse?

Abstracts

Contributions for iPRES 2018 include an optional paper abstract review. The iPRES 2018 Program Committee will provide feedback and suggestions for abstracts received between 15 February and 20 March. While submitting your paper abstract is voluntary, this is an important opportunity to get feedback about your proposal prior to submitting your paper and we hope to hear from many of you about your ideas. Your abstract should be at least 300 words and not exceed 500 words. The abstract should contain the following elements:    

• Title: Give the paper a name, be as precise as possible.
• Author(s)/Presenter/s: Identify author(s) of paper with name, affiliation
• Submitter: Who is submitting this proposal? Include professional title and expertise (no more than three sentences).
• Conference Theme Addressed: Please note how the proposed paper aligns with the Conference theme(s).
• Description: Please give a brief description of the scope and aim of the proposed paper. Please clearly describe the topic that will be presented and state its unique contribution to the field.
• Type of submission: Indicate Abstract for Short Paper or Long Paper 

Long and Short Papers

*Long and short papers are due for peer review by April 15* 

Authors may choose to use the ACM sigconf template for submitting papers. See template with instructions for Word and LaTeX http://www.acm.org/publications/article-templates/proceedings-template.html.

The ACM template is not required: Authors may choose to submit a document that contains the sections identified in the ACM template.

• Title: Give the paper a name, be as precise as possible.
• Author(s)/Presenter/s Names, Author(s)/Presenter/s Organizations: Identify author(s) of paper with name, affiliation
• Abstract
• Conference Theme(s) Addressed: Choose one or more relevant terms from the call for submissions:
  • Collaboration and capacity-building
  • Lessons learned within and across domains
  • Technological infrastructure
  • Sustainable digital preservation approaches and communities
• Keywords: Generated by the author(s)
• Introduction
• <Sections>: Author(s) are encouraged to define sections clearly.
• Conclusion: Takeaways and Discussion
• Acknowledgments
• References

Proposals for thematic panels to be held during the main conference program. Panel proposals will be judged on the merits of the proposal and relevance for the expected audience. Proposals must detail the subject and desired outcomes for the panel discussion as well as the proposed panelists.

• Title: Give the panel a name, be as precise as possible.
• Presenter/s: Indicate suggested panelists and chair; or as much   information as you have about panelists.
• Submitter: Who is submitting this proposal? Include professional title and expertise (no more than three sentences). 
• Conference Theme Addressed: Please note how this panel aligns with the Conference theme(s).
• Description: Please give a brief description of the scope and aim of the panel. Please clearly describe the topic that will be presented and state its unique contribution to the field.
• Type of submission: Panel

Posters are ideal for reporting on emerging issues and on works in progress. Demonstrations provide an opportunity to highlight and share innovative solutions. Both require an extended abstract of up to 2 pages that clearly describes the topic to be presented and states its unique contribution to the field. Posters and demonstrations should aim to improve knowledge, show new technical capabilities, or share solutions and experience in the field.

The poster session will include a “minute madness” session, where presenters will have exactly 60 seconds to entice people to stop by during the poster exhibition session. 

This year we are inviting digital-only poster submissions. Specific instructions on preparing posters will be provided by the Program Committee to accepted posters. 

There will be an award for best poster that will be presented on Wednesday of the conference.

• Title: Give the poster/demonstration a name, be as precise as possible.
• Presenter/s: Indicate the name, professional title, and expertise of each speaker (no more than three sentences per speaker).
• Submitter: Who is submitting this proposal? Include professional title and expertise (no more than three sentences).
• Conference Theme Addressed: Please note how this poster/demo aligns with the Conference theme(s).
• Description: Please give a brief description of the content/aim of the   poster/demo. Please clearly describe the topic that will be presented and   state its unique contribution to the field.
• Type of submission: Indicate Poster or Demonstration

For Demonstrations only

• Required infrastructure and/or resources: Indicate the materials required in order to run the demonstration (e.g., PC, projector, audio, WiFi, etc)
• Duration: Indicate the length of the demonstration
• Goals: Explain 2 or 3 of the central goals of the demo (e.g. improve   knowledge about the xx domain, show the new technical possibilities for   accessing data, search for solutions through discussion and sharing of experiences, etc.)

Workshops are intended to be hands-on and interactive, and proposers are free to decide how to structure and design them. Workshops usually involve the development of a skill, related to the topic covered in the workshop. While workshops involve more hands-on learning, they should also allow for discussion, interaction and debate on the topic of the class.

Tutorials should focus on a single topic and designate whether it aims at an introductory level or an expert level. Tutorials allow time for group discussion of content and debate on the themes and concepts covered in the class. Tutorials need not be hands-on. Proposers are free to decide how to structure them.

Please prepare a proposal (to submit as a PDF in EasyChair) with the following fields of information completed. Peer reviewers will only have this information to determine acceptance of your proposal, so please be clear and thorough for each bullet point below:

• Title: Give the tutorial/workshop a name, be as precise as possible.
• Presenter(s)/Instructor(s): Indicate the name, professional title, and expertise of each speaker (no more than three sentences per speaker).
• Submitter: Who is submitting this proposal? Include professional title and expertise (no more than three sentences).
• Conference Theme Addressed: Please note how this tutorial/workshop aligns with the Conference theme(s).
• Description: Provide a detailed (no more than three page) description of the tutorial/workshop, including a proposed agenda outline in bullet points.
• Type of submission: Indicate Workshop or Tutorial. A workshop assumes hands-on activity, whereas a tutorial is an opportunity to explicate a method or procedure. Please refer to the call for Workshops and Tutorials for more details.
• Goals/learning objectives: List 3 of the central goals of the tutorial/workshop (e.g., improve knowledge about the xy domain, show the new technical possibilities for accessing data, search for solutions through discussion and sharing of experiences, etc.)
• Target audience: Indicate the target audience for the tutorial/workshop (e.g., IT engineers, audio technicians, documentarists, management, archivists, etc.)
• Content: Indicate content to be covered during the tutorial/workshop. A full agenda will be requested for accepted workshops and tutorials.
• Conditions/required knowledge: Indicate knowledge/minimal requirements needed to follow the tutorial/workshop. Please also indicate any software/hardware that participants are required to bring.
• Required infrastructure and/or resources: Indicate the materials that iPres would need to provide for you in order to run the tutorial/workshop (e.g., PC, projector, audio, WiFi, whiteboard, etc).
• Length: Indicate the proposed length of the tutorial/workshop (in hours).