Revised Adoption Process September 25, 2006
Posted by sherwood in : Uncategorized , trackbackWho: Emerging Technology Committee /ACPAC
1. - Determine Key and Desirable Parameters
Key
- Automated, authenticated account creation
- User account maintenance – including administrative reset
- Database backup facility
- Content syndication capability (RSS/Atom feeds)
- Enclosures and file uploading
- Spam blocking
- Categories
Desirable
- Comment moderation
- Pingbacks/trackbacks
- Multi-blogging (authorization of contributors)
- Image uploading
- Searchable
- Templates, Themes Lib (A)
- Multi-admin privileges (B)
- Active plugin development
+ + + + Choice: A. Student Portfolio versus B. Class-Based Blogs + + + +
A. Created at student request and linked with webdav; portfolio function requires that student can maintain the account through the duration of enrollment. Emphasis on customizability and uses as a student-centered learning tool.
B. Created at faculty request, linked with and limited to class registrants; a CMS base facilitates access management within broad framework. Uniform accessibility; less customization.
(Individual BLOGS: http://blogs.sherwoodweb.org/ )
(CMS Class blog: http://www.sherwoodweb.org/sherwood_drupal/ )
Who: TSC
2. Determine technical and support resources required
- FramEwork; security
- Evaluate software options: Scalability, Security, User controls, including templates, Record of support, development continuity and prospects
- Propose implementation option (s)
Who: APCAC and ATS
3. Prepare for Implementation
- Develop Help Documentation
- Train Help desk for student assistance; workshop for faculty
- Articulate usage guidelines in accordance with “Technology Civility”
- Articulate expiration and migration guidelines
4. Implement on Trial Basis or U-wide deployment
K. S. 2006-09-26
Comments»
no comments yet - be the first?