Inventory Task Force - Another Potential Solution

Hi Folks – I’ve also posted this on the blog

I want to run past what I think the requirements are for inventory – does anyone disagree with these, or have any others to add?

1. Provide a comparison between the scanned barcodes and the items in the catalog for that call number range and identify discrepancies.
2. Support a variety of devices that a library may have available and not require specialized equipment that is used only for inventory. Supported devices should include any device that store barcodes in an ASCII text file which can be transferred to a PC.
3. Allow you to inventory a contiguous range of call numbers of any size.
4. Not require a live wireless connection to the staff network, since this is not available in all places in all libraries. Even if there is wireless coverage in the library, it may not extend to all areas of the stacks.
5. Not require extensive training for staff members conducting the physical scanning or running the reports.
6. Not require a major investment either for the libraries or eiNetwork.

Requirements #4 (wireless) and #6 (cost) eliminate Innovative’s wireless workstation product. I’ve had an opportunity to get feedback on tests of the existing telnet based Millennium Inventory module, and I’m thinking that it doesn’t meet requirement #5 for ease of use. There’s also an issue with requirement #3 because there’s a limit of 5,000 items that can be inventoried at any one time.

I’d like to suggest another potential solution, and that is to develop a small application in MS Access for inventory. This application would import a shelf list that is extracted from a review file, along with a text file of the scanned barcodes. These files could then be used to generate shelf list reports and comparison reports. There would be a standard application, but if a library has staff that works with MS Access, it could easily be customized. I have a prototype of this application available. If anyone would like to try it, please let me know. I would at least like to get you opinion on whether you think this is worth pursuing.

This is a link to the procedure for the prototype

This is a link to all the inventory task force documentation - current recommendation drafts, procedures, inventory procedures at other libraries

Regards

June

Inventory Reports Questions

I’m thinking about inventory requirements in two major categories – requirements for conducting the inventory itself, and requirements for the reports that the inventory produces.   

As far as the inventory itself goes, I think the following requirements are pretty clear.       Do you folks agree with these?

1. Support a variety of portable devices: i.e. scanners, laptops, RFID readers.   Anything that can store barcodes in a text file.


2. Allow you to inventory a contiguous range of call numbers of any size.


3. Should not require a live wireless connection to the staff network, since this is not available in all places in all libraries.   Even if there is wireless coverage in the library, it may not extend to all areas of the stacks.


4. Should provide a comparison between the scanned barcodes and the items in the catalog for that call number range and identify discrepancies

As far as a report “package” that would be produced from the inventory process, I’m less clear on what’s needed.    Here’s my questions:

1. If the inventory find items that are on the shelf, but have a status other than available, do you want to
   
   1. Fix it on the spot
   
   
   2. Review an error report, and then go back and fix it.


2. For items that have incorrect status codes, would want
   
   1. A total count of all the items with incorrect status codes
   
   
   2. A breakdown by status code (i.e. 6 missing items were found on the shelf, 2 claims returned items, and 2 in transit items)
   
   
   3. A breakdown by status code, along with the specific titles involved.


3. For misshelved or out of place items, would you want to
   
   1. Fix it on the spot
   
   
   2. Review an error report, and then go back and fix it.


4. What kind of circulation statistics, if any, should be included in the reports?


5. Should any kind of age information (i.e. item create date, cat date, publish date) be included in the reports?


6. Should any other item related information be included in the reports?

Inventory Task Force Recommendations Ver 1 - Please Comment

Hi Folks. This is the first draft of recommendations for the Steering Committee, based on yesterday's meeting. I would like to be able to present something at the December 20 Steering Committee meeting.

Inventory Task Force Recommendations Draft

Inventory Survey Results - Final

We've had 37 responses to the survey, which I think is very good. I've posted a summary of the results at this link:



http://member.einetwork.net/member/ils/inventorytf/SurveySummary.html

Inventory Survey

One of the things I want to do to start is to create a consortium wide survey using survey monkey. This survey would ask about current inventory practices, problems, and needs. Here are some of the questions, do you have any others?

1. Do you currently do some kind of collection inventory?
2. How often do you do inventory?
3. Do you have a written procedure that you could share?
4. What is your primary purpose in doing inventory? Look for missing items? Weeding? Value of Collection? Collection Development?
5. If you don't currently do inventory, why not?
6. Do you use any special equipment for inventory?
7. Do you use any special reports? How do you use those reports?
8. Do you use any software other than Millennium for you inventory?