=========================================== Administrator's Reference =========================================== .. toctree:: :maxdepth: 3 :caption: Contents: This page has views and emails used by the administrator. Note some of the views may not be visible to you, depending on your privilege setting. .. _clients-view: Clients View ------------------- A :term:`client` can either be a :term`contract race` race director or a :term:`signature race` sponsor. .. _create-client-view: Create Client view ====================== .. image:: images/create-client-view.* .. _event-management: Contract Race Management ------------------------------ .. _admin-calendar-view: Race Calendar view ============================= **Navigation:** Contract Races > Race Calendar The main administrative interface is a calendar of the :term:`contract races ` in the database. The administrator can create a new :term:`contract race`, or select a :term`contract race` for Edit, or Delete operations. To create a new :term:`contract race`, click on a date. To edit a :term`contract race`, click on the contract race. .. image:: images/admin-calendar.* The colors for the days and contract races help the administrator understand the state of the :term:`contract race`, whether finish line :term:`services ` are required, or if this :term:`contract race` just has premium promotion :term:`service`. .. image:: images/admin-calendar-legend.* :align: center .. _event-overview-view: Race Table view =================== **Navigation:** Contract Races > Race Table While the :ref:`admin-calendar-view` may be the easiest way to view all the :term:`contract races `, this view provides a table of all the contract races in the database which can be used as well. The admin can create a new :term:`contract race`, or select a :term`contract race` for Edit or Delete operations. Notice the :term:`State` column. The :term:`State` may be updated automatically by the tool or the admin can update it through the administrative interface. See :term:`state` for a description of the states and whether they are set by the tool or by the administrator. Clicking the buttons at the top will take you to specific views or perform some action. :New: takes you to :ref:`create-event-view` :Edit: (requires single selection) takes you to :ref:`edit-event-view` :CSV: download a csv file of the currently filtered contract races. **Note** only the displayed contract races will be downloaded, so if there are multiple pages of contract races, some may be missing. :Calendar: switch to the :ref:`admin-calendar-view` The top row of controls provides a way to filter the table display down to only show the contract races which are in a particular :term:`State`, within a Date Range, or which has contracted for specific :term:`Services `. .. image:: images/event-overview.* .. _create-event-view: Create Contract Race view ============================ The Create Contract Race view is one way a race entry is created in the tool. Generally, this is used when a request is received for a new race. See :ref:`post-event-processing` for details on how existing races are automatically “renewed” for the following year. Notice the :term:`State` field. The :term:`State` may be updated automatically by the tool or the admin can update it through the administrative interface. See :term:`state` for a description of the states and whether they are set by the tool or by the administrator. When selecting **Race**, **Course**, or **Client**, a search box is displayed. You can start typing to find these items if they were previously stored. If a new :term:`race`, :term:`course`, or :term:`client` is needed, click on the ** entry and the :ref:`create-race-view`, :ref:`create-course-view`, or :ref:`create-client-view`, respectively, will be displayed so the item can be created. .. image:: images/create-event-view.* .. _create-race-view: Create Race view ================== .. image:: images/create-race-view.* .. _create-course-view: Create Course view =================== .. image:: images/create-course-view.* .. _edit-event-view: Edit Contract Race view ============================ The Edit Contract Race view can be used to update the specifics about the race, and to generate a contract. Click **Update** to update any changed fields in the :term:`contract race`. Click **Update and Send Contract** button to generate the contract and send the :ref:`contract-email` to the race director (Contact email), treasurer, and raceservices. The contract race state is automatically set to *contract-sent*. The **Resend Contract** button is only active if contact has been sent. If in *contract-sent* :term:`state`, :ref:`contract-email` will be resent. If in *committed* :term:`state`, :ref:`agreement-accepted-email` will be resent. If the :term:`contract race` needs to be deleted, click **Delete**. You will be asked for confirmation before the :term:`contract race` is deleted. Note another option is to change the :term:`contract race` :term:`state` to *canceled*. .. image:: images/edit-event-view.* .. _contract-email: Contract email ============== The contract email is sent to give the race director access to the agreement. The race director may view the agreement, download the agreement and accept the agreement directly from this email. When the **Update and Send Contract** button is clicked from the :ref:`edit-event-view`, this email will be generated automatically. The email will be something like the following. Note this is configured in the system and can be changed by a superadmin. To: From: raceservices@steeplechasers.org Cc: raceservices@steeplechasers.org, treasurer@steeplechasers.org Subject: FSRC Race Support Agreement: - Hi , To confirm your date and lock it in on the FSRC schedule, you need to accept the Race Support Agreement. Click to `view <#agreement>`__ or `download <#agreement>`__ your Race Support Agreement for on . If you need any changes please reply to this email. If everything looks OK, please click the ACCEPT AGREEMENT button and follow the directions. Your invoice should arrive soon after you accept the agreement, but the payment isn’t due until a few days before the race. In order to get your listing on our `website calendar `__, we provide the ability for the race director to manage the listing. That way, you can customize it as you see fit. The link to get started is: https://steeplechasers.org/events/community/add. [if premiumpromotion] We'll add the race to our email promotion around . Please send along this year's artwork and registration link when you have it. [end if premiumpromotion] thanks, When race director clicks ACCEPT AGREEMENT, the link takes them to the :ref:`accept-agreement-view`. .. _agreement-accepted-email: Agreement Accepted email ======================== The Agreement Accepted email is sent when the race director accepts the agreement. This contains the same information as was displayed in the browser view after accepting. The email will be something like the following. Note this is configured in the system and can be changed by a superadmin. To: From: raceservices@steeplechasers.org Cc: raceservices@steeplechasers.org, treasurer@steeplechasers.org Subject: ACCEPTED - FSRC Race Support Agreement - Hi , Thank you for contracting with FSRC for race support services for on . [if customernotes] The following notes were captured when you signed your agreement. [customernotes] [end customernotes] [if finishline or coursemarking] You will be hearing from us about five days prior to your event for final coordination on our finish line services. [end finishline or coursemarking] [if premiumpromotion] Please watch for your premium promotion to start about three months prior to your event. To receive these, please subscribe to our mailings at http://eepurl.com/bMW_Wf, and be sure to check the Frederick Area Featured Races option. After your race, please send email addresses of your participants to communications@steeplechasers.org. These folks will be included in our mailings about Frederick area local races. As a reminder, you have agreed to include a statement in your waiver as follows, "I understand that I may receive emails about this race and other races promoted by the Frederick Steeplechasers Running Club." [end premiumpromotion] If you have any questions or changes, please contact raceservices@steeplechasers.org. thanks, .. _pre-event-coordination-email: Pre Contract Race Coordination email ========================================== Before the :term:`contract race`, an email is sent to assure proper coordination. If the race director contracted for finishline and/or for coursemarking, [5 days] prior to the race, the Pre Contract Race Coordination email is sent. The email will be something like the following. Note this is configured in the system and can be changed by a superadmin. To: From: raceservices@steeplechasers.org Cc: raceservices@steeplechasers.org, treasurer@steeplechasers.org, Subject: Coordination with FSRC for on Hi , Note this is an automated email, so it’s possible you have already coordinated on this. If so, please ignore. is coming up on and we wanted to make sure we have all our ducks in a row. will be managing your race on race day, and can be contacted at . Please let us know how many runners you expect, so that we can make sure we have the right number of volunteers to support the race. This should be sent as a reply/all to this email. [if not coursemarking] We plan to be there 30 minutes prior to your start time of to get the finish line set up. [end not coursemarking] [if coursemarking] We plan to be there 90 minutes prior to your start time of to get the course marked. Some folks will be arriving 30 minutes prior to your start time to get the finish line set up. [end coursemarking] Please take the time to review the :ref:`agreement` and let us know as soon as possible if anything has changed, at raceservices@steeplechasers.org. thanks, .. _post-event-processing: Post Contract Race Processing ===================================== After the :term:`contract race`, a couple of automated tasks take place. This processing happens [5 days] after the contract race. - :term:`Race` is automatically “renewed” meaning a *renewed-pending* :term:`contract race` is created the following year, on the same date, depending on the :term:`date rule` specified for this race. See :ref:`date-rules-view` for more information. In this case, "same date" means the Nth day of week in the month, e.g., if the race was the 3rd Saturday this year, it will be “penciled in” for the 3rd Saturday next year. **Note** if the :term:`date rule` for the :term:`race` is not set, the system creates one automatically, based on nth day of week in month. - for :term:`contract races ` which have *finishline* or *coursemarking* services, a :ref:`post-event-email` is sent to thank the race director for the opportunity to provide our services, to let them know they’ve been penciled in for the following year, and to ask them to complete a short survey on how well we did - for :term:`contract races ` which have only *premiumpromotion* service, an email is sent about 120 days before the next year's contract race is expected to occur .. _post-event-email: Post Contract Race email ============================== The Post Contract Race email is sent several days after the contract race completes. This email is tailored based on the contracted services and solicits input through a post contract race survey. The email will be something like the following. Note this is configured in the system and can be changed by a superadmin. To: From: raceservices@steeplechasers.org Cc: raceservices@steeplechasers.org, treasurer@steeplechasers.org Subject: Thank You for using FSRC Race Support Services - Hi , Thank you so much for using FSRC for race support services for on . If you’d like FSRC to post your results to the `Results `__ page of our website, please send these to results@steeplechasers.org. We recommend that you use our `race results template `__ for formatting your results file. We have penciled you in for next year on <“renew” Date>. Please let us know as soon as possible if you can confirm you’ll be staging your event again next year, or if you’re sure you won’t be. And we’d love to hear how well you think we performed. Please take a very short survey at . [if premiumpromotion] Please don’t forget to send email addresses of your participants to communication@steeplechasers.org. These folks will be included in our mailings about Frederick area local races. [end premiumpromotion] thanks, .. _post-event-email-reminder: Post Contract Race email reminder ==================================== The Post Contract Race email reminder is sent 120 days before an expected contract race which has not been confirmed. This email is similar to :ref:`post-event-email`. .. _agreement: Contract Race Agreement ============================= The :term:`contract race` agreement will be similar to the following. Note this is configured in the system and can be changed by a superadmin. When viewing, this will be a google doc published view, and when downloading this will be a pdf document. January 30, 2018 Dear : You have requested race support services from Frederick Steeplechasers Running Club for your event. This is to confirm that we have scheduled the race support services as detailed on the following agreement. Your organization is responsible for the following: - **Finish Line/Timing Services** - Provide race bib numbers with pull-off tags to all participants with the name, age and gender of each participant recorded on the tags. The runners should be instructed to pin the race bib (with the pull-tag in place) on the front where it can be clearly seen by the finish line personnel - **Standard Promotion**: Add your race to the FSRC website event calendar (if not already present): https://steeplechasers.org/events/community/add - **Premium Promotion:** Provide spreadsheet file of your participants' email addresses from the previous year (if available) , and then provide the current list at the conclusion of the race. Please include a statement in your race waiver as follows: I understand that I may receive emails about this race and other races promoted by the Frederick Steeplechasers Running Club. - **Course Support:** Aid stations and Course Marshals at key locations along the route are recommended and are the responsibility of the race organizers. FSRC is responsible for: - **Finish Line/Timing Services** - Transport, setup and operation of FSRC equipment (Display Clock, Time Machine Race Timer, Finish Line Chute, flags, signage and related materials) - Timing and scoring, including generation of a list of award winners, posting of ordered bib pull-tags with finish times at the race site, and delivery of bib pull-tags at the conclusion of the event. Note: FSRC does not tally final race results beyond the award winners. Race Directors are expected to use the delivered bib pull-tags to generate race results. - **Course Marking** - The race course will be marked with cones, directional signage and mile markers - **Premium Promotion** - Your race will be included in twice-monthly email blasts to the FSRC-maintained list of area race participants, starting three months prior to your race date. - **Results**: Your race results will be published on the FSRC website, if desired. Email results to results@steeplechasers.org. Suggested format can be found on the `Race Support Services `__ page of the FSRC website. FSRC finish line, timing and course marking services apply only to the competitive portion of the event. Walks or “fun runs” associated with the event are not part of this agreement and are the sole responsibility of the event organizer. Thanks .. _event-exceptions-view: Contract Race Exceptions view ================================== **Navigation:** Contract Races > Exceptions :term:`Exceptions ` are required to alter the normal rules for allowing races. Normally races are allowed on weekends and not allowed on weekdays. So the first Monday of September (Labor Day) is an example of an exception because we will allow races on that day. To create a new :term:`exception`, click on New from the Contract Race Exceptions view. To edit an :term:`exception`, click on Edit. .. image:: images/create-event-exception.* | **Name** This is an arbitrary name to give the exception (e.g., Labor Day) **Date Rule** Choose or create a :term:`date rule` which describes the exception. See :ref:`date-rules-view`. **Exception** *available* for a rule that overrides dates which are normally unavailable, and *unavailable* to override dates which are normally available. **Notes** Any notes the administrator would like to add .. _date-rules-view: Date Rules view ================ **Navigation:** Contract Races > Date Rules For items which need to be carried from year to year (e.g., :term:`races `, :term:`exceptions `) a :term:`date rule` can be created to describe how to carry over the item. To create a new :term:`date rule`, click on New from the Date Rules view. To edit an :term:`date rule`, click on Edit. .. image:: images/create-date-rule.* | **Rule** Defines how the :term:`date rule` is interpreted * *First*, *Second*, ... , *Fifth*, *Last* mean which Day of Week within the month (e.g., Fourth Thursday in November is Thanksgiving) - must fill in **Day of Week** and **Month** * *Date* means a particular date within the month (e.g., 25th of December is Christmas) - must fill in **Month** * *Easter* is self-explanatory -- no other fields needed **Day of Week** *Sun*, *Mon*, etc. **Month** This is the month for the :term:`date rule` **Offset Days** Use Offset Days if the day can be determined from another day (e.g., 1 day after Fourth Thursday in November is Black Friday, so Offset Days would be 1) **Additional Days** For a rule with multiple days, use Additional Days (e.g., First Sat in May plus 1 additional day is the Frederick Running Festival) **Date** For Rule = Date, this must be specified. (e.g., 25th of December is Christmas) **Year** For a rule which only applies for a particular year, the year can be specified here. .. _sponsorship-management: Sponsorship Management ----------------------------- .. _sponsorship-overview-view: Sponsorship Overview view =========================== **Navigation:** Signature Races > Sponsorships This view provides a table of all the :term:`sponsorships ` in the database. The admin can create a new :term:`sponsorship`, or select an :term:`sponsorship` for various operations. Notice the :term:`State` column. The :term:`State` may be updated automatically by the tool or the admin can update it through the administrative interface. See :term:`state` for a description of the states and whether they are set by the tool or by the administrator. Clicking the buttons at the top will take you to specific views or perform some action. :New: takes you to :ref:`create-sponsorship-view` :Edit: (requires single selection) takes you to :ref:`edit-sponsorship-view` :CSV: download a csv file of the currently filtered sponsorships. **Note** only the displayed sponsorships will be downloaded, so if there are multiple pages of sponsorships, some may be missing. The top row of controls provides a way to filter the table display down to only show the sponsorships which are in a particular race year, for a particular :term:`race `, which are in one or more :term:`states `, or are at one or more :term:`sponsor levels `. Setting race year will be "sticky" when navigating in the same browser tab, and setting race will be "sticky" when navigating within this tab or to other tabs. .. image:: images/sponsorship-overview.* .. _create-sponsorship-view: Create Sponsorship view ========================= The Create Sponsorship view is one way a :term:`sponsorship` entry is created in the tool. Generally, this is used when a new sponsor (:term:`client`) is being solicited. See :ref:`post-sponsorship-processing` for details on how existing sponsorships are automatically "renewed" for the following year. Notice the :term:`State` field. The :term:`State` may be updated automatically by the tool or the admin can update it through the administrative interface. See :term:`state` for a description of the states and whether they are set by the tool or by the administrator. When selecting **Client**, a search box is displayed. You can start typing to find the sponsor :term:`client` if they were previously stored. If a new sponsor :term:`client` is needed, click on the ** entry and the :ref:`create-client-view` will be displayed so the sponsor can be created. .. image:: images/create-sponsorship-view.* .. _edit-sponsorship-view: Edit Sponsorship view ======================== The Edit Sponsorship view can be used to update the specifics about the sponsorship, and to generate a agreement. Click **Update** to update any changed fields in the :term:`sponsorship`. Click **Send Agreement** button to generate the agreement and send the to the sponsor :term:`client`'s contact email, treasurer, and races. The sponsorship state is automatically set to *committed*. The **Resend Agreement** button is only active if agreement has been sent. The agreement email will be resent. If the :term:`sponsorship` needs to be deleted, click **Delete**. You will be asked for confirmation before the :term:`sponsorship` is deleted. Note a better option is to change the :term:`sponsorship` :term:`state` to *canceled*. .. image:: images/edit-sponsorship-view.* .. _post-sponsorship-processing: Post Sponsorship Processing ============================= After the :term:`signature race` associated with a :term:`sponsorship`, an automated task take place. This processing happens [15 days] after the race. - :term:`Sponsorship` is automatically "renewed" meaning a *renewed-pending* :term:`sponsorship` is created for the following year. .. _sponsor-query-form: Sponsor Query Form ===================== The sponsor :term:`client` can indicate their desire to sponsor a :term:`signature race` using the Sponsor Query Form. .. image:: images/sponsor-query-form.* .. _sponsor-query-log: Sponsor Query Log ===================== **Navigation:** Signature Races > Query Log When a sponsor :term:`client` fills out the :ref:`sponsor-query-form`, the contents of the form are saved in the Sponsor Query Log. .. image:: images/sponsor-query-log.* .. _sponsor-race-dates-overview: Sponsor Race Dates Overview =============================== **Navigation:** Super > Race Dates [super-admin only] .. image:: images/sponsor-race-dates-overview.* .. _sponsor-race-variables-overview: Sponsor Race Variables Overview =============================== **Navigation:** Super > Race Variables [super-admin only] .. image:: images/sponsor-race-variables-overview.*