PTO Sites & Directories Project Plan

Based on conversations and our meeting on 6/30/08, here is a draft of our project charter and timeline.

PHASE 1 CHARTER: To be completed over the summer of 2008.

We haven't discussed the idea of a "phased implementation" of PTO sites and directories, but it makes sense that what we're doing now is Phase 1, to be followed by additional phases. So let's start by referring to this as Phase 1 from the outset. Here are our major objectives.

Determine a web hosting account

  • Flexible enough to meet a range of tools
  • Scalable to support multiple sites/domains (e.g., wardpto.org, npstac.org, nnhsptso.org, nshspsto.org) and decent volume of web and email traffic (e.g., send out thousands of emails in a given day)
  • Team members: Arnold, Charles, Erik

Establish/refine/implement a PTO website framework

  • Incorporate/learn from best examples so far
  • Incorporate new/leading thinking around content types, extensive taxonomy? capabilities
  • Support content syndication between sites (e.g., cross-posting notices and calendar events)
  • Team members: Erik, Lisa, Janet

Design and implement a common directory system

  • Probably based on CiviCRM/Drupal?
  • Get this ready for NNHS PTSO, who seems to have highest sense of urgency
  • Team Members: Lisa, Geoff, Janet, Charles

 

ACTION ITEMS
Let's use this space for the active management of project action items. Team members can directly edit/update their action items, or post comments.

PTO Website

  • Setup sandbox – northptso.org (Drupal?/CiviCRM) - Erik
  • Draft site map
  • Determine cotent types
  • Determine taxonomy?


PTO Directory

  • Setup sandbox – northptso.org (Drupal/CiviCRM)
  • Define/Refine attributes to capture & how to organize them (schema)
  • Define guidelines & use cases for how the directory will be used


Hosting/Technology

  • Price/feature comparison; select host account
  • Setup sandbox – northptso.org (Drupal/CiviCRM)

 

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

directory history

I inherited the directory project last year. Previously, it had been created taking the flat file data (in a csv file) from the old NNPTSO site via the altrue module and manipulating it in an excel spreadsheet.

I ended up importing the data into Access, as I was more familiar with databases than spreadsheets and figured I could output the printed directory as an access report.

However, the data from the altrue module had problems:

1--there were duplicates

2--there was data missing

3--it was a flat file, with the primary entry? being by child

 

In addition:

4--the data from the school (teachers/staff directory) was in both word files and excel spreadsheets

The requirements of the directory were that it contained:

1--listing in alpahbetical order by student last name

2--listing of all students by grade

3--appendix of parent whose last names differered from the child's name

4--mailing labels for directories, including multiple orders when a child belinged to more than one household

Because time was short, I ended up creating one master flat file table in access organized by student with up to 5 parent/guardians. To make the directory, I queried that table and created several related queries (by class, by student last name, by family, etc) to generate the reports that became the sections of the directory.

It wasn't 'pretty' or 'elegant' but it worked in the timeframe I had.

Ideally, we can create a better system using many to many relationships that will be a model for future years and other schools.

Thanks for the background

Lisa, I look forward to meeting with you tomorrow. Hopefully we can take a bite out of this project.
~Janet

Syndicate content