EVENTS

BACK-END REQUIREMENTS

It is required that an edit-system be created to allow administration of the content of the events section by SPEEDO staff and other non-expert users.

The system itself should provide the following functionality:

Each event entry should encompass the following aspects:


   Event Name      Single line text entry

   Description     To be added as free-text into a textarea. 

                   When parsed into HTML, single carriage returns 
                   are to be treated as line-breaks, while double 
                   carriage returns will be treated as paragraph marks, 
                   when parsed to HTML.

                   It is required that the textareas in all the admin tools 
                   have WRAP="virtual" provided as an explicit attribute to
                   the TEXTAREA tag. 

   Category        To be selected from a drop-down list of pre-defined 
                   categories which are Swim, Beach and Triathlon.

   Start Date      The date on which the event will start.

                   The date will be entered as a set of numeric values 
                   selected from three horizontally aligned drop-down
                   menus.

                   The first menu represents the day (01 to 31).

                   The second field represents the month (01 to 12).

                   The third field represents the year providing a list
                   of years from the current year up to three years hence
                   (ie: 1999, 2000, 2001, 2002).

                   The default values for these fields (to be automatically 
                   set in the form when adding a new event) should 
                   be the date on which the event is being added.

                   On submission of the event details, it will be necessary to 
                   validate the dates being submitted (ie: 31 02 2000 is 
                   not valid). If an invalid date is entered, then the 
                   user's attention should be drawn to this so that the
                   erroneous data may be ammended appropriately.

                   Equally it should also be tested that the start date 
                   occurs prior to the expiry date.

   End Date        The date on which the event will end.

                   The date will be entered as a set of numeric values 
                   selected from three horizontally aligned drop-down
                   menus.

                   The first menu represents the day (01 to 31).

                   The second field represents the month (01 to 12).

                   The third field represents the year providing a list
                   of years from the current year up to three years hence
                   (ie: 1999, 2000, 2001, 2002).

                   The default values for these fields (to be automatically 
                   set in the form when adding a new event) should be one 
                   month after the date on which the event is being added.

                   On submission of the event details, it will be necessary to 
                   validate the dates being submitted (ie: 31 02 2000 is 
                   not valid). If an invalid date is entered, then the 
                   user's attention should be drawn to this so that the
                   erroneous data may be ammended appropriately.

                   Equally it should also be tested that the start date 
                   occurs prior to the expiry date.

   Country         Drop-down option listing of all relevant countries.

   Event Website   Single line text entry

NEWS LINKS

It is a requirement that any event may be linked to a list of news articles which are associated with it.

To achieve this, a list of events should therefore be provide in the news article edit template, with appropriate fields being provided as a string to enable each event to be uniquely identified.

SECURITY

Access to this area of the site should be restricted by the provision of an approved username and password.

It is our requirement that no access by any means to any of the admin tools be provided unless a valid username and password - ideally stored separately on the system in a suitable encrypted form - has first been submitted to the system by the user during that session and that the username and password submitted to the system will not be recorded as an entry in any server logs and statistics. Under no circumstances should access to any administrative tool be given to the user without an approved username and password first being supplied.