1 / 37

OSPI: Open Source Portfolio Initiative

OSPI: Open Source Portfolio Initiative. Steve Cawley, U of Minnesota Kari Branjord, U of Minnesota Trent Batson, U of Rhode Island. Jay Fern, Indiana U Paul Treuer, U of Minnesota, Duluth Janice Smith, r-smart group. Introductions. Agenda. History Future of the Community

jase
Download Presentation

OSPI: Open Source Portfolio Initiative

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. OSPI: Open Source Portfolio Initiative

  2. Steve Cawley, U of Minnesota Kari Branjord, U of Minnesota Trent Batson, U of Rhode Island Jay Fern, Indiana U Paul Treuer, U of Minnesota, Duluth Janice Smith,r-smart group Introductions

  3. Agenda • History • Future of the Community • Future Functionality • Implementation: Institutional • Implementation: User Perspective • Questions

  4. Kari Branjordbranj002@umn.edu Director, Enterprise Application and Web Development. OSPI Founding and Current Board Member

  5. History of OSPI • How did OSPI happen? • What key decisions were necessary? • How did we arrive at a governance structure? • What can be learned from our experience?

  6. Birth of OSPI • U of Minnesota Portfolio • Conversations with U Del, rsmart for years • Observing JA-SIG • Educause 2002

  7. Initial Principles and Goals • Monolithic code base to modular code base • Scrub (refactor) U of M codebase • Open Source infrastructure • Standardize coding conventions • Dole out assignments

  8. Starting a Community • NLII networking, January 2003 • EPAC • Press Announcement in February 2003

  9. Solidifying a Community • Monterrey, host John Ittelson • Attended by 19 thought leaders, representing 12 institutions, 1 foundation, 2 for profit companies • Set application direction • Initiated discussions about resource involvement

  10. Governance • Recognized the need for leadership • Meritocracy-based structure • Significant, sustained contribution required, based upon opinions of members

  11. Governance

  12. Strategic Planning • 2-day Board Meeting in Boulder • Define role of for-profit companies and commercial support • Planned for several funding options • Refined technical direction

  13. The Code • U of M code refactored January to July using staff from 3 groups. • Testing performed by 8 groups • Released 7/30/03 • Largest implementation is U of M with over 30,000 users • First supported customer--Virginia Tech

  14. The Geek-y stuff • J2EE compliant • Linux • Apache • Tomcat • Future: OKI OSID-based

  15. Current Community • 1225 users have registered for a demo account (914 US, 311 Int’l) • 770 Active Groups (68%, 32 %) • 993 Individual Code downloads

  16. License Agreement • Start early! • Adopt and Adapt • Open/Open

  17. Current Efforts • 1.x, Focus on Presentation and Usability • 2.0, Funded by Mellon, more from Jay Fern

  18. Future of the OSPI Community Trent Batson Director, Information & Instructional Technology Services OSPI Board Member University of Rhode Island

  19. Community Building • www.theospi.org • Leverage existing organizations • User and Community Conference July 2004 • Collaboration

  20. Developing Functional Requirements for Open Source Portfolio Jay Fern Project Lead OSP 2.0 Indiana University

  21. Common Interest Groups Global Actions Workspace Personal Documents Libraries Object Repository Interactions Graphics Others… Services Core Management Core Access Repository Administrative Profile Presentation Scaffolding Reports Transaction

  22. Institutional Implementation of the Open Source Portfolio Janice A. Smith

  23. Strategies for Success • Develop a comprehensive vision • Build a committed community • Plan for technical support • Prepare for academic challenges

  24. ePortfolio Benefits for Institutions • Assess learning in • courses • programs and degrees • institutions • Prepare for accreditation • professional • institutional

  25. ePortfolio Benefits for Individuals • Develop self-esteem • Manage evidence of success • Prepare for careers • Facilitate advisement • Enhance faculty-student communication • Streamline promotion and tenure

  26. Create Interest in ePortfolios by • Involving stakeholders in planning • Inviting key faculty to pilot ePortfolios • Giving access to everyone • Linking to campus systems • Assisting with curricular change • Helping faculty document their success • Showcasing excellence

  27. Get the freedom of open source with the confidence of expert support

  28. r-smart can help you • Assess your site for success • Plan your implementation project • Install and configure your ePortfolio • Customize it for your institution

  29. with r-smart you can • Prepare faculty and students • Adopt best practices in ePortfolio use • Access ongoing technical support • Participate in a community of users

  30. Ok, what is it?

  31. Paul Treuer ptreuer@d.umn Associate Professor Supportive Services Program, University of Minnesota Duluth Open Source Portfolio Implementation Strategies: theUser’s Perspective

  32. Pre-college Programs Introduction to College Learning College Writing Portfolio Camp Getting Oriented to ePortfolio at the University of Minnesota Duluth

  33. Building a Comprehensive ePortfolio Portfolio Requirements in Academic Programs • Program Portfolio Checklist • Portfolio Assignments in Program Courses • Capstone Courses Document Faculty/Staff Learning and Growth • Unit and Staff Checklists Automated Integration with System Records • Photo and Demographics • Academic Records (Transcript and Degree Audit) • Professional Development (Training Record)

  34. Using ePortfolio to Present Oneself • Advisement • Admission to Academic Programs • Peer-to-peer Collaboration • Letters of Recommendation and Award Nominations • Learning Measured against Professional Standards • Mentoring • Applications for Employment • Professional Evaluations and Promotion

  35. Portfolio Help Desk Career Services Port- folio Resource Center Instructional Develop- ment Workshops Portfolio User Guides, Published by UM Technology Enhanced Learning (TEL) http://www1.umn.edu/tel/TELatUM/Portfolio.html Getting ePortfolio Support

  36. Quarterly Performance Review Accessing Records Remotely Mentoring/Teaching Peer-to-peer Colla- boration Background for Letters of Recommendation Sharing Professional Activities with Family and Friends The User’s Perspective: How am I Using ePortfolio?

  37. Questions?

More Related