Versions Compared

Old Version 9

changes.mady.by.user Lawrence Eribarne

Saved on

compared with

New Version 10

changes.mady.by.user Lawrence Eribarne

Saved on

Key

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

...

TimeItemWhoNotes
Training NeedsAll
  • Faculty and Staff Familiarity with Generative AI: Most faculty and staff are not well-versed with generative AI. There's a pressing need to educate them quickly.
  • Meeting Dynamics: Adam highlights the challenges of large meetings where participants might not feel comfortable expressing ignorance. Logan emphasizes that faculty skepticism might stem from the summer season and the need for individual sign-ups for personal ccounts.
  • Need for Practical Support: Tamara stresses the need for concrete strategies, practical advice, and prompt structures for both faculty and students.
  • Generative AI Training: Discussions revolved around different training sessions, the role of Bok, and feedback from pedagogy fellows.
  • Honor Council Issues: Rebecca mentions challenges arising from misuse or misunderstanding of AI in uses or ability to validate n the honor council.
  • TA's Familiarity with AI: Greg's survey reveals mixed experiences among TAs with AI but a majority seems excited.
  • Training Tools: The potential for various tools like Slack channels, videos, and HUIT tools were discussed, along with concerns around privacy and data storage.
  • Faculty Staff: Guidance / training needed for TAs and TFs.
  • Bok: will do onesession within fall teaching conference. This week did bootcamp for 27 pedagogy fellows and they were on the very positive,
  • Mandatory Training: Crhis suggested training be mandatory before access is provisioned.

Sandbox DemoVentz

Integration with Canvas: Jefferson discusses ongoing work to integrate GAI tools with the Canvas platform.

Tool Development and Features: Various aspects of tool development, including scaling, data storage, and user experience, were explored.

Future Vision: Jefferson suggests that success would be retiring current tools as more advanced enterprise tools become available.

Features: Adam noted that submitting link to chat history is a requirement.

Features: Chris pointed out there is one to many and many to one use cases (students across classes, and faculty across classes).

Features: Rebecca pointed out that focus on data upload and code interpretor are the correct priorities for feature dev.

Requests: Jeffeson pointed out tool will be provisioned on a request basis and capacity review. 


...