Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

Objective

State the purpose of the group in 25 words or less (brief, energizing). 

Facilitate a transition to new and updated workflows that utilize Alma. Collaborate to ensure access to all consortially and locally purchased electronic resources. Establish procedures and processes that all campuses can use to manage E-Resources. Within reason, establish standardization of terms, processes, etc. Sync the NZ workflows and IZ workflows. To provide sustainable avenues for acquiring and sharing access to e-resources within the UC system. Create efficiencies between campus members using analytical analysis. Build knowledge and skills with Alma Analytics to develop methods of assessing the efficacy and discoverability of e-resources u-c wide and locally using Alma analytics.


Roles

Members

Meeting Roles

1) Note Taker and actions items - Vice Chair
2) Time Keeper - alternating assignment

Steering Committee

  • Chair, Vice Chair and volunteer members

  • Manages the work plan and evaluates new projects


Expectations for Working Together

Decision-Making

  • We will use decision-making processes as listed in the SILS Work Practices document:

    • Super-majority

    • Fist-of-five

    • Consent agenda

  • For more information please see page 7 of SILS Structure, Work Practices and Charges

  • Each campus plus CDL will have a single vote. During membership transitions there may be two representatives from a campus or CDL, however they will have one vote.

  • If there is a major objection from any member, the team may escalate a decision to the SILS Operations Team.

Collaboration Tools

  • Meetings will be held on Zoom. Zoom sessions will be recorded following a brief non-recorded time at the beginning of the meeting.

  • The SILS E-Resources Operations Subteam listserv, SILS-ERESOURCES-L@LISTSERV.UCOP.EDU, will be used for group communications

  • Slack will be used for one-on-one or private communications but is not preferred for group conversations due to the lack of archiving

  • Google Shared Drive will be used as our primary working space (spreadsheet, drafting documentation, etc.)

  • Confluence Wiki will be used for agendas, meeting notes, tracking decisions, tracking actions/tasks, publishing final drafts of charter, reports, etc.

  • Alma Sandboxes will be utilized when feasible to test new functionality, changes to workflows, etc.

Principles for Collaboration

  • Our interactions in the group will uphold our desire to have safe communication spaces

  • We acknowledge that discussions may become contentious, however we want to be transparent in our communication and avoid back-channeling

  • To ensure input from all members during meetings, we will use the Raise Hand function in Zoom as appropriate

  • Vice-Chair will take a poll of members to ascertain if an issue or concern under discussion affects each campus. This will help the SILS subteams to scope their work while supporting members with local issues.

Create a list of statements that the team agrees to uphold. For example, ask yourself: How do we make this group a safe space for transparent discussion (knowing that it might become contentious, and avoid back-channeling)? What are our ground rules for meetings? How do we ensure everyone is engaged? How do we ensure everyone has a voice? How will we resolve disagreements?

  • No labels