1 / 37

Digital Marketplace Project: Update for PTSC

Digital Marketplace Project: Update for PTSC. Academic Technology Services California State University October 18, 2006. CSU Integrated Technology Strategy. Academic Technology Plan in 2003 Developed through campus consultation and cross-functional leadership

wilona
Télécharger la présentation

Digital Marketplace Project: Update for PTSC

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. Digital Marketplace Project:Update for PTSC Academic Technology Services California State University October 18, 2006

  2. CSU Integrated Technology Strategy • Academic Technology Plan in 2003 • Developed through campus consultation and cross-functional leadership • Approval/Direction on 1st Four Priorities by Presidents and Provosts • Foundational Skills (Math, English, ICT) • eLearning Framework (LMS, MERLOT, Libraries, ) • Student Success (Degree Audit) • Digital Marketplace • Continued consultation with advisory groups + • CO leaders provide new/additional directions Want MORE? http://www.calstate.edu/ats

  3. CSU Strategic Direction by Board of Trustee • Reduce Remediation • Facilitate Graduation (22 Points of Light) • Provide Access to Quality Education • Section 508 compliant • Affordable • Convenient The CSU has significant imperatives to improve

  4. Digital Marketplace is a CSU Strategic Response to Imperatives for Change VISION: Establish an electronic exchange and commerce trading presence to share, sell, and distribute academic technology goods, and educational content and services to the CSU and subsequently to other institutions of higher education. SCOPE OF IMPACT: Worldwide Service SCOPE OF WORK: Focused on high value needs and low-hanging fruit

  5. Department Store - Commerce Digital Marketplace Village • Formality • Structure • Standards • Regulations Library - Public Interest • Individual goals served • Sale of goods and services products • Amazon.com model Farmers Market - Exchange/sale • Serves the community good (Through “tax” dollars) • Some free services to public • ID authentication for privileges (Library Card) • CSU Electronic Core Collection • MERLOT peer review collection; services Community Park - Share • Direct sales between producers and customers • Wholesale to wholesale or retail to customers • Peer to peer transactions • eBay.com model • DIVA • Peer to peer/public • Direct exchange/use/share • MERLOT free exchange section Warranty & implied quality assurance • City Managers & Professional Staff • Provide infrastructure, operations and services • Town Council • Provide policies, laws, etc. • Start with CSU, and add other higher ed institutions as members later

  6. What are the Benefits to the CSU? • Enable student success through availability of learning resources • Improve readiness • Deliver accessible education • Facilitate graduation • Reduce the cost of content to students • Provide students greater choice in finding and organizing content • Provide faculty greater choice in designing curriculum using free to fee-based content • Provide a convenient and efficient one-stop, web-based shopping • Simplify life

  7. Relationship: Work flow among functions • Content provider distributes materials • User browses and acquires materials from retailer • Retailer provides permissions for acquiring material from clearing house • Content Host delivers material to user or users application • Clearing house handles the transaction and billing for learning content royalties

  8. Some Design PrinciplesWhat the Digital Marketplace is • A broad set of open, standards-based Internet services that allow for the exchange of commercial and non-commercial education content between many providers and many users • This exchange treats education content individually at an object-level • This exchange operates independently of the application which uses the education objects (e.g. a LMS or an eportfolio) • This exchange enables full access compliance by using applications • Providers are free to put conditions of use on their property • Users are free to gather content from any source available • Providers and users are free to negotiate terms as appropriate • The integrity of the exchange is maintained by trusted third parties which manage the exchange

  9. The Digital Marketplace:What are the challenges? • Requires • True content inter-operability • True application inter-operability • Trusted rights management and billing mechanism • Parties working together to define the roles and how the roles will work together • Everyone must see the potential for meeting their own goals and objectives • Business cases against specific business models close • Institutions meet their academic needs and operational requirements • Must establish a new entity for many-to-many transactions: Clearing House • The IP behind this design must be open • User requirements must guide role and relationship definitions to scale up consumption

  10. Master Plan • Multi-Phase Rollout • CSU • MERLOT • ROW • Initial Phase (January, 2007) • Assure approach remains valid • Gather use case requirements from faculty, students, publishers • Build initial elements as part of e-Leaning Architecture Initiative • Establish an governance structure to guide the development of the DM • Look for early demonstration • Trial System (August, 2007) • Version 1.0 (first wave of campus users) Production Rollout (January, 2008)

  11. Developing Partnership • Approach must include key players in the HE learning marketplace • Attendees at Digital Marketplace Summit on July &/or Sept 25-26 at the CSU • Apple • Bedford, Freeman, Worth • Blackboard WebCT • CISCO • Desire2Learn • Giunti • HarvestRoad • IMS Global Learning • O.K.I./MIT • Oracle • O’Reilly Media • Pearson • Sun • Thomson • Varsity Books • Recent inquiries to join • Microsoft • Adobe • Angel • McGraw Hill • Carnegie Mellon • IBM

  12. Applications views into DM for specific purposes Dept Head Faculty Faculty ePorfolio Student LMS Provost Digital Marketplace Content Services Faculty Data Warehouse Syllabus Builder Student Administrator Virtual Classroom Adaptive Learning Faculty Digital Marketplace will become transparent to users as application are defined by the users in the terms of how content is used and interacted with to provide efficiencies in teaching and learning (DM will be the asterisk and not the focal point)

  13. Three Major Services Educational Applications Services Content Services Publish / Assembly Services • User- Faculty • Administrators • Facilitates reuse • Enforces content compliance • Reduces time on task • Increases quality • User- Students • Faculty • Administrators • Use Case Driven • Aligned to CSU Initiatives • Customizable by campus • User- Content providers • Content Delivery • Clearinghouse functions • Transparent to Faculty • & • Students

  14. e Content Protection Layer Digital Marketplace Architecture and Application View Oracle Services Oriented Architecture Digital Marketplace eCommerce Digital Marketplace will be the first application deployed within the ATS SOA

  15. 1) Content Delivery 7) Course Catalog 13) Assessment 2) Federated Search 8) Course Creation 14) Grading CSU DM SOA Services 3) Repositories Of Record & Federated Meta data 9) Resource Upload and Submission Calendar Workflow 4) E-Commerce 10) Content Authoring & Assembly 5) Content Protection Service 11) Collaboration Tools Common CSU ATS Services Optional CSU ATS Services 6) Identity Access Management 12)Content Preview No Common Service planned at this time

  16. Fundamental Technology Strategy Leveraging the M.I.T / O.K.I projectapproach to SOA flexibility and sustainability along with the Oracle SOA implementation http://www.okiproject.org

  17. Open Service Interface Definitions (OSIDs) • Define “Service Sockets” for Applications “Service Plug-ins” for Service Providers • One element of the SOA landscape • Complementary with Web Services WSDL, etc. and other protocols • Supportive of Data/Metadata standards

  18. Content / Repositories Rotch Visual Collections Tufts Digital Library Tufts Artifact Google MERLOT ARIADNE Jstor ARTstor UCLA Digital Library iTunes U Cisco VMS Bedford, Freeman, and Worth Metamedia Museum of Fine Arts, Boston Others in progress Pearson Custom Publishing Thomson Publishing O’Reily Configurable Repositories Z39.50 SRU/SRW OAI Fedora MySQL Postgres Dspace Giunti Learn eXact Lobster HarvestRoad Hive Local Google site Available elements using this approach

  19. Federate Search Tools SearchParty Lionshare Thalia image tool (MIT) Stellar image tool (MIT) Harvest Road Hive Authoring Tools Pachyderm (Presentation Tool) Exact Packager (Learning Object Authoring) Hive Explorer with RELOAD VUE (Concept Mapping) LMS Blackboard (in progress) WebCT (in progress) Sakai Moodle (in progress) Content Preview VUE Harvest Road Explorer Delivery Application iTunes U Learn eXact Mobile Delivery Devices Web Browsers iPOD IPAC Blackberry Available elements using this approach(1st Pass need more validation) (2 of 2)

  20. Kinds of Specifications/Standards

  21. Data/Interface/Protocol Examples : • Service Interface Specifications - including but not limited to: • OSID • Repository OSID for JSR 170 ( in process) • Etc… • Data Specifications - including but not limited to: • IMS Content Packaging • IEEE LOM • SCORM Packaging • Dublin Core • METS Schema • Etc… • Protocol Specifications - including but not limited to: • Web Services • SRU/W • Z39.50 • Etc…

  22. Interface Adapters Patterns (types of OSID services) • Federating • e.g. search or submit with multiple targets • Unified View • e.g. map disparate metadata to a common set of types • Disaggregation • e.g. distribute implementation • Business Rule • e.g. conditional behavior • Side-effect • e.g. make a group when making a course • Version • e.g. mapping to previous OSID implementations • Bridging • e.g. providing cross language solutions

  23. (LMS – Get Content) Merlot Pearson CSU LOR OSID = Open Service Interface Definition (Magic Middleware)

  24. CSU Metadata Framework

  25. Authoring Tool 1 content into two locations in different formats Assistive Device LMS Delivers and renders “same” information in different formats and locations

  26. CSU Institutional Repository Student Librarian Faculty

  27. Summary • Digital Marketplace is a technology infrastructure service that enables • SCALEABLE CUSTOMIZATION of user-centered application services • Technology-enhanced services across multiple CSU initiatives • CSU to break down significant barriers to deliver an accessible, affordable, and high quality education

  28. www.calstate.edu

  29. Professor Plum, from either a web browser (RLMS) or a desktop application (VUE), logs in. • This results in a call to the Authorization OSID implementation for DM. • 3. All tools that operate within the DM use a common mechanism for user authentication. • 4. The DM receives authorization triples from campus IAM systems (who can do what with what). • 5. Federated search is distributed to multiple repositories. • 6. The search is converted from a common form to a back-end specific form. The same holds for converting results from repositories to the common Asset and metadata form used with the OSID. • 7. Assets and their metadata flow back to the tool. • 8. Resource lists are created, based on assets, and stored in the Hive. Note that Hive can use notification and workflow to alert the accessibility office for them to examine the resource list. • 9. Hive can push resource lists to various LMSs.

  30. Back up slides

  31. CSU-DM Review Council Membership: 1 Provost, 2 CIO, 3 Faculty, 1 CFO, 1 Librarian, 1 Student Services (accessibility) DM Project Office CSU –DM Review Council DM Project Team MERLOT –DM Review Council Governance Marketplace Functional Design Engineering – Infrastructure Deployment • Responsibilities: • Represent and communicate with/to CSU campuses, DM Project Office, and other CSU advisory groups • Review and provide recommendations to the DM project office on the • Be the forum for issues and their resolution on the DM project. • Identify policy needs and recommend policies for the CSU’s planning, design, implementation and assessment of the DM project.

  32. Use Case #1 • Faculty “sampling” and selection for instructional resources for students and professional development resources for themselves • Student acquisition of instructional resources (faculty-selected and self-selected) and student development resources (see handouts)

  33. Content Publisher (1) Content Publisher Content Provider Content Hosting Facility Content Hosting Facility Clearing House Retailer (4) Retailer Retailer (5) (2) Users (3) How the Digital Marketplace will work 1: Content provider publishes content to hosting facility, informs retailers, informs clearing house 2: Retailer promotes content, user browses and acquires content from retailer, retailer informs clearing house 3: User receives permissions for content usage from clearing house 4: User received protected content from hosting facility 5: Clearing house handles billing and attribution Source: “Toward an Electronic Marketplace for Higher Education”, IEEE Computer, June 2005, pg 66ff.

  34. January ’07 Interoperability Architecture based on Use Case (so Far) Discovery Preview

More Related