Hi Folks, i have an idea around a simple update-items.pl tool. my idea is a tool similar to circ's current branchtransfers.pl script (that takes scanned barcodes as input), and it updates the scanned item's various values what values ??? perhaps some/all of these... (any others??) Item Information 1. Home Library: 1. Holding Library: 2. Item type: 3. Collection: Statuses ( Lost Damaged ) 1. Current Location: 3. Lost Status: 4. Damaged Status: 5. Withdrawn: do other libraries use a different method that i'm unaware of? is there another update-items.pl type tool i have missed? Cheers, Mason
shelving location would also be helpful.. I thought there was some work coming for 3.2 already? or are you the one working on it! David Schuster Mason James-5 wrote:
Hi Folks,
i have an idea around a simple update-items.pl tool.
my idea is a tool similar to circ's current branchtransfers.pl script (that takes scanned barcodes as input), and it updates the scanned item's various values
what values ??? perhaps some/all of these... (any others??)
Item Information
1. Home Library: 1. Holding Library: 2. Item type: 3. Collection:
Statuses ( Lost Damaged )
1. Current Location: 3. Lost Status: 4. Damaged Status: 5. Withdrawn:
do other libraries use a different method that i'm unaware of? is there another update-items.pl type tool i have missed?
Cheers, Mason
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
-- View this message in context: http://www.nabble.com/a-simple-update-items.pl-tool-tp22694810p22714694.html Sent from the Koha - Dev mailing list archive at Nabble.com.
On 2009/03/26, at 2:49 PM, David Schuster wrote:
shelving location would also be helpful.. I thought there was some work coming for 3.2 already?
or are you the one working on it!
no, not until a few days ago ;) i cant recall from the dev-list if anyone else is working on the same tool currently?? its been an often requested and discussed tool though... and yes, shelving-location too! the main use for the update-tool would be for Circulation - to allow staff to bulk-update some boxes of items. - setting all items to STACK or MENDING, or - setting shelving location from '1st floor' to '3rd floor', etc with the same information/warnings that returning an item gives (items is lost, reserved etc)
David Schuster
Mason James-5 wrote:
Hi Folks,
i have an idea around a simple update-items.pl tool.
my idea is a tool similar to circ's current branchtransfers.pl script (that takes scanned barcodes as input), and it updates the scanned item's various values
what values ??? perhaps some/all of these... (any others??)
Item Information
1. Home Library: 1. Holding Library: 2. Item type: 3. Collection:
Statuses ( Lost Damaged )
1. Current Location: 3. Lost Status: 4. Damaged Status: 5. Withdrawn:
do other libraries use a different method that i'm unaware of? is there another update-items.pl type tool i have missed?
Cheers, Mason
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
-- View this message in context: http://www.nabble.com/a-simple-update- items.pl-tool-tp22694810p22714694.html Sent from the Koha - Dev mailing list archive at Nabble.com.
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
the main use for the update-tool would be for Circulation - to allow staff to bulk-update some boxes of items.
- setting all items to STACK or MENDING, or - setting shelving location from '1st floor' to '3rd floor', etc
Having this tool would be invaluable to my library, and would make options like "shelving location" truly useful, as we'd be able to change them quickly and easily. If I can help in any way to make it happen let me know, because I'd love to get to use it! -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org
Hi, WALDO is sponsoring development with LibLime for Bulk Status Changes and for Global Changes. The completion date for both is estimated to be December 15, 2009. We don't have written specs yet, so suggestions are welcome. If you can get something coded before then, go for it! Becky Becky Bell Open Source ILS Consultant Phone: (507) 720-0706 Phone: (800) 326-6495 Ext. 6 Fax: (914) 729-1985 beckybell@waldolib.org http://www.waldolib.org
-----Original Message-----
From: koha-devel-bounces@lists.koha.org [mailto:koha-devel-
bounces@lists.koha.org] On Behalf Of Mason James
Sent: Wednesday, March 25, 2009 9:25 PM
To: David Schuster
Cc: koha-devel@lists.koha.org
Subject: Re: [Koha-devel] a simple update-items.pl tool
On 2009/03/26, at 2:49 PM, David Schuster wrote:
shelving location would also be helpful.. I thought there was some
work
coming for 3.2 already?
or are you the one working on it!
no, not until a few days ago ;)
i cant recall from the dev-list if anyone else is working on the same
tool currently??
its been an often requested and discussed tool though...
and yes, shelving-location too!
the main use for the update-tool would be for Circulation - to allow
staff to bulk-update some boxes of items.
- setting all items to STACK or MENDING, or
- setting shelving location from '1st floor' to '3rd floor', etc
with the same information/warnings that returning an item gives
(items is lost, reserved etc)
David Schuster
Mason James-5 wrote:
Hi Folks,
i have an idea around a simple update-items.pl tool.
my idea is a tool similar to circ's current branchtransfers.pl script
(that takes scanned barcodes as input), and it updates the scanned
item's various values
what values ??? perhaps some/all of these... (any others??)
Item Information
1. Home Library:
1. Holding Library:
2. Item type:
3. Collection:
Statuses ( Lost Damaged )
1. Current Location:
3. Lost Status:
4. Damaged Status:
5. Withdrawn:
do other libraries use a different method that i'm unaware of?
is there another update-items.pl type tool i have missed?
Cheers, Mason
_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha.org
--
View this message in context: http://www.nabble.com/a-simple-update-
items.pl-tool-tp22694810p22714694.html
Sent from the Koha - Dev mailing list archive at Nabble.com.
_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha.org
_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha.org
__________ Information from ESET NOD32 Antivirus, version of virus
signature database 3965 (20090326) __________
The message was checked by ESET NOD32 Antivirus.
WALDO is sponsoring development with LibLime for Bulk Status Changes and for Global Changes.
Becky, does the spec for that match the description Mason gave? When I hear "bulk status changes" I think of status changes by batch, like by call number range or barcode range. I just want to make sure we're talking about the same thing. -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org
Owen, The description of the Bulk status changes describes the feature as "A batch of barcodes can be collected and then imported for a status change (e.g., recall by library, mark as not for loan, requires catalog maintenance)." The functionality required is the ability to collect a batch of barcodes of items that are affected and the ability to change the status of collected barcodes in one action. I looked back at Mason's description and believe that he and WALDO are thinking alike. Becky
-----Original Message----- From: Owen Leonard [mailto:oleonard@myacpl.org] Sent: Thursday, March 26, 2009 11:10 AM To: Becky Bell Cc: Mason James; David Schuster; koha-devel@lists.koha.org Subject: Re: [Koha-devel] a simple update-items.pl tool
WALDO is sponsoring development with LibLime for Bulk Status Changes and for Global Changes.
Becky, does the spec for that match the description Mason gave? When I hear "bulk status changes" I think of status changes by batch, like by call number range or barcode range. I just want to make sure we're talking about the same thing.
-- Owen
-- Web Developer Athens County Public Libraries http://www.myacpl.org
__________ Information from ESET NOD32 Antivirus, version of virus signature database 3965 (20090326) __________
The message was checked by ESET NOD32 Antivirus.
__________ Information from ESET NOD32 Antivirus, version of virus signature database 3966 (20090326) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com
The functionality required is the ability to collect a batch of barcodes of items that are affected and the ability to change the status of collected barcodes in one action. I looked back at Mason's description and believe that he and WALDO are thinking alike.
I think the key is his description "similar to circ's current branchtransfers.pl script." That means scanning each item individually with the updates happening in individually, rather than collecting barcodes in a batch for processing en masse. Does that sound right Mason? It may not have a functional difference as far as your requirements go, but I would hope that a "Bulk status change" feature would offer more than one way of building a batch, just like the inventory script gives you the option of choosing a call number range, barcode range, etc. That's just my idea of it though. -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org
On 2009/03/27, at 12:08 PM, Owen Leonard wrote:
The functionality required is the ability to collect a batch of barcodes of items that are affected and the ability to change the status of collected barcodes in one action. I looked back at Mason's description and believe that he and WALDO are thinking alike.
I think the key is his description "similar to circ's current branchtransfers.pl script." That means scanning each item individually with the updates happening in individually, rather than collecting barcodes in a batch for processing en masse. Does that sound right Mason?
It may not have a functional difference as far as your requirements go, but I would hope that a "Bulk status change" feature would offer more than one way of building a batch, just like the inventory script gives you the option of choosing a call number range, barcode range, etc. That's just my idea of it though.
hi Folks thanks for the feedback. down the track i can see the potential for the tool to be enhanced with add/mod/saving item-batches to run status-updates on, or uploading a text-file of barcodes, or selecting items using various fields and min/max ranges etc... but yes, at the moment ill keep the 1st draft nice and simple, and focus on it accepting scanned barcodes from Circ (like the branchtransfer.pl tool)
Mason James <mason.loves.sushi@...> writes:
On 2009/03/27, at 12:08 PM, Owen Leonard wrote: tential for the tool to be enhanced with add/mod/saving item-batches to run status-updates on, or uploading a text-file of barcodes, or selecting items using various fields and min/max ranges etc...
but yes, at the moment ill keep the 1st draft nice and simple, and focus on it accepting scanned barcodes from Circ (like the branchtransfer.pl tool)
Just an idea we could look at is how about modifying private virtual shelves to have this ability. This could be a switch when making a staff intranet shelf. This gives us a list we already have, and allows us to scan in barcodes. I have not recently looked, but does the virtual shelf save a biblionumber or an itemnumber. An itemnumber would be preferable as it contains more information since it is one to one for the biblio instead of one to many (bib to items). This covers the whole scanning and list making. Now we just need to add a checked option for "bulk update" or something like that which allows us to change the options that were specified like itype and location. So the interface could be as follows: Item 1 Item 2 ... Item n [previous][options] [bulk update] The bulk update would then open an interface below [location drop down] [itype drop down] [lost status drop down] [damaged status drop down] The benefit of using a virtual shelf it that they are persistent. If a library puts a list of items on display, generally they need a way to revert to their former locations, so they would need switched back. If they are already in a list then there is a way to do that. Items of similar itypes and locations could be kept in a list, with a different list for itype/ location or for whatever purposes. _______________________________________________ Koha-devel mailing list Koha-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/koha-devel
Shelves are biblio based, with good reason. The item may have "more" info, but it is quite possibly *wrong* info compared to the other items on the same biblio. In logic, the shelf listing resembles most closely the hit list returned from a search, except that it is composed by an individual rather than returned by Zebra. Importantly, the shelf should be able to represent titles where NO ITEM exists, and therefore cannot be item-based. Other than that, though, the workflow to add items to a list could very well accomodate barcode scanning in single or batch form. --Joe On Mar 31, 2009 8:24 AM, "Darrell Ulm" <darrellulm@smfpl.org> wrote: Mason James <mason.loves.sushi@...> writes: > On 2009/03/27, at 12:08 PM, Owen Leonard wrote: tential for the tool to be enhanced > with add/mod/saving item-batches to run status-updates on, >... Just an idea we could look at is how about modifying private virtual shelves to have this ability. This could be a switch when making a staff intranet shelf. This gives us a list we already have, and allows us to scan in barcodes. I have not recently looked, but does the virtual shelf save a biblionumber or an itemnumber. An itemnumber would be preferable as it contains more information since it is one to one for the biblio instead of one to many (bib to items). This covers the whole scanning and list making. Now we just need to add a checked option for "bulk update" or something like that which allows us to change the options that were specified like itype and location. So the interface could be as follows: Item 1 Item 2 ... Item n [previous][options] [bulk update] The bulk update would then open an interface below [location drop down] [itype drop down] [lost status drop down] [damaged status drop down] The benefit of using a virtual shelf it that they are persistent. If a library puts a list of items on display, generally they need a way to revert to their former locations, so they would need switched back. If they are already in a list then there is a way to do that. Items of similar itypes and locations could be kept in a list, with a different list for itype/ location or for whatever purposes. _______________________________________________ Koha-devel mailing list Koha-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/koha-devel
participants (6)
-
Becky Bell -
Darrell Ulm -
David Schuster -
Joe Atzberger -
Mason James -
Owen Leonard