Hello.
We’re looking at conducting a large-scale inventory for a consortium during the next year. The main goal of this project is to make sure what’s on the shelves matches what’s in the catalog. On my end, I’m not so concerned about the INVDA field being updated.
I know that there is the “classic” method of doing this where the files are uploaded via data exchange and then systems staff update the INVDA (inventory date) field via the Admin Corner.
If you’ve done it this way, what happens to items that are checked out when scanning the shelves? Would the INVDA field not be updated for these items?
This seems like it could become difficult to keep up with this if there is an onslaught of files from dozens and dozens of libraries to be updated by systems staff.
Instead of using the method above, I was considering having staff at each library scan the barcodes into a COUNT USE category not already in use. Then I was thinking about creating a list of items in that collection that don’t have a value in that COUNT USE field/aren’t checked out/billed etc. and they could look for the items/mark them as missing if needed.
Is there anything I’m missing with the latter method? It would be my preference to set this project up in a way that the staff at the member libraries could do this project independently without a need for the systems office to update things in Admin Corner for them.