Announcements/PC Updates - See notes from PC's last meeting
- Looking for BugFest QA volunteers
- More MVP/capacity planning results to come out in next couple of weeks
- WOLFcon: Save the date, Jan. 22-24, 2020 at Texas A&M University, College Station Texas
| Kristin Martin | - PC Meeting Highlights: Anton Emilianov, QA manager with EBSCO, is looking for volunteers to be bug testers. He's looking for up to 40 people to manually test workflows in FOLIO (this is on top of the automated testing that's done). Commitment on this involves a bug test every six weeks, the first happening after the next release which is scheduled for mid-September. The expectation is that testers will dedicate two solid days for testing and preferably testers will make a commitment to be available for each bug test over the course of a year. Testers do not have to be involved with SIGs.
- FOLIO Stakeholders Meeting: Attendees discussed MVP planning. It is anticipated the the capacity planning group will be wrapping up their work in the next couple of weeks.There was also some discussion around the future of OLE as Michael Winkler is retiring.
- WOLFCon will be held at Texas A&M University in College Station, Texas January 22-24. The conference will have a similar format to the previous WOLFCon meeting held in Durham rather than strictly a working meeting like the face-to-face recently held in Washington, D.C.
- The containers subgroup, led by Charlotte Whitt and Laura Wright, has met twice to discuss how containers will work within inventory. The group includes members from several SIGs including metadata management and resource management. They are looking at use cases and it seems that containers will work for some but perhaps not all. If you have use cases or questions, please send them to Virginia. There is not yet a wiki page for the group, they're working through Slack.
- A metadata export group is being formed. It is primarily focused on working through an export epic JIRA that is scoped to the Inventory app. The ERM apps have import/export functionality for the purpose of discovery. It would be good to document use cases for acquisitions though if needed, there would need to be some discussion as to whether this would fall within the scope of the existing epic in JIRA or if another one would be needed. Some of the use cases might be taken care of by the Library Data Platform (LDP) which should be in the MVP. It was suggested that we ask someone from the Reporting SIG to provide an update at a future RM SIG meeting.
|
Acquisitions - Questions/unresolved issues from renewals/ongoing orders/encumbrances
- Demo of work done on orders, including: order templates
- Discuss the updates proposed for the ordering of packages
| Dennis Bridges | - Orders/renewal information:
- The lingering question from last week's meeting is whether it's necessary to have the renewal information in the order record. Since much of the work in the area of ordering has been done by the small acquisitions working group, there is confusion in the RM SIG as to how it all works together. After much discussion, it was decided that the next three RM SIG meetings will be dedicated to working through the renewals. Kristin will look for documentation that we've developed in this area.
- Order templates:
- Order templates can be created by going to: Settings → Orders → Order Templates
- About templates:
- There are not required fields in the template but when you are using a template to create an order, you will be prompted to complete all required fields.
- Templates can have different prefixes/suffixes.
- Bill to/ship to information can be set in Settings → Tennant → Addresses
|