Please report any problems to the Shared Tools Team at st-help@doit.wisc.edu    Broken Links? Missing Macros? WIKI Retiring Plugins
Child pages
  • POD Meeting 2010-08-05
Skip to end of metadata
Go to start of metadata

{secto

Previous Meeting | Next Meeting

Use of Personally Owned Devices for University Business (POD)

Thursday, August 5, 11:00-1200, Memorial Union.

  1. Agenda review OK

  2. Status of leadership discussions.

    Action: No campus conference on POD is needed at this time.

  3. Where do we go from here?
    Handout:
    POD Recommendations

    Action:

    • Clarify what is meant by an application or a service (this issue was previously identified)
    • Meet with Heideko Mills and/or other members of her team to discuss how to coordinate policy with technical implementation. Gary will see if she can attend the next POD meeting, (or if some other meeting can be arranged.)
    • Update the recommendations, and submit them to the interim CIO.

  4. Possible revisions to Guidelines for Use of Non-UW-Madison Applications and Services
    Handouts:
    Guidelines for Use of Non-UW-Madison Applications and Services for Research
    Guidelines for Use of Non-UW-Madison Applications and Services for Instruction

    Action:

    • Publish an additional version of the guidelines for "administration", since this is an important issue for them as well.

    • Recommend that the university create a process for contracting for non-uw apps and services. The team could suggest a process as a starting point for further disucsion. The process would to determine:
      1. whether or not we need/want a contract with a supplier
      2. how to handle getting the contract
      3. what should be in a typical contract

    • Recommend there be a brief list of major or most commonly sought apps and services. The team could suggest an initial list as a starting point. The list might be used in combination with communications efforts and referenced in the guidelines. The list would not attempt to be exhaustive, but could address the most commonly sought functions. The UW-Madison services could be updated once a year by searching for relevant services on various web sites. The non-UW apps and services could be updated as contracts are negotiated (see process recommendation above.)

      Such a list might be arranged by function and/or keyword, to help faculty and staff:
      1. find UW-Madison apps that can perform the function
      2. select a non-UW-Madison option with whom we have a contract or other trust relationship

    • Some things that might go on the list:
      • Filesharing (also called a Drop Box)
      • Web hosting
      • Calendar
      • Email
      • Document sharing
      • Streaming media
      • e-Learning
      • Backup
      • Tethered license server
      • Various from Library
      • Various from UW-Extension
      • Various from others on campus

    • Some candidates for additional contracts (things estimated as used by a sizable number of staff or units). For some of these there is an existing UW-Madison service. Sometimes the issue is cost, sometimes functionality, sometimes ease of use. Examples: some dislike the WiscMail web interface to the extent they prefer to find an alternative. Some faculty need/want functions not provided in Learn@UW, so they use Moodle. Candidates include:
  5. Other?

Future Meetings:

Attachments

No files shared here yet.

Contact

  • No labels