Bug 2441 - receiving more than 1 item
Summary: receiving more than 1 item
Status: CLOSED FIXED
Alias: None
Product: Koha
Classification: Unclassified
Component: Acquisitions (show other bugs)
Version: Main
Hardware: PC All
: P3 normal (vote)
Assignee: Chris Cormack
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-31 05:04 UTC by Paul Poulain
Modified: 2012-10-25 21:28 UTC (History)
0 users

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Cormack 2010-05-21 00:51:13 UTC


---- Reported by paul.poulain@biblibre.com 2008-07-31 05:04:23 ----

Previously, it was possible to enter the qty recieved.
now, it's limited to 1, and the value is READONLY.

Why ?

+ what's the use of the javascript + on the bottom left, to create more than 1 item on recieve ?



---- Additional Comments From paul.poulain@biblibre.com 2008-07-31 05:17:07 ----

I understand better now : the qty increase when you click on the + !

That's nice. Except for libraries that don't create the item during receive. (That makes 100% of our clients if I don't mind.)

Let me explain how it works in France :
- the "book buyer" create the order
- the "book reciever" open the parcel & empty it (& check that what is written on the vendor shipment paper is what is in the parcel
- the "equipment employee" add the barcode, the callnumber, some transparent protection things, the RFID or the 3M piece of anti-thievery.
- the book buyer (sometimes the 1st, sometimes a cataloger) create the item & complete the biblio.



---- Additional Comments From jmf@liblime.com 2008-08-09 05:20:38 ----

Without a barcode, no item is created, so this is fixed now.



--- Bug imported by chris@bigballofwax.co.nz 2010-05-21 00:51 UTC  ---

This bug was previously known as _bug_ 2441 at http://bugs.koha.org/cgi-bin/bugzilla3/show_bug.cgi?id=2441

Actual time not defined. Setting to 0.0
The original assignee of this bug does not have
   an account here. Reassigning to the default assignee
   for the component, chris@bigballofwax.co.nz.
   Previous assignee was rch@liblime.com.