2021-06-25 Acquisitions Group Meeting Notes

Minute taker

@Heather Thoele

Agenda

• Housekeeping
• Updates 
• Report from the Product Council 
• BugFest 
• Continue the discussion around the updates to the EDIFACT workflow (orders)

Susan Martin

Links need to be different for Tuesday and Friday meetings

Tuesdays will be https://zoom.us/j/353648867

Friday's links will be https://zoom.us/j/675766727

Will meet every other Friday to stay in sync with sprint cycles. 

Kristin Martin

Product council updates. 

Shared revised structure with product council. 

Community has changed and grown. 

Main areas of concern from Product Council. 

• Don't want to lose track of the overview of Resource Management
• Managing print serials, or managing serials in general. 
  • Virginia: Serials can fall under Acquisitions 
• Kristin started updating the 'about' information for the SIG's in the wiki
  • This should help show how folio is proving a holistic view. 
• Alexis: Wants to make sure sure Acquisitions will not become more  print focused?
  • • Susan: It will not. There are several people that attend ERM and other SIGs to bring that information into the group. 
  • From chat: Owen Stephens to Everyone:  08:16 AM
    I’d completely back that up. We’ve always tried to be clear that the Agreements + Licenses app are not doing the things that Orders and Invoices does. There are some boundary issues of course - and I think those are inevitable and have to be tackled. 
  • Kristin: Receiving is a print function. Everything else is holistic. 
  • Also have to deal with a 9 hour time span for everyone that wants to participate in these synchronous meetings. 
  • Sara C: Owen comes to the Friday meeting regularly, can we have someone from MM attend the Tuesday meetings? That is where I have the biggest challenges related to serials right now.  The bridge from Acq to inventory is not one I understand well. 
    • Kristin: Will chat about getting liaisons between the SIG's, 
  • Sara C: IN the Friday's meetings we had started having the implementers wiki page on how to handle Acquisitions? How will that be managed now?
    • Susan: Still working things out, that is a good point.  Let us know about things like this so we can keep working on it. 
    • Sara C: So if we have things to add, feel free to add?
    • Susan: Yes, and let us know if there is anything else you want to add to discussions for the meetings. 
  • From Owen Stephens to Everyone:  08:24 AM
    In ERM we’ve tried to mix up the implementers issues and presentations with feature discussions which I think has worked well. Personally I’d love to have more presentations by implementers but I recognize that this is a lot of prep work for those presenting
• Dennis: From PO perspective, not sure how to handle the transition from Tuesday's Acq meetings to Friday's Acq meetings. Need to play with this a bit, but having this be an Acquisitions meeting with a more collaborative conversation will be good. 
  • Discussion about the links between POL's and inventory have been ongoing. Now time to start testing. 
  • From Susan Martin to Everyone:  08:26 AM
    If anyone here has implemented and wishes to share their workflows around a particular point, let me know.  :-)
    From Owen Stephens to Everyone:  08:29 AM
    I’m really pleased to be able to be attending a regular Acq focused meeting - from my perspective it gives me more confidence we can work on the Acq/ERM cross-over aspects
    From Me to Everyone:  08:29 AM
    And me!
  • From Dung-Lan Chen to Everyone:  08:29 AM
    Really looking forward to expanded functionalities that are planned for Kiwi release for Receiving app that will address a lot of print serials receiving issues currently exist in juggling between Receiving & Inventory apps.  Thanks to Dennis and those involved in the discussions earlier of use cases regarding receiving print serials, etc.!!  I wanted to set up our workflows in anticipating what's going to be available down the road.

Bug Fest R2 2021 Juniper

Bugfest starts Monday.  June 21

Claim test cases June 21-27

Bug Fest June 28-July 9

Bug Fixing July 12-23

Re Juniper release become GA August 2, 

Test rail: PO's have created test cases, step by step guide for testing a case. 

People go into Test Rail you claim a test. If someone has already claimed a test, you can still run it. You just don't assign that test case to yourself and you can add your results to that test. 

Challenge in Bug Fest: How to maintain a large enough data set with reasonable information you can do something with. So we carried over all the data from IRIS to Juniper for testing.  If you participate in Bugfest and working in the finance app, please start by creating a new structure. You will see your previous record, but he will try to edit them so they appear further down the list. 

From Kristin Martin (she/her) to Everyone:  08:33 AM If someone doesn't have a testrail 
From Susan Martin to Everyone:  08:33 AM Good question.
From Julie Brannon (she/her) to Everyone:  08:34 AM To request testrail access send a slack message to Anton Emelianov and he'll get you setup!
From Susan Martin to Everyone:  08:34 AM +1
From Kristin Martin (she/her) to Everyone:  08:35 AM @julie, should I send him names of staff members who might be able to participate? Some of them don't have FOLIO slack accounts.
From Susan Martin to Everyone:  08:35 AM I'd like to know that as well.
From Julie Brannon (she/her) to Everyone:  08:35 AM I think he just needs names and an email address to get them setup

If you have not logged in to test rail within 6 months, you need another log in. 

39 minutes after: Demonstrated how to get to test rail 

Here's a video about hos to claim a test case: https://folio-org.atlassian.net/wiki/download/attachments/3441752/claim_test_case_1.mp4?version=1&modificationDate=1591644723000&api=v2
From Robert rscheier@nelib.org to Everyone:  08:40 AM https://folio-org.atlassian.net/wiki/display/FTC/Helpful+Resources

There is a page for videos here: Helpful Resources 

From Julie Brannon (she/her) to Everyone:  08:43 AM
Helpful tip:  When you are looking at the list of folders (seen on the bottom right of Dennis' screen) you may not see all of folders listed - you can't scroll through them all.  If this is this case for you, a message will display at the bottom "815 more tests available. Switch to compact view to see all tests."  You'll want to click the compact view hyperlink to expand the list to all folders.

From Robert rscheier@nelib.org to Everyone:  08:44 AM
Anton also mentioned to please not to take a claimed test from someone else
From Owen Stephens to Everyone:  08:45 AM
One of the things that the product owners have raised about the test rail process is that it can be helpful for multiple people run the same tests
And this isn’t obvious in the Test Rail interface - but as Dennis says, you can just go in a do a test and file a result

There are a couple of topics being discussed at this part of the life cycle. Just verifying information and looking at these features for an upcoming release. 

Exporting orders in edifact format. This has been highly ranked by institutions. 

Also talking about order renewal integrations. Started with the Ebsconet system. Identifying what information needs to be updated. 

UX PROD 184 - Create orders and link order lines to materials in the knowledge base.  This topic will start next week in App interaction. And again in our Friday time slot. 

Export FOLIO orders in EDIFACT format

Export FOLIO orders in EDIfact . Last requirement we haven't discussed in detail is the idea that you may need to resend the file. 

What happens if something goes wrong with the upload and the user needs to resend the original file? Or if you want to edit the order?

There are a few mocks for interacting with the EDIfact files.  

Does this proposed flow meet your needs? Would you ever need to do this for more than one vendor at a time? 

There isn't much time left, so feel free to answer in the slack channel or join us Tuesday's meeting. 

Dennis: If you have feedback or it's difficult to follow along in this new format please share it with us.