.. _glossary: Definitions =============== .. glossary:: :sorted: client Name of the entity with whom the contract is being entered with. For :term:`contract races `, the contract is sent to the client 'Contact Email' for approval. For :term:`sponsorships `, the agreement is sent to the client 'Contact Email', already deemed approved. contract race :term:`Race` on a particular date. E.g., the contract race record saves information about the 9/14/2019 Market Street Mile course The course has an address where the finish line will be set up. Generally, we work with loop courses, so this is the same as the starting line. date rule A rule which defines a date on which a :term:`race` or :term:`exception` is created. E.g., Third Sat Aug is a date rule. exception An exception to 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. lead the leader who will run the finish line operation on the day of the :term:`contract race` race A race can be run annually. The 'race' (e.g., Market Street Mile) has information which doesn't generally change, e.g., it's run on the second Saturday of September. Compare to :term:`contract race` which is a race on a particular date. renew A :term:`race` is renewed a few days after the :term:`contract race` for the current year. The :term:`date rule` for the race is used to schedule the race for the following year. service - finishline - timing service done by the race services team - coursemarking - marking the course done by the race services team - premiumpromotion - advertisement for local races done by the communications team, sent periodically signature race A signature race is a race owned by the Steeplechasers which charges for registration, has a significant budget, and has net proceeds go to a charitable beneficiary. sponsorship A sponsorship is when a :term:`client` provides funding for a :term:`signature race` in a particular year in return for :term:`sponsor benefits `. sponsor benefit Sponsor benefits are the benefits received for a :term:`sponsorship` in consideration of the funding provided by that :term:`client`. Sponsorship benefits are different for each :term:`signature race` for each :term:`sponsor level`. A sponsor benefit may be assigned to more than one :term:`sponsor level`. sponsor level Sponsor levels are defined for each :term:`signature race`. The sponsor level for a particular :term:`sponsorship` is determined by the amount of funding provided by that :term:`client`. Different :term:`sponsor benefits ` are assigned for each sponsor level. state - :term:`contract races ` - *renewed-pending* - :term:`race` was copied automatically to the next year ("renewed") during :ref:`post-event-processing`. The admin is expected to confirm with race director that the :term:`contract race` will happen and that the date and other :term:`contract race` details are correct. This is set automatically through :ref:`post-event-processing` or after clicking Renew. - *tentative* - race director has confirmed :term:`race` will be run again this year, but is not ready to receive the contract. This is set by the admin. - *contract-sent* - race director has confirmed the date. Admin has sent contract to race director. This is set automatically. - *committed* - race director has signed contract (electronically). This is set automatically. - *canceled* - :term:`contract race` has been canceled, but we don't want to lose track of it. E.g., if the race owed or paid money it's better to change the state to canceled than to delete the :term:`contract race`. The transition from *renewed-pending* to *tentative* is done by the admin using the :ref:`create-event-view` or :ref:`edit-event-view`. This should be used to help remember which races have had some discussion with the race director. - :term:`sponsorships ` - *renewed-pending* - :term:`sponsorship` is copied automatically to the next year ("renewed") after the :term:`signature race` is completed. Alternately, if the admin wants to consider a new sponsor :term:`client` the admin can create the :term:`sponsorship` manually and place it in the *renewed-pending* state. - *tentative* - the :term:`signature race` director has solicited the :term:`sponsorship` from the :term:`client` but the client hasn't responded. This is set by the admin. - *contract-sent* - not used for :term:`sponsorships ` - *committed* - the :term:`client` has agreed to this year's :term:`sponsorship` and the agreement has been sent. This is set automatically. - *canceled* - the :term:`client` has indicated that they will not be sponsoring the :term:`signature race` this year. The transition from *renewed-pending* to *tentative* is done by the admin using the :ref:`create-sponsorship-view` or :ref:`edit-sponsorship-view`.