Your SlideShare is downloading. ×
Roadshow presentation
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.


Introducing the official SlideShare app

Stunning, full-screen experience for iPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Roadshow presentation


Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide


  • 1. MyUni Institutional portal and web content management Richard Jones Bo Middleton Tracey Stanley
  • 2. Road-show format
    • Portal – What have we actually bought? What does the new portal look like? What will be in the portal?
    • CMS – What is a CMS? Role of the CMS.
    • Content – Future of Campusweb. What about current websites. Content guidelines
    • What next? Timelines. Dates for road-shows and training. Further consultation
    • Q & A
  • 3. What does a portal look like?
    • Login name: test3
    • test4….test8
    • Password: MyUni1
  • 4. Content Management System (CMS)
    • Content management is the creation, sourcing, managing, publishing and sharing of content.
    • Content Management System (CMS) is a tool to automate the management of content, to make the process of collecting, managing and publishing of valuable information easier for those that create content within the University.
  • 5. What’s the difference? Portal vs. CMS
    • Portal - Entry point on the Web to “Log In” for personalised interaction with content, personal tools, and transactional systems, “myUni”.
    • CMS (Content Management System)
      • System to help organise and maintain web content for internal, external sites and portal channels.
      • Separates content management from design.
      • Facilitates consistency and currency of content, navigation, and look-and-feel by implementing roles, workflow, and templates.
  • 6. The role of the CMS
    • To create, manage and publish Portal related content.
    • To create, manage, publish and reuse web content across University web sites.
    • To provide a framework and toolkit that can help to manage the consistent branding of the University’s web sites.
  • 7. Future of Campusweb
    • All existing ‘student’ links will be mapped into the portal, as appropriate.
    • Ensure that information is presented in as helpful and logical way as possible for students.
    • Information currency, quality and ‘student focus’ assessed and improved as we map the links.
    • Ensure that all ‘central’ content linked to the portal has been quality-assured.
  • 8. Presentation of content
    • Task-based approach; eg: How do I…
      • Get help with studying? (might include Skills Centre support, advice on plagiarism, Student Advice Centre etc )
      • Find financial help and support? (might include student loans, Access to Learning Fund etc.
      • Find information about my course? (might include timetabling, module catalogues etc).
  • 9. Quality issues
    • Want to work with ‘central’ areas to ensure all content is:
      • Appropriate to the audience.
      • Up to date and regularly reviewed.
      • Written with the web in mind.
      • Accessible.
    • Will draw up a set of guidelines and provide help and support in implementing them.
    • Writing for the web workshop.
    • Will be arranging meetings with central content owners to discuss how your content can best be presented in the portal.
  • 10. What next – portal timelines
    • March 06 – students use portal to complete online module enrolment
    • July 06 – more channels ready – new and returning students use portal for online registration
    • Start 06-07 session – change desktop in clusters, promote to new students. Staff will be able to use the portal (mostly content for students)
    • April 07 – channels for researchers
    • Start 07-08 session – new Banner functions for staff and students
    • Start 07-08 session – Prospects/Applicants portal (for 08 starters)
    • Then Alumni and (more) staff portal
  • 11. What next – portal development
    • VLE integration
      • Single sign on
      • Embedding tools
    • Banner integration
    • Portal potential
      • Mobile devices
      • Integrating other tools
      • Lifecycle portal
  • 12. What next – portal road-show
    • Portal road-show: See a demo of the new portal and join a discussion on future portal development
    • All slots:
    • 12 - 1.30 in EBL conference room
    2 nd Feb Thurs 10 th Feb Fri 20 th Feb Mon 6 th March Mon 9 th March Thurs
  • 13. What next – portal training
    • Learn how to create portal ‘groups’, how to use the portal to send targeted messages, and how to create customised portal channels.
    • All training sessions: 9.30-4.30, EBL level 10 training room
    • Book through SDDU website – ‘Courses and Workshops’ link, Search and book online
    18 th July Tues 22 nd March Wed 4th April Tues 10 th May Wed 26 th May Fri 9 th June Fri
  • 14. What next – further info
    • MyUni http:// (not yet live)
    • Portal - contact Bo Middleton, Portal Project Manager x36386 [email_address]
    • CMS – contact Richard Jones, Web CMS Project Manager x 31145 [email_address]
    • Web content – contact Tracey Stanley, Content Integration Project Manager x35569 [email_address]