LoCo Directory

The purpose of this page is to layout the design process behind the future release of the LoCo Directory in Django.

Site Layout

The following image provides an overview of the initial proposed site layout:

Process

1. Guest goes to home page. 1. Guest views Location List to see what is in their area

1. Guest can either search for a location or click on a location.
2. Guest goes to the Location Page.
   1. Guest can either view a list of teams or events in that location.
   2. Guest can go the Location Manage page only if authenticated (see below)
      1. Guest can edit, add, or delete a Location only if they are logged in and authenticated.
         1. Deletion can only be done by a site administrator.
         2. Addition can be made by authenticated user ("administrator of a team in LP") when adding a team.
         3. Editing can be made by authenticated user ("administrator or a team in LP" or authenticated "Team Leader or Contact").

1. Guest views Team List to see all teams.

1. Guest can view an Approved List and an Unapproved List of teams
2. Guest can search all teams.
3. Guest can navigate to a Team Page.
4. Guest can view a list of events for a team.
5. Guest can only go the Team Manage page only if authenticated (see below).
   1. Authenticated user can add and edit a team
   2. A team can only be removed by a site administrator.

1. Guest views Event List to see all events.

1. Guest can search for events (event name, event location, team)
2. Guest can view the Event Page
3. Guest can only go to the Event Manage page only if authenticated (see below)
   1. Authenticated user can add, edit, and delete an event

Authentication

Authentication will be provided by an OpenID login through Launchpad. From here the application will check to see if the person logging on is an administrator of a LoCo Team. If they are an administrator or get added to the application by their LoCo Team administrator, then login will be successful and they will have access to the "Manage" pages. If they do not qualify for the previous, then they will remain in a guest status and will only be allowed to view.

Class Lists

Contacts

• First Name
• Last Name
• Email
• Phone (optional)
• Street Address 1 (optional)
• Street Address 2 (optional)
• Country
• City
• State
• Zip (optional)
• Launchpad Page

• Team

• Title ('Primary Contact', 'Secondary Contact', 'Team Administrator')
• Messaging ('IRC', 'Yahoo', 'MSN', 'Jabber', 'ICQ') - include nickname(s)

Teams

• Name
• Status ('Approved', 'Unapproved')

• Contacts

• Country
• City (optional)
• State

Events

• Name
• Description
• Type ('Bug Jam', 'Packaging Jam', 'Install Fest', 'Meeting', 'Conference', 'Release Party', 'Get Together'...)

• Team

• Date
• Time
• Street Address 1 (optional)
• Street Address 2 (optional)
• Country
• City
• State
• Zip (optional)

• Contacts