Questions:
- How long have you had a portal?
- What constituents are being served?
- What are the high level functions of the portal? For example:
- Provide news/communications, perhaps targeted to students/faculty/staff, by campus, by school, etc.
- Display messages targeted to individuals based on their status, deadlines, etc.
- Use collaboration tools such as email, calendar, etc. (see new messages/appointments, perhaps create new information within the portal)
- See current information from core business systems, for example: my drop/add status from the student system, my upcoming paycheck from the payroll system, etc.
- Carry out tasks within the portal that post data back to core business systems, for example, drop a class, enroll in a benefits plan, etc.
- Provide quick links to frequently used web-based services
- Provide comprehensive links to web-based services (not limited to the portal, could be located in other applications), perhaps targeted to constituencies
- What frameworks are you using?
- How does the portal relate to other aspects of the university's web presence? For example:
- Relationship to the university home page
- Relationship to campus, school, department, and office web sites
- Relationship to web applications for ERPs (such as student system or HR system self service)
- Relationship to the university's LMS(s)
- Relationship to the university's presence in non-university sites such as Facebook, Twitter, etc.
- What is your intent for the portal as a "destination"? For example:
- We expect users to make it their browser home page
- We expect users to check for new content at least once a day? week? month?
- Once a user has access to the portal, we expect it to be their primary point of interaction with the university during their life cycle
- We expect users to visit the portal anytime they are trying to complete a university administrative task
- We expect that users will mainly visit the portal for a mandatory business process (for example, students recieve a registration email that links them to the portal)
- We offer users a persistent login to the portal so they can visit any time without logging in again
- Usage of the portal varies a lot among students/faculty/staff
- Is your portal, or some of its content or services, designed to be consumed other than as a web page? For example:
- As a mobile site (if so, how does the portal relate to the university's overall mobile strategy?)
- As RRS feeds
- As messages or alerts to twitter, IM, SMS, etc.
- Please provide a brief description of the current state of play
- Please describe the governance structure. For example:
- Who has overall responsibility for the content and services in the portal?
- Who decides how content and services are added? What process is followed? What standards are applied?
- Please provide a url to the portal -- if it is open to anonymous users
- Please provide a link to useful documentation about the portal strategy
- Please provide a link to any end user documentation that would help us understand what the portal does