It would be nice if there were a way to get full records for purchase suggestions - a replace via Z39.50 option maybe. Right now most libraries order from a batch given to them from a vendor or from a Z target to get full records, but if they do this then their orders aren't linked to the suggestions. The only way to keep the suggestion linked is to order from it and in essence a brief record. I don't have a good suggestion here, but thought I should share the idea in case someone else has a solution.
This is the very reason we do not order directly from purchase suggestions. Perhaps if there were an option to link from the suggestion to the MARC/order after it is downloaded(similar to the way an order is placed on an existing bib record?) or via a duplicate search when the download is staged?
Hi Sandre - thx for your comments! If you don't order from suggestions the 'ordered' and 'available' status can not be reached for the suggestion. Could it be a workaround to overlay the record with z39.50 after creating the order line?
That might work if you are not using EDI ordering, but if you are, then the record and the order are created at the same time when you download the file from the vendor. You need that information to send the order to the vendor through the ILS.
I am changing the title of this bug a little bit to make it stand out a bit more. If for some reason the 'order from suggestion' can't be used, like when ordering form as staged file or using EDI, there is currently no way for the suggestion to reach the Ordered or Available status and the patrons don't receive notifications. I think it would be nice if you could link an order to a suggestion after it has been created to fix this. If the order is status new or ordered the suggestion is moved to ordered. If the order is available already, it's moved to available. Notifications are generated according to status. This workflow would also help if there are multiple suggestions for the same record.
*** This bug has been marked as a duplicate of bug 19358 ***
*** Bug 1887 has been marked as a duplicate of this bug. ***