ARCHIVED: Completed project: OneStart v2.0

This content has been archived, and is no longer maintained by Indiana University. Information here may no longer be accurate, and links may no longer be available or reliable.

Primary UITS contact: Brian McGough

Completed: April 17, 2007

Description: Project to upgrade the OneStart portal to enhance usability and user experience as well as enabling additional content publishing capabilities for the portal

Outcome: Content migrated from OneStart v1.0 to OneStart v2.0, with enhanced features for adding additional active content in the future and a better way to navigate and find university services for constituencies in particular roles

Milestones and status:

  • Announcement about upcoming changes to OneStart in Monitor (around May 1, 2007)
  • Complete marketing plan (around May 15, 2007)
  • Complete core development (around July 1, 2007)
  • Complete migration strategy for existing content (around July 15, 2007)
  • Make pre-production environment ready so users can evaluate it and adjust to the OneStart v2.0 environment (around August 1, 2007)
  • Prepare IT Training series that deals with OneStart (after August 1, 2007)
  • Prepare Knowledge Base documents for new version of OneStart to be activated on go-live date (after August 1, 2007)
  • Hold open showcase events at IUB and IUPUI, captured for podcast distribution to other campuses and those who could not attend one of the presentations (September 1-15, 2007)
  • Production release of OneStart v2.0 (September 29, 2007)

Comment process: Email onestart@indiana.edu.

Benefits:

  • Major technological upgrades (portal, portlet compliance)
  • Major content rendering improvements
  • Easier navigation from a content layout and ontology perspective
  • Easier to write code that can be deployed in the portal

Related information: OneStart users, the Support Center, and the units that project services will need to be educated on where their services will be located in the new version of OneStart.

Risks: If communication and marketing are inadequate, users may get upset because they were unaware of the changes and not told the reason for the changes. Also, we need to inform all content providers in OneStart about the upcoming changes and work with them in migrating their content from v1.0 to v2.0 of OneStart.

Issues: There will be a cutover from using OneStart v1.0 to OneStart v2.0, and we will need to be ready to support users who have questions about the change and how to find their services. Also, some services are not in compliance with the single sign-on requirements needed to make projecting services through the portal meaningful.

Primary clients: Students (from prospects to enrolled students), staff, faculty, alumni, parents of students

Client impact: Clients will need to learn how to navigate to the services they use; this will be a considerable but short-term impact until clients get used to the new interface and navigation schemes used by the portal.

Project team: The primary project manager is Brian McGough, manager of the Systems Integration Team.

Governance: We need to form an oversight committee for the upcoming rollout very soon. It should consist of members representing all of the services deployed in OneStart.

This is document auzz in the Knowledge Base.
Last modified on 2018-01-18 15:30:21.