Versions Compared

Old Version 3

changes.mady.by.user Chrissi Dean (Unlicensed)

Saved on

compared with

New Version Current

changes.mady.by.user Chrissi Dean (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  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):


Issues:

  • Providing single authoritative source of data - ITS issue
  • Staff Directory - all written by Ian
  • Multiple sources - would require Ian and ITS resource wise to try and address this
  • IPFX - ITS (usually the blocker) - why is the authoritative source?  Origins as the phone directory.  
    • Could change focus away from this as final piece of data.  Change the relationship around and just take this information when it is available.

Data sources:

  • AMS - campus services
  • Banner = SSIP and SAS
  • IPFX - ITS (Product)
  • VicPhone - SQL DB that is ours (populated out of IPFX) - does not have persistent unique identifier
  • HR Database - ITS and HR (potential main authoritative source - but issues with visitors etc not in this system)
  • AD/Exchange - ITS (assumption this could be minimal data source - majority of staff will have entries in here - noting some edge cases). 
  • Research Master - research office

Options:

  • Could be managed centrally via web to create the profile - would have to be a manual extraction of data initially
  • Need to explore the data that can be extracted from these systems - Andrew could look at some of this?

Other:

  • For staff profiles, anything in additional information would have to fed into Squiz via dept admin currently
  • PBRF - research information could be derived from here going forward
  • Could potentially create a web form for staff to ingest data to be displayed on the site?
  • Web governance will play a big part in how we manage this, and where restrictions are put in place on who can edit what.  What should come from an authoritative central source, what can be managed manually.
  • Keith notes we should be aiming for structured data so we can auto generate, providing light guidelines on compliance, also providing links to staff members own sites as required