Updates
|
Club Activities Project Requirements
Team: Webteam Task list Roles Technology: PmWiki Links Development notes Website: About All recent changes Site map
This project was completed, but did not deliver and operational system, and was not judged suitable for use on the TTC website.
Definition of success
- project delivers an operational system
- integrated into PmWiki (as a cookbook recipe)
- released to PmWiki community
- documentation (wiki based) complete, including
- full installation and configuration details (database, software, development environment, maintenance, testing)
- continuing/future development/maintenance description
- testing description
- includes an operational testing framework
- open source (same licence as PmWiki)
Project scope
- tight scope, single objective
- test first development (guidelines)
- open source software
- database design to be reviewed by TTC club member
Environment
Functionality
- database that includes activity (trip and clubnight) information,
and in some configurations can be edited as a wiki page,
including both display and hidden fields, and the capability to flag some records and fields for display,
fields to include
- date, heading, speaker, description (permits embedded wiki markup), row hidden flag
- when developing allow for future extensibility to include trips
- to date, trip type, trip location, contact phone, contact email, item hidden flag for individual contact details
- displays can be either editable, and display only,
it is envisaged that editable displays would be processed in situ in a table,
for example
- next club night (non editable) (eg as displayed on home page)
- all club nights (editable) (eg as displayed on clubnight page)
- all trips in date range (non editable) (eg could also use on home page for the coming weeks trips)
- all trip types of specified types (editable) (eg as displayed on snow trips page)
- all club nights with hidden detail (editable) (new protected page for this)
- notes
- management attributes (if any over and above PmWiki supplied features)
- all formatting to be controlled by CSS classes (naming convention data*)
- client side javascript may be used, eg to allow selection of, say, only family trips to be visible
- coding should be to a specified coding standard or guidelines
Usage
- embedded as markup in a wiki page
- selects from defined markups, date ranges, trip types etc
- configured in config.php (part of PmWiki)
- defines mark up: database, views, columns, date ranges, sorting (default by date ascending), editable or not (say
(:data base=dbname view=dbview editable=yes :)
- See also
- ClubActivitiesProjectNotes
|