Page Comparison

Initial findings from Paul (taken from WIP-29) 

• Pages are for use by students, staff and the wider public (media, researchers, staff in other organisations, etc)
• Their purpose is to allow readers to find staff they are looking for and learn about the teaching/research/publication areas, and how to make contact.
• The pages are a mixture of information drawn from up to seven (Access Management System, Research Master, Vic Phone, IPFX, MS AD, HR, and Banner) other systems and entered by staff (or administrative support people on their behalf)
• The creation process is brittle, mainly due to the start-end dependencies of the integrated or up-stream systems but in part due to the complexity of the form and the infrequent nature of using it.
• Despite the integration with many systems, the University is still poorly serviced by any sensible and authoritative identity store. Instead, different systems all master identity in their own way, all of which have strengths and weaknesses.
• The core team have many requests for help to create and maintain these pages, each individually small but quite a time commitment in total
• COO has brokered a deal with ITS to provide more/better identity data so course catalogue can construct a more complete view of a person.
• Student workshops identified that they value high quality staff pages in course selection/enrollment decision, especially for high level papers and research options.
• Considerably more important for the PG students than UG
• Find a Researcher and the Media Guide both require high quality staff profiles to work well (or realise the intended benefits). From a quick look I believe they are probably both delivery poorly on compared to expectations, mainly due to the low/variable quality of the profile information but also due to "clunky" too design. Does anyone have any review results for these services?
• Consider carefully the 3-tier model that Keith has developed, and if we support it focus on tier 2 and maybe 3. See https://victoriauniversity.atlassian.net/wiki/display/WIP/Examples+of+staff+content
• Based on the findings I recommend that we seek a scope change for CSI to include staff profile pages as core data.
• If agreed we would:

Deliver the following in WIP II, Phase II

1. Build a new form to be used for the creation and maintenance of staff profile information that will:
   1. Draw data automatically where possible (using APIs, etc). For example, Symplectic can offer an API for this, whereas Research Master can not.
   2. Require users to enter data only if it can not be sourced from another system
   3. Can be pre-populated with existing profile information (is this possible? Desirable?)
2. Produce some artefact to explain why better profiles (the audiences and what they want to see and possibly a small number of good profiles.

Advocate for these to be done elsewhere

1. Solving the problem of multiple authoritative sources of identity. Our role would be to should lend support to the cause and contribute to any (ITS) project
2. Encourage (or require?) staff to update their profiles
3. Produce detailed guidelines and examples

Meeting with Keith B, Paul S and Andrew 20/05/15 (draft notes):