2020-06-12 Meeting notes

 Announcements/Updates

• Product Council Meeting 2020-06-11
  • Dracine Hodges - PC Chair-Elect
  • EBSCO updates on next year development and involvement
  • SIG updates
  • Documentation process from Marcia Borensztajn

Questions on EBSCO updates:

• what does that mean, e.g. as Dennis Bridges is an EBSCO employee - does that mean ACQ dev will be focused only on EBSCO customer's needs
• why should SMEs from institutions that are not EBSCO customers give input to SIGs and Subgroup's dev
• Folio so far has been a joint effort
• Kristin will take the question back to PC
• how can we as community make sure that we are not just sticking to our quarterly features, but invest to make the system as a whole work
• who is picking up overarching questions
• App interaction is an important part in bringing the whole system together and addressing overarching questions
• needs more weight
• EBSCO customers like 5C want to stay contributing to the community; hear that the first time in this meeting and will enquire with EBSCO
• EBSCO invested a lot
• time that SMEs spend is payed time as well; that is valuable contribution as well; some libraries have POs in Folio
• community needs to mature and act independantly from the big players but together with the big players
• we have a common goal
• thoughts will be brought back to the PC - Kirstin will take care as co-chair

Chat:

Von Owen Stephens an alle: 02:48 PM
I think its also important to consider the question of what the role of the product manager is vs who pays for them Sorry - product owner, not manager
Von Kirstin Kemner-Heek an alle: 02:48 PM
@Owen: +1
Von Owen Stephens an alle: 02:48 PM
So the role of PO needs to be clear so that people can fulfil that role to the benefit of the whole community not matter who pays their wage
Von Virginia Martin an alle: 02:48 PM
yes, thank you for articulating that so well, Owen

• in the middle of preparing Q2 release
• invoices can relate to orders but don't need to
• invoice settings → vouchers: there one or multiple groups can be created
• in batch group configuration settings: batch export config can be set
• daily or weekly on on specific week days
• exports can be send to ftp location
• format needs to be chosen for export files (currently xml and JSON)
• more formats can be added; would need conversion from JSON
• password for accessing ftp server need to be set
• need to save settings for connection
• batch group appears on invoice
• if there is only one group there is no select list; if multiple groups the correct one can be chosen
• there will be a pending payment for anything on an approved invoice
• in this current release the automated export functionality is not included; in this release it will be manual; needed to be split
• everything since the last export is listed and can be exported
• payment of only parts of an order is possible; e.g. if only 1 of 3 copies is received; it is possible to only release parts of the encumbrance then
• question: can you bulk edit invoices as paid
• not at the moment, but invoices can be approved and paid in one click
• sometimes libraries need to approve and pay at different times
• invoices need to be toggles as "export to accounting" to be exported to accounting
• request: have a status before paid or automatically have the status changed to paid when the export is run
• status log on the invoice would be helpful; and a status log for the order as well
• helpful information on the invoice: which export file the invoice is in
• APIs for retrieving batch voucher files are in place

Chat: Von Julie Brannon an alle: 03:28 PM
Is there a way to display the date/time of when the export occurred on the invoice?
Von Virginia Martin an alle: 03:28 PM
oh good idea Julie!
Von scolglaz@mtholyoke.edu an alle: 03:28 PM
+1 Julie

Von Scott Perry an alle: 03:31 PM
I am hoping to have the flow for invoices be Saved ==> Reviewed ==> Approved (this covers our separation of duties issues) ==> Exported (confirmation received) ==> Paid for those invoices submitted via the direct feed.

Von Julie Brannon an alle: 03:35 PM
And if we have a resent capability in the future, it would help to see the date time for any resends as well.

Von Owen Stephens an alle: 03:36 PM
The main downside of JSON is the lack of tools to work with as a non-developer

UXPROD-2455

• orders general settings: order material type can be set
• controlled vocabulary; terms can be added and deleted (delete: as long as they are not used)
• request to be specific on labels

Chat: Von Julie Brannon an alle: 03:43 PM
+1 to sara's comment - we definitely need different labels for order material type and item material type
Von Jack Mulvaney an alle: 03:43 PM
Agreed
Von Kathleen Berry (she/her) an alle: 03:43 PM
YES

• order material type will appear in POL details
• one per POL; no need to multi select
• item material type will be handled under a separate feature
• defaults will be an option
• item material being optional will be a post mvp feature

UXPROD-2456

• order duplicate check
• please review and leave comments where necessary (via slack or JIRA)
• will need to be developed for 2 different ways: manual orders and batch processing orders
• how will this work for single vs multi tenants
• will need to be able to order another copy, there needs to a flag/warning
• how relevant is this feature; especially in relation to cross-app searching
• feature needs review