Meeting Notes 2022-December-7

• Ashley recently shared an announcement regarding a beta version of a revised instruction form.
  
  • Please review it and send any feedback to Ashley and Reanna by next Tuesday before the announcement goes out to all of CUL.

Meeting time

• Reanna will send out a message for feedback regarding our
• Would anyone be heartbroken if we cancel the Jan. 4 meeting? Many folks will be out/unavailable at that time, as well as the following week.
  • RE will check in after the week of Jan. 4 to see if we should reschedule.

• Hannah Toombs, Olin's new Engaged Leraning Librarian, will be the new
• Subteams:
  • Tools subteam:
    • Round of applause to tools subteam! They created a Kahoot proposal and already received feedback. Simeon's feedback: we need to create a statement of need regarding the tool. RE can submit a statement of need, Simeon will handle the rest of it. Full instructions on statements of need are on Confluence.
    • Ideally, we should accomplish this by next Wed, Dec. 14.
    • We can pull heavily from the proposal to get the content together.
    • TRA assessment wasn't necessary for Lauren's Kahoot subscription proposal.
    • Web accessibility check for Kahoot will take place in January.
    • RE will:
      • Check with Simeon to see if Lauren's statement of need suffices, or should we submit a separate form.
      • Correspond with tools subteam to check that the content for the statement of need is okay.
  • Data literacy subteam:
    • Decisions for colearning sessions: Tricider poll results show a tie between two potential paths:
      • Host initial panel of librarians who work with data in January/early Feb and ask for feedback about what content attendees would like for future sessions

      • Host a series (3-4) of panels/workshops throughout next semester.
        Session one will be on what kind of work folks are doing to support data literacy at CUL. Session two could be on understanding a data question and how to help with basic data questions during reference transactions. Session three could be on incorporating some data literacy into your information literacy sessions. Session four could be a primer on a programming language such as Python or R.

    • Decision: we can schedule the programs ourselves.
      • Let's start reaching out to people to schedule session.
      • Let's put who we should reach out to, as well as who will be responsible to take charge of contacting that person.
  • Perhaps early February would be an ideal time to transition into trainings: Feb. break weekend might be especially ideal, usually not that many conflicts on calendars.

Subteam Check-ins