2021-06-17 Acquisitions Group Meeting Notes

Attendees

Ann Crowley

Ann-Marie Breaux (Deactivated)

Dennis Bridges

diane.cannon

Dung-Lan Chen

Heather McMillan

Jackie Magagnosc

Jean Pajerek

Julie R. Stauffer

@Katy Kazee

Kimberly Pamplin

Martina Schildt

@Masayo Uchiyama

Michael Phillips

Natalya Pikulik

@Okay Okechukwu 

Rachel Sneed

Scott Perry

Scott Stangroom

Shannon Burke

Shyama Agrawal

susan.martin@mtsu.edu

@Suzanne Mangrum

Suzette Caneda

Tatjana Clemens

Tracy L Patton

tbethard

Discussion items

Minute taker

@Heather Thoele


Agenda 


        • Continue to discuss order renewal integration details and what data is most valuable to update.
          •  First Question:  about updating the fund and publisher by vendor system. 


        • Discuss EDIFACT order export. This refers to  UXPROD-531 - Export FOLIO orders in EDIFACT format DRAFT  which has been identified as a very high priority in the community pointing exercises. We will review a proposed workflow for EDIFACT orders based on previous discussion and revisit use cases to be sure nothing has been missed

        HOMEWORK: review Export FOLIO orders in EDIFACT format and review cases. 

         

  Housekeeping

 susan.martin@mtsu.edu

Please attend RM Sig tomorrow. Discussion will be brought forward about the future of the RM SIG. May deactivate RM SIG and raise the status of this group to full SIG. May also change the time this group meets. 

Meeting structure in this group will change a little. Will have more homework. 

8:30 Eastern Time

https://zoom.us/j/675766727
 

Export FOLIO orders in EDIFACT formatVideo 7 Minutes after

Export FOLIO orders in EDIFACT format

Wants to make sure we have specific use cases to support requirements. 

Need to be able to send orders in different formats for different organizations. 

For an organization that you have an EDI connection with, you might also send PDF's.

Are there use cases for CSV files? Some organizations will have an automated roll up of orders into a spreadsheet. Are they vendors you might have EDI connection with? Or is that a separate thing?

    • Martina Schildt: To me that is a separate thing. 

If you have different accounts on an organization, they may need to be treated differently when it comes to EDI. 

Natalya: With Harrassowitz will have three different vendor address. 

Ann-Marie: Right now EDI is not using the envelope address for anything. 

Dennis: If you have multiple institutions, are you expecting to have separate organizations records?

  • Yes. 

Dennis: Different libraries within an institution may be sending EDI files to the same organization. They need to know which institution is sending it so it gets invoiced and shipped to the correct location. 

So it's possible that you will open orders in the morning, then realize before the file has been sent, that one of the orders has the wrong vendor. In order to correct this they will edit the order and intercept the file before it is uploaded to the Vendors FTP location. 

Use case An institution has multiple libraries there will be different pickup and drop-off directories for the EDI files. Meaning two separate EDI files would be uploaded to two separate directories or two separate FTP locations. One for main library and one for Law. 

Some accounts with different envelope addresses (Library EDI Codes) may be included on the same EDI file or the library may need to have them exported on separate files. 

Dennis: Is there anything to indicate that there needs to be two separate files? Or do you need the choice?

  • Ann-Marie, not sure.  For Gobi, If they hit the same drop off folder, they will be considered the same entity. 
  • Dennis: We need to flesh this out a little more. We need some way to chop things up based on account. 

44 minutes after: We need to be able to decide that an order should be exported after it's been opened.  

Dung-Lan, In voyager, the EDI file to our vendor is at the po level, not at the po line level. So if a po has ten po's, there is only one file sent to the vendor. Currently YBP is the only vendor integrated with Folio for this. Will a brief record come back into folio, then we send it to Gobi to confirm the order? Where is the duplicate check process happening? Our selectors may not check properly to make sure there isn't a duplicate.

Ann-Marie: EDI ordering is not going to be just Gobi. It will be any vendor that can accept it. Currently it's just Gobi, but any vendor that can receive EDIfact orders can receive them. 

If order button is pressed in GOBI, then duplicate checking is happening in Gobi. 

Dennis: On the folio side, there is not yet an automated duplicate checking function. 

Dung-Lan = Do most libraries currently using Gobi, do they use Gobi with selectors making the order, then Gobi would check to see if the library owns it?

Ann-Marie - For Gobi, Gobi gets more orders directly from the Gobi system rather than from an EDI from the library. Some libraries allow the selectors to make selectors, then someone from the library's acquisitions will of a duplicate check before the order button is pressed. 

Scott Perry: In Git Hub there is a link for a duplicate check report in the LDP. 

Dennis: If the order is closed. is there an expectation that you want to send the order out?

  • no, we would make a new copy of the order. 

Ann-Marie - there is a resend at the bottom.