Page Comparison

Meeting details

...

• Continue with last week's questions

Notes

1. If items have different locations from their holdings, should the holding location change based on items? For one item with a different location, and for items with multiple locations?
   • Ask MM/MM - clean up issue
   • Wouldn't happen by default, especially with temporary locations
   • Institutional decision about own workflow for when they change item and holding data
     • Duke wants source of truth for where resources are stored to be holding
   • FOLIO inherits from holdings down to item
   • Not something to happen in remote storage workflow with Dematic
2. When we change a location to remote storage it is the permanent location, can that location be changed again
   • Yes, deaccession process
3. Accession queue setting
   • Rare, but not a regular change
   • Should be allowed, but won't be a regular occurrence
   • Permission for remote system configuration appropriate
4. How do we work around not having deaccession in the first implementation? What should happen if a user changes a remote storage location to a standard location in item or holding record?
   • Deaccession is a more intricate process - David (Dematic)
     • Special code
     • Wouldn't be done on purpose
     • Doesn’t seem critical
   • Cammie (CaiaSoft)
     • People change accidentally, report says this location doesn't match
   • Jacquie
     • Similar exception report
   • Mary & David use access query to run report
   • Cammie don't want to withdraw item from library system unless item is physically in hand
   • Add confirmation popup: Are you sure you want to remove this item from remote storage?
     • If yes, run an exception report or communicate this to Remote storage location, this includes x number of titles
     • Cancel
   • Retrieval process future state?

After answering questions above, group talked through Configuration settings, commented within Vision document

Artefacts

...