Error!

Spaces has been migrated to the cloud. Please go to https://ucla-confluence.atlassian.net to update your space/s.

IT Services has migrated the content of spaces.ais.ucla.edu to Atlassian Confluence Cloud. Please visit https://ucla-confluence.atlassian.net to update your space/s. Spaces.ais.ucla.edu is now in read-only mode through July 31st, 2024
Child pages
  • Meeting Notes - 2011-10-27 Conference call

Versions Compared

Key

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

...

  • There are certain attributes that SP's often request. Often, these are bundles of attributes. Some of the data is low risk and do not expose identity, but some are high risk attributes.
  • We want to determine what categories/bundles are often requested so that we can document this and bundle data to certain types of SP's. This way, when new SP's come on board, there is a clear process and set of requirements for the steps they need to take in order to get the data they need.
  • The group brainstormed different data attribute bundles, as well as low/medium/high categories. Once a recommended process is set, it can be taken to the ITLC for endorsement. Afterwards, the ITLC could reach out to the data proprietors of each campus.
  • Arlene says that the focus is on the UC system and not a generic InCommon-wide solution.
  • InCommon has bundles that can be released to research-type providers. We can look at them to avoid duplication of effort.
  • Dedra says that we can also talk to other SP's that are coming online to see what their requirements are; this could help us better develop these sets of attributes.
  • Dedra asks what each campus has to go through in terms of talking to their data proprietors for the release of information. The response is that it generally varies widely from campus to campus. Some campuses have a very lengthy process while others do not.Hello