acq:scenarios:ordering_monographs_consortial_model
Differences
This shows you the differences between two versions of the page.
acq:scenarios:ordering_monographs_consortial_model [2007/09/16 22:52] – created dbs | acq:scenarios:ordering_monographs_consortial_model [2022/02/10 13:34] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ======Problem scenario: Ordering monographs (consortial model)====== | ||
+ | (contributed by Don McMorris) | ||
+ | As many libraries were small, most would order through a central system account and the consortium headquarters would receive. | ||
+ | |||
+ | =====Actor: Member library staff===== | ||
+ | Create a purchase order. | ||
+ | bibliographic record (if there isn't one, an e-mail is sent to staff to | ||
+ | request a new record). | ||
+ | vendor via EDI. When records are released, new item/ | ||
+ | created. | ||
+ | |||
+ | =====Actor: Consortium HQ's Acquisitions staff===== | ||
+ | Supplier would box and ship items to consortium HQ. Staff would sort | ||
+ | items onto book trucks by PO number, and verify contents on packing | ||
+ | slips. | ||
+ | the purchase order, stamp and label the item, box the items up, and send | ||
+ | them (via courier) to the library that ordered them. | ||
+ | |||
+ | =====Actor: Member library staff===== | ||
+ | Staff gets the items in the delivery. | ||
+ | and link from the line item to the item record. | ||
+ | barcode to the book, and attach the barcode to the item record. | ||
+ | item would then be checked in (in terms of circulation) to trap any hold | ||
+ | requests and to automatically move the status from " | ||
+ | (or " | ||
+ | then be shelved. | ||
+ | |||
+ | =====Actor: EDI agent===== | ||
+ | Throughout the process, the EDI will handle some functions | ||
+ | automatically. | ||
+ | in the library' | ||
+ | HQ). When the vendor issues an invoice via EDI, the item will be changed | ||
+ | from " | ||
+ | sure). |