MINUTES: 02/07/2006 Online meeting

Please post comments and feedback, or edit minutes as needed. These were pulled from our chat transcripts on Thursday night:

Discussion of Concerns as fallout from NPL initial meeting

• Amount of work expected to be implemented between now and the end of the semester. We can break the implementation into first tier, second tier, etc. needs to address this. NPL is aware of our time constraints and we should be able to address this by keeping in communication with the site.
• Discussion of concerns of the ‘do-ability’ of the add-ons that NPL currently has and will acquire near term:
• OPAC
• E-vanced solutions calendar system, support@e-vancedsolutions.com
• Online fee payment: overdues, continuing ed registrations, course seminars, travel opportunities, etc.
• Concerns were expressed about the inability of Earthlink to support scripting. This will affect the testing of our software as some scripts will be required to perform the functionality that NPL seeks.
• ACTION: We agreed to investigate what services NPL and IUPUI could offer for a test environment. Ben will check with IUPUI first, then we will check for server space with NPL if IUPUI is unable to provide us with group space.
• Working with graphic designer at NPL may be challenging. Will need to determine what they will need from us to support addition of graphics to their site.
• General approach to design agreed upon:
• Ben and Mike will layout the initial design and apply cascading style sheets to work with multiple browser platforms
• Placeholders for graphics will be used until graphics that are suitable can be obtained
• Content will be supplied
• First pass, from current website
• Second pass, through collaboration with staff at site
• Design will support future software / resource add-ons
• It should be easy to add a new link

Keith initiated a task list outline off the cuff during the meeting; fleshed out from group feedback and comments

1. Interview client
2. Secure workspace
3. Finalize list of vendor add-ins
4. Investigate list of vendor add-ins
5. Design site / navigation
1. Design initial mock-up
2. Generate CSS from mock-up
3. Create template
4. Add content to template
5. Document template editing procedures

i. Inline

ii. Standalone

6. Add static pages
7. Build graphics and pages
8. Refine static pages and content
9. Fine tuning
10. Feedback from site
11. Fine tuning
12. Approval from site
5. Acquire graphics for site
1. Specify dimensions to meet needs on site
2. Approval from site
6. Identify parts of site that will need to be dynamically generated
1. Are those controlled by the add-in software, i.e., can the calendar supply event information as an include or part of a script?

Things to do before Sunday meeting

1. PDA Content / Browser Syndication
1. ACTION: Mike will investigate this with contacts he has available to him
2. Initial Content Template Draft:
1. ACTION: Ben will hash out the initial draft of a template
3. Agreement to meet one hour prior to next class meeting to go over some things in person; notes will be taken for anyone who can’t make the meeting
4. Post a draft of the task list to each other prior to Sunday 7pm meeting
5. Arrangements to use a non OnCourse chat relay system