2020-03-30

Owned by Emma Boettcher
Last updated: Mar 30, 2020
4 min read

Agenda

  • Introductions/group logistics
  • Permissions: decide granularity of permissions
    • Could a user have permissions to change an item's item status but not otherwise edit the item record?
    • Could a user have permissions to change item's item status to status X, but not to status Y? (and another user have permissions to change an item's item status to status X and to status Y?)
    • Could a user have permissions to change an item's item status from status X, but not from status Y? (And another user have permissions to change an item's item status from status X and from status Y?
  • Wrap-up & next week

Notes

  • Erin agreed to notetake for this first meeting - we will go in rotation.

  • Communication - Emma is fine with email. Slack can be a bit hit or miss for subject matter librarians. Susan - email preferred. Erin - Slack is good for discussions, esp. between meetings, and people may come in and ask questions, esp. people who are not on the calls.

  • Emma will check and make sure all the group members are added to Slack.

  • Group page in App Interaction SIG (2020 Item status (item state) subgroup - focused on availability) has a list of various topics that will be coming up.

  • Emma - Start by talking about improving what's already there, as well as features that need to come (like custom item status, three-part item status, etc.)

  • Erin - It will be important to keep groups informed that you are a member of.

  • Charlotte - can you give a list of the current version of the documents and background that you have right now? Help to not have to search in Google Drive, esp. since we might inadvertently find older documents.

  • Erin - so maybe we should be intentional about communicating back to the SIGs we're on. Do we have the right SIG membership?

  • Emma - POs said that MM, RM and RA were most important and that's who we have.

  • Christie - what is the scope of the item status discussion? There are various grand plans, things that we traditionally use item state for that are planned for different elements that aren't implemented yet. Knowing the scope will help us understand more and figure out how to respond to these areas.

  • Emma - not sure if the scope is really defined beyond things like, missing, on order, etc.

  • Christie - so we have items that are outside of a circulation focused understanding. Things like remote storage, shared print, binding, copy cataloging.

  • David - for binding, we loan them to a dummy user.

  • Christie - we manually update item states all the time.

  • Erin - shared link to a resource that she and Emma worked on - https://folio-org.atlassian.net/wiki/display/FOLIOtips/Item+State+in+FOLIO

  • Emma - might be more a way of defining this as representing staff workflows in item state, as a scope statement

  • Christie - there aren't really item states for managing the physical item lifecycle - like withdrawn to shared print. A part of the item state discussion needs to help us understand what we need to do. UChicago is implementing in December and we don't think we can do what we need to do.

  • Emma - I'd like for us to talk about circulation scope and physical item work together, as enormous as that  might be.

  • Erin - so maybe we need to step back and really do an introduction to where we're at. Laura - yes. We need to know more about the existing model before we can talk to permissions.

  • Christie - impact on discovery is really important. Historically we've used item state to deliver really granular information to the discovery layer for patrons.

  • Erin - exactly. And at Duke we've started looking at using locations for some of that instead of item state because item state isn't in the FOLIO circulation rules in the same way.

  • Emma - so one of the concerns is people that are implementing this year - what we essentially have is availability/item state and I don't want implementers
    this year to be left without any options.

  • Laura - it would really help to understand the longer term plan. Martina - I second this. Susan -  I agree.

  • Erin showed a slide deck that she used at Duke when introducing the three part model to Duke staff. Some of what Erin displayed is beyond what Emma had been thinking
    of - things like modifying requesting behavior. Very influenced by desire for a workflow engine. 

  • Christie - I like this model a lot and hope we can get there. But talking about the strategies for  workarounds would be helpful to, because we could identify gaps that need development.

  • David - a lot of what RA did was designed around the idea of the workflow engine.

  • Christie - we don't want to implement a workaround that we can't back out of when the real functionality is available.

  • Emma - so what do we need to know about item state to be able to go to other things? Example of things like workflow transitions - you may just want a transition to happen, rather than having to set a needed for and then checking something in.

  • Christie - so one of the workflows that we're thinking about are dummy items. And we use item state to indicate that it's a very specific type of thing, like
    analytics. Which we won't have by the time we go live. So our current state would work if we had an item state called "analytics."

  • Charlotte - could you use instance status instead?

  • David - this is about functionality that is meant to drive behavior on the discovery layer. May make Custom Item Status really important to UChicago as a workaround.

  • Erin - so maybe it's about this group developing some expertise that they can take to their SIGs to work on solutions that are needed.

Zoom

Recording

To-Dos

  • Emma Boettcher 
    • verify that members of team are added to item state slack channel
    • share with group inventory of current reference documents to use when understanding development
    • scope with individual schools their use of existing item states (perhaps share the Circ google doc that we worked on a while back?)