2020-07-13

Attendees:

Emma Boettcher Christie Thomas David Bottorff Susan Ponischil Martina Schildt Laura E Daniels(notetaker)

Agenda

• Questions & concerns from RA & RM SIGs
  • Ability to add Needed for during Orders workflow
  • Printing Needed for at Check In
    • Emma will work with Darcy (PO) on this
  • Only showing Needed for when Check In is at home location?
    • Not universally wanted
    • Idea is, would be first routed to home location (availability - in transit), only when checked in at home location Needed for would show up – assumption is that the Needed for process would not happen outside of home location, this will not necessarily always be the case – do need a way, for instance, to indicate which reserves processing unit something needs to go to
    • Are there any advantages to this?
      • None identified, some disadvantages – might obscure useful information
      • Unless "needed for" processes "know" physically where the process happens, this would create problems (David)
• Data import
  • Update records: differences from changing item status on item record
    • On order (can't change an item status from On order on item record, Data Import proposes it be allowed)
      • Ability to bypass receiving process is needed in cases where full cataloging comes from vendor (common across multiple institutions) – this is why we need to be able to update item status from on order via Data Import
    • Paged, Awaiting delivery, Awaiting pickup (on item record, can change item status from these values; Data Import proposes it be disallowed)
  • Create records
    • Limitations on whether records can be created with item status X? – different for individual item creation and batch (import)
    • Not the same as those for changing status to for individual items
    • "On order" should not be allowed (as status for item created in Inventory). In general changes to and from "on order" need to be in sync with orders app; in many cases, item records are not created until a piece is received, items created in Acquisitions (with "in process" status)
    • But through Data Import, items can be created with "On order" status
    • Emma will pass this info on to Ann-Marie (PO for Data Import)
• Item statuses for dummy intellectual records (i.e. items that don't represent a real object)
  
  • custom item statuses, configured so they can't be requested, checked out, etc.?
  • not requiring item status on all item records?
  • could there be an item status that corresponds to "dummy," "intellectual items" e.g., "this is not a real item."
    • analytics & bound-withs;
    • collections such as microfiche, where individual pieces are only barcoded if they are requested via ILL;
    • shared print repository (users have access, but the piece is physically in another library's collection).
  • Using item state for this purpose makes the meaning of these "intellectual items" clearer. Also, we don't want item states associated with real, physical items associated with these types of items.
  • how is item state, in this case, different from material type? would this be another way to represent intellectual items?
  • in many cases, these types of items still need to be requestable, but the request processes may be different (some refer to actual physical things, some refer tangentially to physical things
  • Item status is the most powerful way of controlling behavior, but different states would be needed for different types of intellectual items, based on desired behavior
  • If custom item state is how we plan to represent these materials, then custom item states are required for go-live
  • having an "intellectual item" state could be a thin thread solution (customizable item states will take longer to develop)we don't want other workarounds/solutions to compete with item state for managing these resources – so we might need not to require item state (if customizable states will not be available by go-live)

Notes

No major concerns from RA & RM SIGs. MM update will happen next week.

Zoom

Zoom recording

Action items