Check for duplicate orders

12

When ordering items found through the Evergreen catalog, the system should alert you if you have already ordered a particular title. The system does let you know if you previously ordered a title, but I'm keeping the development idea here in case we want to see changes in how this works. When you find a title in the catalog and select  View/Place orders, you will see a list of line items that you have already ordered (if any.) In the below example, this particular title had been ordered twice through two separate PO's. The screen displays the price and status of the order and also provides a direct link to the PO. You also have the option to add the title to a selection list or PO if you want to order additional copies.

 

Category

Status: 
In the attic

Comments

Re: Check for duplicate orders

Moderator

I’m wondering if there are two pieces to this development.  

  • Provide a check for a PO Name that exists
  • Provide a check whereby when activating an order a lookup of the catalog would be performed based on UPC or ISBN and report back if there is a copy in the system for the given library.  Details about how this would be handled need to be worked out but we certainly don’t want to block an order just because a duplicate ISBN or UPC was found.  There might be other matching criteria used or even a match profile from vandelay.

Re: Check for duplicate orders

Moderator

I like having a warning for re-using a PO Name.

I'm not convinced that I want any other warning/prevention mechanism.  We certainly don't want individual pop-ups or over-rides, and I feel like acquisitions is finally getting to a workable speed, so I hesitate to add in too much extra looking up to bog down that system.

-Alex

Re: Check for duplicate orders

Moderator

Duplicate PO names already have an entry here (http://masslnc.cwmars.org/node/3022)

Re: Check for duplicate orders

Moderator

Alex,

Are you concerned about some kind of duplicate check slowing the system down?  Having a popup that you would have to click through?  Or a combination of problems.

Re: Check for duplicate orders

Moderator

I'm wondering if the check for duplicate copies should look something like this so it does not siginificantly interfere with workflow.   It could be as when the bib record is loaded and matched, it will display the number of copies in the system for the given library.  

Re: Check for duplicate orders

Moderator

Exactly, Tim,

I am concerned about slowing the system down -- various acquisitions tasks (loading records, PO loading, invoice loading, fund loading...) are slow, and I'm not convinced that an extra check for a rare occurrence is worth slowing tasks down.

Also, the thought of clicking through pop-ups makes me crazy.  It makes me think about when, in Item Status, I accidentally load in a file of barcodes that includes a number of items already deleted and then I have this nightmareish experience of sirens and pop-ups as the system warns me that the items aren't in the system.  blech!

Listening to the one detailed use case, I feel like the duplicate PO name check might be enough.

I do like your suggestion of including (X copies owned) to the line items.  My one concern is defining the owning library to include.  It doesn't really concern me, at a single-branch library, but I wonder about getting it configured just right for other situations.

-Alex

Re: Check for duplicate orders

I recently placed an order for a third copy of The Goldfinch and, as expected using a gridded vendor cart and not the View/Place Orders option, nothing indicated I'd done so before.  This visual looks like a great addition.  Perhaps anything other than 0 copies could be in red?

Re: Check for duplicate orders

Moderator

Eileeen, I can write specs that way.

Re: Check for duplicate orders

Moderator

I like this approach, but when writing the specs I would add something about doing it in such a way that does not slow down performance. This looks like one of those areas where retrieving the copy information could cause a hit on performance, but if you include something in the specs, then my hope is they would do it in such a way that it does not cause a performance hit. 

Also, you would want to be very specific about when copies should display here. The multi-branch scenario Alex raised is a good one. Do we want to see copy counts for all those branches or does it need to be broken down? Should lost and missing copies count towards the totals? 

Re: Check for duplicate orders

Moderator

In the draft of specs, one thing I did was write

 

·         The system should provide the number of copies in the lineitem already owned by the ordering agency or its children before the order is activated.  If the number is greater than zero then the number would be indicated in bold red font.

 

I think I'll be specific about the missing and lost copies also.  I do have general language in the RFQ that all development should not impact performance but I could but it here also.

Re: Check for duplicate orders

Moderator

C/W MARS has funded development on this idea for completion in Fall 2014.

Re: Check for duplicate orders

Moderator

Moving this idea to the attic. C/W MARS has funded development and the code has been posted for community review. We expect it to be available in the next (after 2.7) release of Evergreen.