2018-06-15 Meeting Agenda & Notes

Date

Attendees

Agenda

TimeItemWhoNotes
5minFinal reportCarlos Rodriguez
  • Reminder to submit this in the next two weeks
  • Should be relatively brief – half a page, paragraph or two.
  • Will be released in July
5minTitle for Boundwith Host RecordsLuiz Mendes
  • Proposal from Resource Management
  • Discussed back in the Fall
  • Came from Fulfillment
  • Problem: From the patron record, bound-width resource shows the default title of the host bibliographic record.
    • Not very meaningful
  • Solution: Replace current title “Host bibliographic records for bound-with item barcode ****” with “Multiple titles bound as a single volume with the barcode ****"
  • Change should be made by the first week in July
  • Will share with Fulfillment open meeting
12minHand-off tasks to new chairbrandon dudley (Unlicensed)
  • We shared committee selections to COLD last week, asked them to inform their staff.
  • Will announce to everyone today.
  • Next two weeks, committees should package everything up
  • Ensure consistent hand-off for all committees changing chairs
  • Reach out to new members and chairs after Friday.
    • Make sure they are aware of projects that need to continue
    • Help them formulate agenda for next year
    • Make sure they know to solidify meeting schedule early
  • Think about what goals you want to set for next year
  • Summer conference
    • Current chairs asked to find speakers for the topics
    • Incoming chair should know about this to help
    • There is a time slot for an open meeting at the summer conference
      • Isn't a committee meeting as such
        • Almost everyone on the functional committees will be at the conference, however
      • Can be an open discussion for all practitioners in that area
    • No slot for a coordinating committee meeting, but is there interest?
      • Carlos offered to take everyone out to dinner – both outgoing and incoming chairs
      • There was general interest
5minMeeting schedule for next yearCarlos Rodriguez
  • Have met monthly on a Friday this past year for an hour, was that good?
    • Several conversations ran long, so maybe 90 mins
  • 90 mins monthly on Friday, 1-2:30 PM, tentatively accepted
  • Vice chair John will have a role
  • July meeting would be good as a prep for summer conference and hand-offs
    • Good to keep momentum going
30minPresentation at ALA Technical ServicesCarlos Rodriguez
  • Feedback on questions that Carlos sent out, if time
    • What do integration and collaboration mean in the context of your respective consortia? What strategies have been effective in achieving these goals?
    • What outcomes are desired for service delivery, work processes, and cost savings? How have these evolved over time?
    • What tensions have emerged between local needs/practices and standardization across the consortium, and how are these reconciled?
    • What thorny problems have you discovered in the shared environment, particularly around collections and technical services?
    • What opportunities and challenges are on the horizon?
  • Tech Services talked about this.  Carlos will chat with Luiz about all that.
  • David & Brandon also have some older presentations that touch on this.
  • Changes in workload and personnel vs. just policies?
    • Many campuses have 'democratized' configurations and tasks previously centered in systems staff
    • Working smarter or faster?
      • Efficiencies especially in ERM?
      • GOBI API has helped
        • Not unique to this project, but getting help from other campuses has made it easier to implement
      • Sacramento has recently undertaken some restructuring
        • Freed-up some time in cataloging, shifting to scholarly communication
      • Resource sharing a major new area
    • Authorities work in Alma a major area of interest from other institutions, but thorny
    • Collaboration has been a big outcome from the project
      • Much greater communication between the campuses
        • Slack has been a game changer
        • Weekly and monthly meetings online
      • APIs have given some creative individuals like Jeremy at SLO to create new tools
      • Putting aside local differences, especially in resource sharing
      • Being able to see into other people's data, especially in Analytics, has been useful
  • Are the staff thinking differently?
    • Committees have been encouraging folks to think about the consortium
    • Has led to some papers and conference presentations among CSU staff
  • Send any final insights to Carlos.