Notes
Slide Show
Outline
1
Open Source Update:
Sakai, OSPI, Chandler, DSpace
  • Scott E. Siddall
  • Denison University


2
Future of the software market
  • We share unique software requirements
  • Education is a tiny piece of the global software market place


  • Who will create our software, at what cost?
  • Will we have to craft our own software?
  • What will be the impact of software development by for-profit education?
3
Build-Buy-Borrow
  • Build your own?
    • Bear all the development costs
    • Provide all your own support
  • Buy?
    • Share development costs with others, plus a vendor profit
    • Pay for support from vendor
  • Borrow (open source)?
    • No licensing costs, or share the costs
    • Provide your own support, buy it, get it from the community
4
Open source is a licensing model
  • Open Source Initiative
  • 55 licensing models
  • GNU Public License (GPL) applies to 40,000 projects at Sourceforge
  • GPL, BSD, Mozilla, MIT are all popular
5
“The Cathedral and the Bazaar”
  • Every good work of software starts by scratching a developer's personal itch.
  • Good programmers know what to write. Great ones know what to rewrite (and reuse).
  • When you lose interest in a program, your last duty to it is to hand it off to a competent successor.
  • Treating your users as co-developers is your least-hassle route to rapid code improvement and effective debugging.
  • Release early. Release often. And listen to your customers.
  • Given a large enough beta-tester and co-developer base, almost every problem will be characterized quickly and the fix obvious to someone.


  • - Eric S. Raymond, 1997
6
“Open source is moving up the stack” *
  • Central services and infrastructure
    • Email systems, servers, network management tools
  • Desktop operating systems
    • Linux, Sun Java Desktop
  • Web applications
    • ePortfolios, portals, course management, digital asset management, collaboration and communication tools
  • * Brad Wheeler, Indiana University
7
The Pros and Cons
  • OSS costs less than proprietary software
  • OSS licensing is easy
  • OSS is more reliable, fewer bugs
  • OSS can be customized
  • OSS is more secure
  • OSS is better because it uses open standards
  • OSS is by and for a community
  • Proprietary software has better support
  • OSS is difficult to install, distribute, migrate to
  • OSS avoids vendor lock-in
  • OSS reuses software elements efficiently
  • Proprietary software developers have better resources
8
The Culture of Open Source
  • Complex software development
  • By loosely coordinated developers and contributors
  • In an informal meritocracy
    • software specifications are rarely written
    • continuous design instead
    • virtual project management
    • a gentle hierarchy


9
Need for leadership
  •    “People think just because it is open-source, the result is going to be automatically better. Not true. You have to lead it in the right directions to succeed.”
  • - Linus Torvalds
10
Community Source
  • Purposeful coordination of work within a community
  • Based on the principles of open source development
  • A greater reliance on
    • Defined roles
    • Responsibilities
    • Funded commitments


  • In between the cathedral and the bazaar




11
Practical recommendations
  • Examine the entire cost
    • Licensing, hardware, support, training, documentation, migration from legacy tools
  • Ask why you are considering any application
    • Are learning outcomes the driver?
  • Pilot the software
    • Directly involve all stakeholders; consider outsourcing the pilot
  • Start with “low hanging fruit” – not mission critical applications
  • Understand and plan for support needs
  • Spend avoided licensing costs on local staff development
  • Keep looking – new opportunities arise each week
12
 
13
 
14
Consortial piloting in Ohio
15
"Four universities – Mellon funded"
  • Four universities – Mellon funded
  • Collaboration and Learning Environment
  • Community Source based on open standards
16
 
17
Sakai 1.5.0
18
Open Source = Freedom
  • Samigo as an example of flexibility


    • Stanford Assignment and Assessment Manager
    • Navigo (Indiana University)
19
Samigo features
  • Assessment Authoring
  • Assessment Publishing
  • Assessment-taking Management
  • Assessment Grading
  • Question Pools Management
  • Publishing Template Management


20
 
21
Organize & Publish Assessments
  • Library of assessments for a course
    • Question & Test Interoperability XML format
  • Published assessments with responses, grades
    • Can be published to sections, groups in course
    • Can have different release, due, retract dates



22
Question Types
  • Multiple Choice (single and multiple correct)
  • Multiple Choice Survey
  • True/False
  • Matching
  • Essay/Short Answer
  • Fill in the Blank
  • File Upload
  • Audio  Recording
23
Pedagogical Flexibility
  • Online Test
  • Self-study questions
  • Homework, problem-sets
  • Essay, code, or project submission
  • Language drills
  • Quick knowledge probes
24
Online Testing
  • Unique tests for each student
    • Randomized order of questions
    • Randomized draw from question pools
  • Timed test-taking during access window
    • Auto-submit at end of timed period
  • One submission only
  • Higher Security
    • IP Addresses restricted
    • Secondary Password (proctored)
  • No late submissions accepted
  • Scores transferred to gradebook




25
Self-Study Questions
  • Immediate feedback
  • Random access to questions during      quiz-taking
    • Table of contents
    • Marked for review list
  • No record of score in gradebook
  • No due date; always available to student
  • Unlimited submissions allowed


26
 
27
Homework/Problem Sets
  • Published with multiple release and due dates for different sections
  • Multiple methods for handling late submissions
  • Students can save work during assignment period.
  • Auto-grading with methods for question type for diagnosing learning problems
  • Quick-reviews of student aggregate performance by instructors viewing histograms, statistics.
  • Pools for organizing questions for reuse


28
Essay and Project Submission
  • Use file upload question type for submitting any type of document
  • Grader can download assignment; upload marked-up file to return to student
  • Grades are recorded in gradebook
29
Templates
  • Create Assessment “Types” for different disciplines, different uses
  • Select what which choices are available to the instructor.
  • Hide complexity by making choices for the type (e.g., self-study always has immediate feedback)


30
Open Source Portfolio Initiative
  • http://theospi.org


31
OSP 2.x coming
  • A major curricular project for any campus
  • Integrate e-Portfolio into CMS
  • WebDAV access
32
Problems to solve
  • Innovators deform CMS tools to carry out learning activities
  • Innovators use many tools
  • Innovators burn out
  • Innovations do not transfer because they are complex


33
 
34