This handbook was last revised in April 2022.

Introduction

This document is intended to serve both as an aide-memoire for the Open Repositories organization and as a guide for each year's conference organizers. We attempt to keep this as up to date as possible, but there may be areas which are inaccurate. If you have questions, please contact the Chair of the Open Repositories Steering Committee.

...

(Please note that the Host and Program Committee chairs sit on the Steering Committee and participate in much of the decision making there.)

Open Repositories Resources

...

We have provided a template here for the EoI: OpenRepositories Bid EoI template (Google Document that may be downloaded as a word document).

After the closing date the ORSC will examine the EoIs and invite one or more institutions to submit a detailed bid. The choice of which EoIs are followed up will be influenced by a number of factors, including:

...

For many OR attendees the cost of attending a conference is significant - especially where transcontinental air travel is involved.  The ORSC must consider the proposed location of a conference in terms of both travel costs and likely accommodation costs (although this latter would become clearer when a detailed bid is submitted).

Preparing a Detailed Bid

Resources

There is a range of resources available to those who are invited to submit a detailed conference bid.  In   In particular, bidders will be given access to the successful bids submitted in previous years and , where available, financial summaries prepared after each conference showing the actual expenditureinformation about previous years conferences. This handbook is also meant to be a resource to help ensure the bid meets the expectations of the OR SCORSC. The OR SC ORSC contains a number of individuals who have direct experience of preparing a successful bid for and, subsequently, hosting a past OR conference; they too are a resource that can be called upon if required.

Fiscal Responsibility

It is not the intention that hosting OR  should be a financial burden on the organising institution. Theirs should be a contribution in kind - providing staff time, and associated facilities, to organise and manage the event; the conference fees and sponsorship income should cover all other expenditure. That said, the OR SC recognizes that many organizations may have to put significant funds towards reserving a venue, for example, well prior to recouping the costs. The bidder should be cognizant that they will be bearing the financial risk of putting these funds forward and potentially of bearing a loss if the conference does not meet targets of sponsorship and registration. All but one OR conference (PEI) have had a surplus at the end of the conference. Please note that it is part of the host’s agreement with the OR SC that any such surplus be passed back to the OR reserve fund for the benefit of future events; It is not the intention that this fund be used to subsidise an unprofitable conference unless extraordinary circumstances can be cited. If providing the surplus back to OR is not possible due to organizational circumstances, we request that we are notified of that in the bid. 

Ultimately, since there is no legal Open Repositories organisation, the hosts are putting on a conference and using the Open Repositories branding. It follows that the hosts must take fiscal responsibility for any contracts that they enter into during the course of conference organisation and must ensure that they are covered by any appropriate insurances (including liability insurance).

Elements of the Bid

The Steering Committee anticipates that the financial element of a bid will be supplied as an Excel spreadsheet or similar. It should cover the costs of all aspects of the conference that will require funding. It should include a reasonable estimate of income from sponsorship (based on previous years' actual figures), and it should break even based on a realistic but conservative estimate of attendance. It is the responsibility of bidding institutions to consider past bids in detail and come up with their own itemised list, but it should include the following:

• Daily meals and refreshment breaks

• Two-three evening events (on other evenings delegates make their own arrangements) - see https://www.diglib.org/dlf-events/dlf-social-event-checklist/ for a useful set of guidelines on social events

• Ideas Challenge Reception (often underwritten by a sponsor) - Please note that this did not occur in Hamburg and was instead wrapped into the Poster reception. That would be an acceptable alternative.

• Poster reception

• Banquet dinner

• Travel, accommodation costs, and a small honorarium (usually about $1000) for keynote speakers

• Conference venue rental and associated costs (if not provided for by the host)

• Facilities rental and setup (AV equipment etc)

• Website costs (if not provided for by the host) - Please note that this may be managed by the Steering Committee in the future so costs for this should be tentative.

• Event recording/streaming costs

• Conference 'swag' including small printed programmes, badges, etc

• Transportation costs (if applicable, perhaps to/from banquet)

• Insurance costs (if applicable)

Elsewhere within the bid document, the following is appropriate:

• Brief details of other conferences that the team has organised

• Proposed dates for the conference (see below)

• Details about the campus and/or city hosting the conference (this may well be scans of an official brochure)

• Details of the hotels that are likely to be used by delegates with approximate costs and a statement that there will be sufficient accommodation available during the proposed dates (see below)

• Details of the conference venue (see below)

• Details of the workshops venue(s) if different (see below)

• Details of the proposed Host organizing committee

• Details of how the conference website would be maintained

• Details of how social media would be utilized

• Ability to provide visa letters to attendees as needed

• Evidence that the institution would be able to arrange travel for the fellowship recipients in case the recipients would not be able to do that themselves (this cost may be reimbursed to the institution or taken out of surplus costs)

The bid should not exceed 15 pages. Any further details can be provided in appendices if necessary.

These are not intended to be complete or exclusive lists and are offered only for guidance.

Dates and structure

The organizers should ensure that the dates they propose for the conference do not clash with any events that might potentially draw from the same pool of delegates (remembering that delegates come from a number of countries) and ideally do not include national holidays for any of the major countries represented by delegates.

From 2015, the Open Repositories event has spanned four days, Monday to Thursday, with the first day being given over to workshops.  The main conference has then typically filled 3 days. We no longer have a separate day for interest groups; these are instead integrated into the conference.

Hotels

The hotels recommended to delegates should be reasonably priced and be within comfortable walking distance of the conference venue. As they are attending a technology conference, delegates will expect that all rooms will have free internet.

In arranging discounted rates with local hotels, organisers of conferences should try to ensure that negotiated special rates include the Saturdays before and after the conference.  In particular, return flights from European destinations are generally much cheaper if the stay includes a Saturday night (transatlantic eg $1200 instead of $3000) but the "Saturday night rule" is evident in airfares elsewhere too.

The conference venue

The conference venue should have a single meeting space comfortably big enough to accommodate all the delegates during plenary sessions. It should have further rooms to accommodate parallel tracks when the conference splits into two or more strands (Hamburg had five parallel sessions; generally we are seeing about three to four).  The conference venue should have a large open area where delegates can gather for refreshments during breaks and in which sponsors and other organizations can have exhibition tables, with monitors etc. as necessary, for delegates to visit and browse. It is likely that this area will also be used for registration.

The venue will need a place that lunch can be efficiently provided for delegates since often the schedule only allows an hour for lunch; in the past this has sometimes been a dedicated dining room, but the open area described above has also been used successfully. If the open area is to be used, a reasonable amount of seating will be appreciated if possible.

It is essential that the venue have good wifi. Poor wifi is probably the biggest single source of complaints at OR conferences over the years. Organizers and venue staff should not underestimate the demands that 400+ technology-oriented delegates can make on a system, and standard conference venue wifi, particularly in hotels, may not be sufficient for a tech heavy conference without adding supplemental bandwidth and access points. The wifi should support VPN and IRC connections. In the past some venues have been able to provide for presenters cabled network connections with priority access to the system or a separate wifi network not available to delegates thus ensuring they could reliably give demonstrations.

The location of the poster reception should be discussed. There are clear advantages to having the posters in the conference venue (where they can be browsed at times other than the reception) but some organisers have placed them elsewhere so that the reception can be in a different (and usually impressive) location.

Workshops

Generally workshops are held the day prior to the conference start and are a combination of half and full day workshops. We have had as many as five to six parallel sessions of workshops. Organizers will need to use their local knowledge to decide where, and how many of these workshops can be managed. The total number of delegates attending such workshops will be somewhat lower than that attending the conference proper, and it may not make financial sense to use the main conference venue for them. Whatever venues are made available should have good wifi, projection facilities, and be close to places where attendees can get lunch. Ideally they will be close together and close to the main conference venue.

And if your bid is accepted?

If your bid is successful it will be important that you gather together a Host Organising Committee as soon as possible. In particular, the OR SC will want to know the name of its Chair as soon as possible so that (s)he can immediately become party to the wider planning process.The expectation is that the Chair of the HOC will begin to participate in calls as soon as selected since much can be learned from the planning of the previous years conference; however, regular participation is definitely expected from the call in July forward. The Chair will also be added to the appropriate email lists, and given access to the wiki and social media sites for publicizing the conference. We also hope that the Chair(s) can attend the conference immediately preceding their conference as there are at least two meetings (a debrief and a standing OR SC meeting) that are useful for knowledge exchange.

The Annual Cycle

(Starting in July or August after the annual OR conference)

The following covers the main points in the annual cycle of preparatory events.  Dates are approximate and may need to be varied depending on the actual timing of the coming OR event.  The timings given here would be for a conference to be held in June or July. It has been the practice in recent years to build extension dates into the planning for proposals. Thus the CfP will call for submissions by a certain date but then, inevitably, a one or two week extension will be offered.  Behind the scenes planning proceeds on the basis of this later date.

August

Appointment of Program Chairs - OR SC

During the summer preceding the conference, the OR SC will identify a Chair or Co-Chairs of the Program Committee. The Program Chairs are added to the Open Repositories Steering Committee for the duration of the relevant conference cycle.  They are not permanent members of the Committee and have no voting rights. Following the event and the immediate post-conference work they are removed from the Committee lists. There is no OR policy on whether the Program Chair and Host Organising Committee Chair should come from different institutions.

September

Appointment of Program Committee and Track Chairs - Program Chair(s)

The Chair(s) will appoint additional members to the Program Committee and together the group is responsible for soliciting and selecting content for the year's OR event.  Later in the year they will identify a team of reviewers to advise on the submissions that are made. Members of the program committee generally serve as Track Chairs. Tracks include Workshops, Posters, 24x7’s, and the Ideas Challenge. These Track Chairs work with the wider program committee but also take responsibility for their particular content block. In addition, the Chair(s) for the Idea Challenge manage that event for the conference.  Content that is proposed for one Track is often referred to and accepted in a different Track (i.e., a full paper proposal becomes a 24x7; a 24x7 might become a Poster) The Program Chairs, Track Chairs, and Program Committee will hold regular conference calls generally starting in the fall.

Set Theme for OR Conference - Program Chairs with approval from OR SC

Working with the OR SC and Chair(s) of the Host Organising Committee, the Program Chair(s) sets the theme for the conference.

Review Communication Processes - OR SC

The OR SC maintains a directory of listservs, groups, and social media venues to target. Each fall, the OR SC should review the directory for defunct lists/venues or potential new additions.

October

Conference website and social media - Host Organizing Committee

Ideally the conference website should be launched in October at the latest.  Social media provision should be made at the same time (identification of Twitter tag etc). The website should clearly signpost the OR "Code of Conduct" (see Appendices). At OR13, the Code was reproduced in the Conference Handbook; from OR2014 it appeared on the conference website as well as in the conference handbook.

Develop Sponsorship Campaign - Host Organizing Committee

Create a sponsorship brochure (based on the template) and web pages. Identify potential sponsors based on existing lists and local opportunities. Note that local hosts have license to shape the benefits sponsors receive at various levels; however this should largely be consistent with past practice, and done with an eye that many sponsors return year over year, and the whole community benefits from some consistency on this front. It is OR policy that sponsors do not receive preferential slotting in the program.

Finalize Call for Proposals - Program Committee with approval from OR SC

Ideally the Call for Proposals is released in November though this date has shifted over the last two ORs (2017 and 2018). A large part of the Program Committee work at this part of the cycle is determining what they want the skeleton of the program to look like: will there be Rants in the 24x7 presentation? How will you integrate platform specific conversations? What space is available for posters and workshops? All of these discussions shape what the CfP might look like, and the categories for the submissions.

The CfP should contain:

• The dates and venue of the conference

• The theme of the conference

• An invitation to submit a proposal for the various tracks.  It should be made very clear that proposals not accepted for one track may be pushed to another if appropriate.

• A clear indication of the form and quality of submission expected for each category (how many pages, etc).  The Program Committee may feel it appropriate to offer optional templates for guidance in each of the categories.

• The CfP should mention the Idea Challenge but this will be the subject of its own call in due course.

• Closing date for proposals.

• The CfP should contain the name(s) of the Program Committee Chair(s) as signatories.

• The CfP should reference the Code of Conduct.

• The CfP should include information about the Scholarship Program (see below)

Past CfPs are available elsewhere on this wiki and recent ones should be consulted. Please note that it should be possible to provide the Program Committee with statistics from the previous year(s) and the number of submissions in each category (paper, poster, 24/7 etc) and the numbers ultimately accepted.

Finalize Dates for the CfP, Acceptance, and Registration - Program Committee and Host Organizing Committee with approval from OR SC

The Program Committee in collaboration with the Host Organizing Committee should finalize the dates for submissions deadlines, reviewing process, decisions, schedule, and registration. It is customary to build in extension times for submissions into the deadlines. Also, the Program Committee and Host Organizing Committee will need to work closely together around the deadline for workshops. We have found it is best practice to have workshops reviewed and selected earlier so that they can be listed when registration opens. This allows the HOC to be able to make determinations about rooms or limits to registration if needed. A sample timeline might look like:

• Nov 15 - Call for Proposals opens

• Jan 5 - Published deadline for submissions

• Jan 13 - Actual deadline for submissions

• Feb 1 - Deadline for review of workshops

• Feb 13 - Deadline for review of all other proposals

• Feb 15 - Registration opens with accepted workshops and keynotes announced

• Mar 1 - Decisions sent to submitters

• Mar 15 - Schedule Available

• June - Conference

Details of Fellowships - Fellowship Subcommittee

Prior to the release of the CfP the Scholarships Subcommittee should decide how many scholarships to the year's OR will be offered so that a call for applications can accompany it.  An application form of some sort needs to be available. (For OR2014 this was a web form as part of the conference website. For OR2015 a Google form was trialled.) An appropriate page of information will be needed on the conference website. The deadline for applications should allow plenty of time for recipients to complete arrangements for additional funding, to get any necessary visas and to make travel arrangements.

Develop and Issue Call for Expressions of Interest (EoI) for future conference hosting - OR SC

The OR SC develops a Call for Expressions of Interest (EoI) for hosting the next conference yet to be selected (generally, OR Conferences are selected two years out). The EoI should include instructions and expectations for the Expression of Interest including a schedule for the next steps and a link to this document. This call should be distributed to appropriate communication channels. The OR SC should actively recruit potential hosts.

November

Call for Proposals Released - Program Committee with support from OR SC

The CfP should have a very broad distribution. The OR SC maintains a directory of listservs, groups, and social media venues to target.  The directory is in the form of a table so that lists can be checked off as they are notified to prevent or minimise duplication. Effort should also be given to finding extra mailing lists that are relevant to any theme the conference might have; these should also be targeted. Encourage recipients to rebroadcast the call to lists that seem to have been neglected.

Keynote Speakers Identified - Program Committee in collaboration with Host Organizing Committee with approval from OR SC

In general, the earlier that keynote speakers (generally for both opening and closing) are identified and secured the better particularly if the Program Committee is looking at high profile speakers. The Program Committee should work closely with the Host Organizing Committee on confirming the budget available for bringing the speakers to OR and for providing a small honorarium; it is not uncommon for OR to bring in international speakers so the budget should be able to account for that.

Launch Sponsorship Campaign - Host Organizing Committee

Once the CfP is released, a sponsorship campaign can also be launched (having the theme set within the CfP can make approaching potential sponsors easier). The Host Organizing Committee should consider previous sponsors as well as local contacts including local or regional universities and business.

December

Identify and Invite Reviewers - Program Committee

Reviewers should be identified and invited for the incoming proposals. The Program and Track Chairs should be able to call on the previous year's list as a starting point, and all members of the Steering Committee should be invited to contribute. In recent years, each proposal in the general paper track has been allocated three reviewers and each reviewer has been allocated four to six reviews.  This has been the subject of discussion as some reviewers felt that they did not get an adequate "feel" for the relative quality of submissions. Reviewers can be loaded into ConfTool and managed there.

Open ConfTool for Submissions - Host Organizing Committee

Ideally ConfTool (or whatever conference submission system is in use) will be open and ready when the CfP is released, but it is common to have it open a bit after the CfP.

Review submitted EoI’s - OR SC

The OR SC should review the submitted EoI’s in order to select candidates to invite to do a full bid. The criteria for selection may vary from year to year primarily because of geographic considerations. This can be done through a discussion on the monthly call or through an online vote. Successful EoI’s should be given at least six weeks to prepare a full bid.

January

Submission Closes and Reviews Begin - Program Committee

Once submissions close (usually with a week long extension from the original date), the program and track chairs should assign reviewers to each submission. Program chairs may decide what level of review different tracks get; for example, submissions to the general track may get three reviews but posters only two. This is up to the Program Committee. Make clear to reviewers what the deadline for reviews will be. In general, reviewers have been given about a month.

Workshops will need to have a faster track since it is important these are included in the registration process.

Venue Selected for Conference Events - Host Organizing Committee

Because the costs for the conference dinner and other venues for social events often figure substantially into the registration costs, these should be selected and budgeted for well prior to the opening of registration. We recommend that the HOC use https://www.diglib.org/dlf-events/dlf-social-event-checklist/ as a set of guidelines for social events; in particular pay close attention to accessibility, a range of food options, and availability of non-alcoholic drinks at all events.

February

Select Workshops - Program Committee with Host Organizing Committee

Because there are often a limited number of rooms for workshops and a limited number of slots available, it is useful to include a workshop selection step in the registration process. This means that workshops have to be reviewed and selected earlier than the remainder of the papers. Arrange with successful workshop organisers to get appropriate details for the descriptive page if that was not included in the submission.

Selected workshops should then be passed on to the Host Organizing Committee to include in the registration process.

Registration opens - Host Organizing Committee

Once workshops have been selected, the Host Organizing Committee should open registration. It will be important to have other logistics such as hotel blocks and travel recommendations set up prior to opening registration since many people may make all of these arrangements at the same time.

In the past, two registration fees have generally been offered - an "early bird" fee, with an associated deadline, and a higher fee for later bookings. It is up to the Host Organizing Committee how they might want to manage the registration fees, including early bird or student fees. In addition, some Hosts have separated the cost of the conference dinner from the registration fee in order to better understand how many people will attend the dinner. There are pros and cons to having a separate cost for the dinner, and the Host Organizing Committee is welcome to speak to the OR SC about this and how this has been managed in the past.

The website booking process must use https.

The registration form should have a checkbox "I agree to be contacted about future OR conferences". Names and email addresses of registrants who mark "yes" will be forwarded to the OR SC after the conference to be added to the open-repositories Google group.

March

Develop Rough Schedule for Program - Program Committee and Host Organizing Committee

It is useful to rough out a program schedule while reviews are being completed so that the Program Committee has a clear sense of how many submissions can be accepted in each track. This will require working with the Host Organizing Committee to understand number of simultaneous tracks that are possible, space for the poster session, etc. Also, the Program Chairs should understand how much time will need to be blocked out for the opening session and keynote, the Ideas Challenge, and the closing session and keynote (the three standard plenary sessions for OR).

Reviews complete, submissions selected, and notifications issued - Program Committee

Elements of the Bid

The ORSC has provided a OpenRepositories Detailed Bid template that can be used to provide the expected information in a bid. The bid should not exceed 15 pages. Any further details can be provided in appendices if necessary. The following are not intended to be complete or exclusive lists.

Narrative Elements

• Dates

The organizers should ensure that the dates they propose for the conference do not clash with any events that might potentially draw from the same pool of attendees (remembering that attendees come from a number of countries) and ideally do not include national holidays for any of the major countries represented by attendees.

From 2015, the Open Repositories event has spanned four days, Monday to Thursday, with the first day being given over to workshops. The main conference has then typically filled 3 days. We no longer have a separate day for interest groups; these are instead integrated into the conference.

• Expected number of attendees

Using previous OR conferences as a guide, estimate your target number of attendees.

• The conference venue

The conference venue should have a single meeting space comfortably big enough to accommodate all the attendees during plenary sessions. It should have further rooms to accommodate parallel tracks when the conference splits into two or more strands (Hamburg in 2019 had five parallel sessions; generally we are seeing about three to four). The conference venue should have a large open area where attendees can gather for refreshments during breaks and in which sponsors and other organizations can have exhibition tables, with monitors etc. as necessary, for attendees to visit and browse. It is likely that this area will also be used for registration.

The venue will need a place where lunch (and potentially breakfast) can be efficiently provided for attendees; in the past this has sometimes been a dedicated dining room, but the open area described above has also been used successfully. If the open area is to be used, a reasonable amount of seating is needed. Be aware that the lunch slot in the conference schedule is sometimes only an hour and so needs to be as efficient as possible.

It is essential that the venue has good wifi. Poor wifi is probably the biggest single source of complaints at OR conferences over the years. Organizers and venue staff should not underestimate the demands that 400+ technology-oriented attendees can make on a system, and standard conference venue wifi, particularly in hotels, may not be sufficient for a tech heavy conference without adding supplemental bandwidth and access points. The wifi should support VPN and IRC connections. In the past some venues have been able to provide for presenters cabled network connections with priority access to the system or a separate wifi network not available to attendees thus ensuring they could reliably give demonstrations.

The conference venue should be accessible. See https://www.sigaccess.org/welcome-to-sigaccess/resources/accessible-conference-guide/ for more information on providing an accessible venue.

The location of the poster display and reception should be discussed. There are clear advantages to having the posters in the conference venue (where they can be browsed at times other than the reception) but some organizers have placed them elsewhere so that the reception can be in a different location.

• Workshop venue and management

Generally workshops are held the day prior to the conference start and are a combination of half and full day workshops. We have had as many as five to six parallel sessions of workshops. Organizers will need to use their local knowledge to decide where, and how many of these workshops can be managed. The total number of attendees attending such workshops will be somewhat lower than that attending the conference proper, and it may not make financial sense to use the main conference venue for them. Whatever venues are made available should have good wifi, projection facilities, and be close to places where attendees can get lunch or be catered. Ideally they will be close together and close to the main conference venue (or within easy public transit reach).

• Accommodations

Accommodations recommended to attendees should be reasonably priced and be within comfortable walking distance of the conference venue. As they are attending a technology conference, attendees will expect that all rooms will have free internet. If a room block is expected to be required as part of the venue negotiations, please mention here; we strongly recommend that any room block is required that it be as small as possible.

• Social Events

Provide potential venues for the conference dinner and poster reception (if not held at conference venue).

• Larger environment

Describe the area where the conference will be held. Why would this location be appealing for people around the world to travel to? You may include as an appendix an official brochure.

• Host Organization experience

Please include information about the host organization’s experience with hosting previous conferences. Also include who is likely to be chairing the OR HOC and who might be members.

• Communication and marketing

The ORSC will provide a website, Twitter account, and Facebook account, but the OR HOC has primary responsibility for managing these during the lead up and during the conference. In addition, the Host will be expected to contract for and manage the registration site (such as EventBrite) and mobile schedule (such as Sched). Please describe your experience managing both websites and social media accounts.

• Sponsorship

Please describe your experience with and approach to securing sponsors for conferences or other events.

• Miscellaneous Items

ORSC relies on Host Organizations to be able to do some things that come with holding an international conference. For example, we sometimes will need a Host to provide visa letters to attendees or to arrange travel for fellowship recipients (this cost would be either reimbursed by the ORSC or taken out of the conference surplus).

• Contingency Plans

Please describe your ability to manage contingencies if the environment rapidly changes (for example, switching to an online conference or moving the conference forward a year if necessary). If your organization would require event insurance, please describe that here.

Financial Elements

The ORSC anticipates that the financial element of a bid will be supplied as an Excel spreadsheet or using the table in the Detailed Bid template. It should cover the costs of all aspects of the conference that will require funding. It should include a reasonable estimate of income from sponsorship (based on previous years' actual figures), and it should break even based on a realistic but conservative estimate of attendance. It is the responsibility of bidding institutions to consider past bids in detail and come up with their own itemized list, but it should include the following:

Costs to the hosting institution:

1. Conference venue rental costs: This should include space for both the main conference and the workshops (these are often in separate spaces). For workshops, it can be useful to budget for some supplies such as easels, pads, and markers. If using a hotel and a room block is required, please include information about the costs if the room block was not met.
2. Catering Costs: Generally this means at the least coffee in the morning and at the mid-morning break, lunch, and a refreshment break in the afternoon. Depending on the venue and the accommodations, some conferences also provide a hot breakfast. A range of options should be provided including vegan and vegetarian options.
3. Social Event Costs: Two evening events (on other evenings attendees make their own arrangements) - see https://www.diglib.org/dlf-events/dlf-social-event-checklist/ for a useful set of guidelines on social events.
   1. Poster reception: Generally drinks and appetizers on the evening of the first day of the conference (not the workshop day). This is sometimes in a different venue than the main conference but often is in the same location.
   2. Banquet dinner: Generally at a venue different from the main conference. Include costs for rental and transportation costs if needed. Some hosts have itemized the dinner as a separate cost for participants.
4. Keynote Speakers: OR generally has two keynote speakers and provides an honorarium to each (usually around $1000) as well as travel, accommodation, and per diem.
5. Mobile and Registration Platforms: While the ORSC provides the primary conference website as well as the conference submission tool (ConfTool), the hosts will need to provide a registration platform as well as a mobile site such as Sched.
6. Event recording and streaming costs: ORSC expects a limited number of sessions (keynotes, plenary sessions) to be recorded and live streamed, but not the entire conference.
7. Bandwidth and wireless costs, if needed: OR attendees often are using several devices to connect to the internet; securing adequate bandwidth is critical to the success of the conference.
8. Conference swag and supporting material: While interest in ‘swag’ has declined over the past few years because of sustainability concerns, small printed programs, badges, and lanyards are generally useful to have.
9. Event Insurance, if needed: It may be useful to purchase event insurance to protect your financial outlay (in some cases, parent institutions may require it).
10. Other: Any other costs associated with the conference. For example, some host institutions have hired a conference organizer.

Income:

1. Registrations: Registration should cover the costs of the conference to the hosting institution once sponsorships and any other income are subtracted. The ORSC does not expect large profits and would rather see the cost to attendees kept as low as possible without the hosting institution suffering a loss. 
2. Sponsorships: Estimate the amount that you expect from sponsors in order to offset costs.
3. Other income: Any other income that will offset the costs of the conference.

Costs per attendees:

1. Travel costs: Include approximate costs for attendees including costs for international attendees. If additional costs are involved to travel from the airport to accommodations, please include those.
2. Accommodation: Include approximate costs for a range of accommodations for attendees. If reserving a hotel block, indicate the cost per room. 
3. Per diem: Include approximate costs for per diem.
1.  If helpful, the United States Department of State publishes per diem rates for foreign cities: https://aoprals.state.gov/Web920/per_diem.asp. See the cost of meals and incidental expenses rate (M&I) as an estimate, while noting that the conference should be providing some meals). 
4. Registration: Please include the estimated registration cost per attendee.

Review process

Submitted bids will be reviewed carefully for the criteria required with close attention to the budget, logistics, and experience. The criteria for selection may vary from year to year primarily because of geographic considerations. In areas that need further clarification, the ORSC will seek clarity from the bidder. The successful and unsuccessful bidders are notified usually within two months. In general, the ORSC aims to select a bid in time to make an announcement at the conference; when this is not possible, we try to make an announcement no later than the end of the summer.

And if your bid is accepted?

If your bid is successful it will be important that you gather together a OR HOC as soon as possible. In particular, the ORSC will want to know the name of its Chair as soon as possible so that they can immediately become party to the wider planning process.The expectation is that the Chair of the OR HOC will begin to participate in calls as soon as selected since much can be learned from the planning of the previous years conference. Regular participation is definitely expected from July forward the year before the conference will be hosted. The Chair will also be added to the appropriate email lists, and given access to the wiki and social media sites for publicizing the conference. We also hope that the Chair(s) can attend the conference immediately preceding their conference as there are at least two meetings (a debrief and a standing ORSC meeting) that are useful for knowledge exchange, and it is a tradition that the Chairs or their representative give a brief presentation on next year’s conference in the closing plenary session.

The Annual Cycle

(Starting in July or August after the annual OR conference)

The following covers the main points in the annual cycle of preparatory events.  Dates are approximate and may need to be varied depending on the actual timing of the coming OR event.  The timings given here would be for a conference to be held in June or July. It has been the practice in recent years to build extension dates into the planning for proposals. Thus the CfP will call for submissions by a certain date but then, inevitably, a one or two week extension will be offered.  Behind the scenes planning proceeds on the basis of this later date.

See Appendix D for a visual overview of the annual cycle. 

August

Appointment of Program Chairs - ORSC

During the summer preceding the conference, the ORSC will identify Co-Chairs of theOR PC. The Program Chairs are added to the ORSC for the duration of the relevant conference cycle.  They are not permanent members of the ORSC and have no voting rights. Following the event and the immediate post-conference work they are removed from the ORSC lists. There is no OR policy on whether the Program Chairs and Host Chairs should come from different institutions.

September

Appointment of Program Committee and Track Chairs - Program Chairs

The Chairs will appoint additional members to the OR PC and together the group is responsible for soliciting and selecting content for the year's OR event.  Later in the year they will identify a team of reviewers to advise on the submissions that are made. Members of the OR PC generally serve as Track Chairs. Tracks include Workshops, Posters, 24x7’s, and the Ideas Challenge. The Chairs serve as the chairs for the General Track. These Track Chairs work with the wider OR PC but also take responsibility for their particular content block. In addition, the Chairs for the Idea Challenge manage that event for the conference.  Content that is proposed for one Track is often referred to and accepted in a different Track (i.e., a full paper proposal becomes a 24x7; a 24x7 might become a Poster) The Program Chairs, Track Chairs, and OR PC will hold regular conference calls generally starting in September/October.

Set Theme for OR Conference - Program Chairs with approval from ORSC

Working with the ORSC and Chairs of the OR HOC, the Program Chairs set the theme for the conference and begin to consider potential keynotes that could address the theme.

Review Communication Processes - ORSC

The ORSC maintains a directory of listservs, groups, and social media venues to target. Each September, the ORSC should review the directory for defunct lists/venues or potential new additions.

October

Conference website and social media - Host Organizing Committee

Ideally the conference website should be launched in October at the latest.  Social media provision should be made at the same time (identification of Twitter tag etc). The website should clearly signpost the OR "Code of Conduct" (see Appendices).

Develop Sponsorship Campaign - Host Organizing Committee

Create a sponsorship brochure and web pages. Identify potential sponsors based on existing lists and local opportunities. Note that local hosts have license to shape the benefits sponsors receive at various levels; however this should largely be consistent with past practice, and done with an eye that many sponsors return year over year, and the whole community benefits from some consistency on this front. It is OR policy that sponsors do not receive preferential slotting in the program.

Finalize Call for Proposals - Program Committee with approval from ORSC

Ideally the Call for Proposals is released in November. A large part of the OR PC work at this part of the cycle is determining what they want the skeleton of the program to look like: How will you integrate platform specific conversations? What space is available for posters and workshops? All of these discussions shape what the CfP might look like, and the categories for the submissions.

The CfP should contain:

• The dates and venue of the conference
• The theme of the conference
• An invitation to submit a proposal for the various tracks.  It should be made very clear that proposals not accepted for one track may be pushed to another if appropriate.
• A clear indication of the form and quality of submission expected for each category (how many pages, etc).  The OR PC may feel it appropriate to offer optional templates for guidance in each of the categories.
• The CfP should mention the Idea Challenge but this will be the subject of its own call in due course.
• Closing date for proposals.
• The CfP should contain the name(s) of the Program Chairs as signatories.
• The CfP should reference the Code of Conduct.
• The CfP should include information about the Fellowship Program (see below)

Past CfPs are available elsewhere on this wiki and recent ones should be consulted. Please note that it should be possible to provide the OR PC with statistics from the previous year(s) and the number of submissions in each category (paper, poster, 24/7 etc) and the numbers ultimately accepted.

Finalize Dates for the CfP, Acceptance, and Registration - Program Committee and Host Organizing Committee with approval from ORSC

The OR PC, in collaboration with the OR HOC, should finalize the dates for submissions deadlines, reviewing process, decisions, schedule, and registration. It is customary to build in extension times for submissions into the deadlines. Also, the OR PC and OR HOC will need to work closely together around the deadline for workshops. We have found it is best practice to have workshops reviewed and selected earlier so that they can be listed when registration opens. This allows the OR HOC to be able to make determinations about rooms or limits to registration if needed. A sample timeline might look like:

• Nov 15 - Call for Proposals opens
• Jan 5 - Published deadline for submissions
• Jan 13 - Actual deadline for submissions
• Feb 1 - Deadline for review of workshops
• Feb 7 - Decisions sent to workshop submitters for confirmation of participation
• Feb 13 - Deadline for review of all other proposals
• Feb 15 - Registration opens with accepted workshops and keynotes announced
• Mar 1 - Decisions sent to submitters
• Mar 15 - Schedule Available
• June - Conference

Details of Fellowships - Fellowship Subcommittee

Prior to the release of the CfP the Fellowships Subcommittee should decide how many fellowships to the year's OR will be offered so that a call for applications can accompany it.  An application form of some sort needs to be available. (Recently a Google form has been used.) An appropriate page of information will be needed on the conference website. The deadline for applications should allow plenty of time for recipients to complete arrangements for additional funding, to get any necessary visas and to make travel arrangements.

Develop and Issue Call for Expressions of Interest for future conference hosting - ORSC

The ORSC develops a Call for Expressions of Interest (EoI) for hosting the next conference yet to be selected (generally, OR Conferences are selected two years out). The EoI call should include instructions and expectations for the EoI including a schedule for the next steps and a link to this document. This call should be distributed to appropriate communication channels. The ORSC should actively recruit potential hosts.

November

Call for Proposals and Fellowship Call Released - Program Committee with support from ORSC

The CfP should have a very broad distribution. The ORSC maintains a directory of listservs, groups, and social media venues to target. The directory is in the form of a table so that lists can be checked off as they are notified to prevent or minimize duplication. Effort should also be given to finding extra mailing lists that are relevant to any theme the conference might have and geographic location; these should also be targeted. Encourage recipients to rebroadcast the call to lists that seem to have been neglected.

Keynote Speakers Identified - Program Committee in collaboration with Host Organizing Committee with approval from ORSC

In general, the earlier that keynote speakers (generally for both opening and closing) are identified and secured the better particularly if the OR PC is looking at high profile speakers. The OR PC should work closely with the OR HOC on confirming the budget available for bringing the speakers to OR and for providing a small honorarium; it is not uncommon for OR to bring in international speakers so the budget should be able to account for that.

Launch Sponsorship Campaign - Host Organizing Committee

Once the CfP is released, a sponsorship campaign can also be launched (having the theme set within the CfP can make approaching potential sponsors easier). The OR HOC should consider previous sponsors as well as local contacts including local or regional universities and business.

December

Identify and Invite Reviewers - Program Committee

Reviewers should be identified and invited for the incoming proposals. The Program and Track Chairs should be able to call on the previous year's list as a starting point, and all members of the ORSC should be invited to contribute. In recent years, each proposal in the general paper track has been allocated three reviewers and each reviewer has been allocated four to six reviews. Reviewers can be loaded into ConfTool and managed there.

Open ConfTool for Submissions - ORSC

Ideally ConfTool (or whatever conference submission system is in use) will be open and ready when the CfP is released, but it is common to have it open a bit after the CfP.

Review submitted EoIs - ORSC

The ORSC should review the submitted EoIs in order to select candidates to invite to do a full bid. The criteria for selection may vary from year to year primarily because of geographic considerations. This can be done through a discussion on the monthly call or through an online vote. Successful EoIs should be given at least six weeks to prepare a full bid.

January

Submission Closes and Reviews Begin - Program Committee

Once submissions close (usually with a week-long extension from the original date), the Program and Track chairs should assign reviewers to each submission. Program Chairs may decide what level of review different tracks get; for example, submissions to the general track may get three reviews but posters only two. This is up to the OR PC. Make clear to reviewers what the deadline for reviews will be. In general, reviewers have been given about a month.

Workshops will need to have a faster track since it is important these are included in the registration process, therefore reviews for these are often distributed amongst the ORSC, OR PC, and OR HOC for timeliness.

Venue Selected for Conference Events - Host Organizing Committee

Because the costs for the conference dinner and other venues for social events often figure substantially into the registration costs, these should be selected and budgeted for well prior to the opening of registration. We recommend that the OR HOC use https://www.diglib.org/dlf-events/dlf-social-event-checklist/ as a set of guidelines for social events; in particular pay close attention to accessibility, a range of food options, and availability of non-alcoholic drinks at all events.

February

Select Workshops - Program Committee with Host Organizing Committee

Because there are often a limited number of rooms for workshops and a limited number of slots available, it is useful to include a workshop selection step in the registration process. This means that workshops have to be reviewed and selected earlier than the remainder of the papers. Arrange with successful workshop organizers to get appropriate details for the descriptive page if that was not included in the submission.

Selected workshops should then be passed on to the OR HOC to include in the registration process.

Select Fellowship Recipients - Subcommittee of the Open Repositories Steering Committee

The subcommittee for OR Fellowships should be ready to contact the fellowship recipients by the time Registration opens. This also allows time for recipients to make appropriate travel plans, apply for visas, etc. The Host Organizing Institution may need to provide additional support in the form of purchasing plane tickets, making hotel reservations, and supplying any documentation for visas.

Registration opens - Host Organizing Committee

Once workshops have been selected, the OR HOC should open registration. It will be important to have other logistics such as hotel blocks and travel recommendations set up prior to opening registration since many people may make all of these arrangements at the same time.

In the past, two registration fees have generally been offered - an "early bird" fee, with an associated deadline, and a higher fee for later bookings. It is up to the OR HOC how they might want to manage the registration fees, including early bird or student fees. In addition, some Hosts have separated the cost of the conference dinner from the registration fee in order to better understand how many people will attend the dinner. There are pros and cons to having a separate cost for the dinner, and the OR HOC is welcome to speak to the ORSC about this and how this has been managed in the past.

The website booking process must use https.

The registration form should have a checkbox "I agree to be contacted about future OR conferences''. Names and email addresses of registrants who mark "yes" will be forwarded to the ORSC after the conference to be added to the open-repositories Google group.

March

Develop Rough Schedule for Program - Program Committee and Host Organizing Committee

It is useful to rough out a program schedule while reviews are being completed so that the OR PC has a clear sense of how many submissions can be accepted in each track. This will require working with the OR HOC to understand the number of simultaneous tracks that are possible, space for the poster session, etc. Also, the Program Chairs should understand how much time will need to be blocked out for the opening session and keynote, the Ideas Challenge, and the closing session and keynote (the three standard plenary sessions for OR).

Reviews complete, submissions selected, and notifications issued - Program Committee

Once reviews are complete, the OR PC works to identify which submissions should be accepted Once reviews are complete, the Program Committee works to identify which submissions should be accepted into the program, which submissions might be designated to a different track from the original submission (for example, a paper might be accepted as a poster), and which should be rejected. Often the Track Chairs can make the acceptance decisions within their tracks and will bring edge cases to the broader Program CommitteeOR PC. The Program Chairs have final authority over acceptances and rejections. Once these are finalized, notifications should be sent using ConfTool. The Program Committee OR PC should allow time to hear back from submitters whose submissions were designated to a different track whether they accept the track change.

Permissions to Record - Program Committee

If any sessions, including the keynotes, are going to be recorded and posted in the OR YouTube Channel, the program committee should collect the appropriate permissions from speakers.

Program Schedule Complete - Program Committee

Now that the decisions about content have been made, attention should be turned to fleshing out the detail details of the program schedule. This should be posted on the website as soon as practical.. Early information about the conference structure and content may be essential to potential attendees seeking funding from their institution. A six week lead time or better is desirable.

Once the timetable is published, an email should be sent to the lists advertising the fact and encouraging people to register. If not already done, now is a good time to identify and recruit session chairs for the conference.

Arrangements Made for

...

Fellowship Awardees - Host Organizing Committee and

...

Fellowship Subcommittee

Once registration opens and scholarship fellowship recipients have been selected, arrangements should be made for the free registrations, and, for the fellowship awardee, travel arrangements. This is particularly critical if the awardees have to apply for visas to attend the conference.

Selection of Full Bid for Conference Hosting - OR SCORSC

Once all bids have been submitted, the OR SC ORSC should review each bid carefully for the criteria required (see above) with close attention to the budget, logistics, and experience. In areas that need further clarification, the OR SC ORSC should seek clarity from the bidder. Once the OR SC ORSC has satisfied their questions on the bids, they should vote on which bid should be awarded the conference. The successful and unsuccessful bids should be notified. The successful bid should be given time to prepare a “Save this Date” website before a public announcement is made. However, it is critical to make the Save the Date announcement as soon as possible ideally in time for this year’s conference so that those dates are on people’s calendars, and other conferences are planned around them. All bids should be saved in the knowledge-base.

April

Prepping of Keynote Speakers - Program Committee

It is important that the Program Chairs schedule a call with the keynote speakers (either separately or together) to check in about logistics, needs for their presentations, and to spend a little time orienting them to the Open Repositories OR community and its general ethos. This is to ensure that the keynote speakers pitch their talks to the right audience.

Management and Planning of the Ideas Challenge - Program Committee

Much of the work around the Ideas Challenge happens at the conference. However, planning should start early. Considerations include whether there is a theme for the Challenge or if sponsorship is sought for the reception (if any) or for prizes. The success of the Ideas Challenge is often dependent on an enthusiastic and appealing campaign just prior to and during the conference; it is important to gather a group who can carry that campaign forward.

May

Planning for Opening and Closing Sessions - Program Committee, Host Organizing Committee, and

...

ORSC Chairs

The opening session generally contain quite a few segments including (but not limited to and not in any particular order):

a
• A welcome from the
OR SC
• ORSC Chair, the Host, and the Program Chairs;
a
• A welcome from someone such as a Provost or University Librarian at the Host Institution,
a
• A review of the Code of Conduct;
an
• An introduction of the
Program Committee, Host Organizing Committee
• OR PC, OR HOC, and the
Steering Committee
• ORSC;
an
• An overview of the number of submissions to the program and acceptances;
• An overview of the demographics of the registrants;
• Introduction to fellowship recipients;
• Thanks to sponsors;
• Substantial changes to the program (for example, new tracks or changes to tracks);
• Ideas Challenge;
• Introduction of the keynote speaker; and
• The keynote itself and questions.

This needs to be well planned in order to not go over the time allotted to the session and allow sufficient time for the keynote speaker. The Program Chairs should clearly communicate to the keynote speaker the time allotted to them.

The closing session also contains a number of segments including (but not limited to and not in any particular order):

• The introduction of the keynote speaker;
• The keynote itself and questions;
• Award of prizes for the best poster (if offered);
• Award of prizes for the Ideas Challenge;
• Thanks to sponsors;
• Introduction of the next OR location (usually done by the Host
Organizing Committee
• Chairs or their representatives of the next year's conference);
• Closing comments from the various chairs; and
• Thanks to key parties.

Similarly this session will need to be well timed so that the conference ends on time.

Preparation for Conference - Host Organizing Committee and Program Committee

The OR HOC should prepare the program for printing and for online. Please note that there was a mixed reaction to an online only program used in a recent OR. Prepare inclusion of sponsorship materials in conference packs, etc. if necessary.  An   An app like Sched can be a useful way to provide an online and social experience for the conference.

It is important that provision be made for collecting conference presentations in a digital form to add to the conference web site (and eventually, a repository of all OR presentations).  In , YouTube, and Zenodo repository).  In the past, session Chairs have sometimes been asked to collect these from their group. However it is done, an effort should be made to get as many as possible: they form a valuable resource.

The Host Organizing Committee OR HOC should be ensuring that all speakers are registered so that any potential gaps in the program are identified very early on.

Typically there can be a lot of sponsor management during this period particularly if there will be exhibit spaces for sponsors.

Members of the Host Organizing Committee, Program Committee, OR SCOR HOC, OR PC, ORSC, and those who will be staffing the conference should be familiar with the Code of Conduct, Anti-Harassment Policy, and the protocol for managing reports of violations.

June

Hold Conference - Program Committee, Host Organizing Committee, and OR SCORSC

All groups should be prepared for last minute hiccups during the conference and have clear communication channels for these/ . Slack is often used to communicate during the conference for this purpose.

Debrief Meeting - Program Committee, Host Organizing Committee, and OR SCORSC

Generally the lunch immediately following the closing keynote is dedicated to a debrief amongst all of the organizers on lessons learned. This also includes the chair(s) Chairs of the following year’s host organizing committeeOR HOC. A conference call with a de-brief as the main agenda topic should be arranged with organizers soon after the conference ends if a face-to-face meeting cannot be scheduled.

...

Attendee Survey - Host Organizing Committee with input from the

...

ORSC

The OR HOC should distribute a survey electronically to all delegates attendees at conference close. The questions should be based on previous years’ surveys (for trending) as well as feature any new questions relevant to that event. The returns from the delegate attendee survey should be collated and sent to the OR SC ORSC within a month of the conference close so that the information derived from the returns can be used to influence the way that the next conference is organisedorganized. The OR SC ORSC can provide the previous year’s survey.

July

Website Wrap-Up - Host Organizing Committee

Rather than let the conference website go moribund, it is appreciated if it can be updated post-conference to reflect some of the highlights and trivia from the event and to add presentations (or links to presentations in a repository) from the program.

Also, past conference website websites have been archived in the Internet Archive; once the website is finalized (including with links to presentations), work with the OR SC ORSC to get this added via an Archive It account or the IA's general crawl.

Content - Host Organizing Committee and Program Committee

Presenters should have provided session Chairs (or otherwise supplied) an electronic version of their presentation.  These   These need to be collated and stored safely. Some organisers organizers have retrospectively linked them from the website's conference programme. At the time of writing, the Steering Committee is looking for a way to host these materials centrally year-on-year.

Social Media Accounts - Host Organizing Committee with ORSC

program. All presentations are deposited into the OR Zenodo repository: https://zenodo.org/communities/openrepos.

Social Media Accounts - Host Organizing Committee with ORSC

At the end of the At the end of the conference, social media accounts (Twitter and Facebook) should be passed off to the next Host Organizing CommitteeOR HOC.

Accounting - Host Organizing Committee with OR Finance Subcommittee and CLIR

In due course, the OR SC ORSC will expect a set of summary accounting reports for the conference, preferably under the same headings as were used in the initial bid.  This   This will allow easy comparison of the two. The total sponsorship sponsorship income should be specifically shown in the final accounts. If, as is usual, the conference made a small profit when everything is taken into account, the organizers will need to agree with OR SC ORSC how and when to transfer the surplus into the OR contingency fund.

Knowledge-base - Host Organizing Committee and Program Committee

As soon as practical following the conference, the knowledge-base in the wiki needs updating with the conference documents for the information of subsequent organizers and potential organizers.  In   In practice, many of these documents may have been added "along the way" but now will be a good time to check that everything is there. If Google docs or other tools were used outside the wiki, download and transfer the required information to the wiki; if there is additional information that may be useful, add those as well. Documents to be included in the knowledge base can be found in Appendix DE.

Review Steering Committee Membership -

...

ORSC

In the month after the conference, the permanent members of the SC ORSC should review the membership. Membership is generally kept at 1412-16 permanent 13 standing members with an addition of the Program and Host Committee Chairs rotating on and off each year. The current membership policy can be found at: https://wiki.duraspacelyrasis.org/display/or11/Membership+Policy+2015.

Appendix A: Open Repositories Code of Conduct

Please see Open Repositories Code of Conduct.

Appendix B: Open Repositories Anti-Harassment Policy

Please see Open Repositories Anti-Harassment Policy.

Appendix C: Open Repositories Anti-Harassment Protocol

Please see Open Repositories Anti-Harassment Protocol.

...

/display/or11/Membership+Policy.

Appendix A: Open Repositories Code of Conduct

Please see Open Repositories Code of Conduct.

Appendix B: Open Repositories Anti-Harassment Policy

Please see Open Repositories Anti-Harassment Policy.

Appendix C: Open Repositories Anti-Harassment Protocol

Please see Open Repositories Anti-Harassment Protocol.

Appendix D: Visual of Annual Cycle

Appendix E: What to include in the knowledge-

...

base for each conference

Each conference will have different methods for managing documents and data related to a conference. They may use a combination of Google Drive, ConfTool, and other collaboration tools. The OR SC ORSC does not dictate what tools are used in the process of managing a conference; however, the OR SC ORSC does request that certain data and documents are preserved in the Duraspace LYRASIS hosted wiki so that future organizers can refer to these.

The conference website should be submitted to the Internet Archive for web archiving.

The data to be captured includes:

• Number of submissions total and broken down by track
• Number of acceptances total and broken down by track
• Number of registrations
• Timeline of registrations (if possible); breakdown of early vs late registrations
• Number of attendees broken down by country
• Number of attendees from
US
• USA broken down by state
• Number of attendees for the workshops
• Number of reviewers we ask to review / number who actually review
• Number of scholarships and fellowships given by country; names of recipients
• Number of submissions to idea challenge
• Twitter feed

The documents to be captured are:

• Copy of the successful bid;
• Copies of both the proposed budget (from the bid) and the actual post-conference record of expenditure;
• Overall schedule including when the CfP was released, extension dates, closing date, review period, registration opening, registration deadlines, program announced, conference dates;
• Call for proposals;
• Communications related to the registration opening, program announcements, etc.;
• List of proposed keynote speakers and invited keynote speakers;
• Conftool (or other system) email templates;
• Venue information including number and size of rooms and any issues with rooms;
• Number of code of conduct violations and type of issue (no personal information);
• Copy of the full program and schedule;
• Sponsorship prospectus;
• Overview of potential sponsors contacted including successful and negative responses. Ideally the levels of sponsorship selected and amounts received will be shown;
• Report of results from the conference assessment survey; and
• Lessons learned for both the host and program committees.

In addition, the website should be submitted to the Wayback Machine.

Appendix

...

F: Data Policies and Guidelines

Please see the OR Privacy Policy

Appendix

...

G: Statement on Inclusion and Openness

Please see see OR Statement on Inclusion and Openness

Appendix H: Guidance for Session Chairs

Please see Session chair guidelines