Review a question related to EDIFACT claiming (Joseph Reimers)
Joe wants feedback
Use export manager to handle export
Any objection to changing the job type from edifax orders export to EDI orders because it’s an EDI file ,which is a specific job type of job. Claiming will be parts of orders.
Dennis Bridges 8:06 AM Just for contrast what about Orders (EDIFACT) and Orders (CSV) anyone have any thoughts?
Discussion on how this functionality will work for orders and claiming.
To see the difference between an order and a claim, filter on different integration type.
There is silence from the group so no strong opinions. If anyone has thoughts on alternative language, leave feedback in slack.
:15
Dennis hasn’t created a slide deck for the UAT feedback on on credit values.
No showstoppers
2 users not able to complete test, but overwhelming majority was able too.
There were a few suggested enhancement, but overall happy with functionality.
Dennis will finish the slide deck and post it on the UAT page.
Looking for ideas on how to fill time in meeting as we are getting towards the end of implementers topics.
Maybe have a ‘lab’ where people bring questions?
Martina Schildt 8:33 AM I like your idea @Dung-Lan Chen.
Often when people ask questions in slack, don’t always see anyone respond. Owen said that a po can answer in theory, but people that are using the system having that discussion help the developers see if there is something they are missing and need to fix.
Kimberly Smith (MTSU) 8:35 AM I think when we ask, it is good to know what the intent was behind the development.
Owen Stephens 8:37 AM Absolutely - I don’t mean to discourage that - for me the more communication the better But I often feel that people feel shy of sharing their experience because they don’t feel like they are the ‘expert’ or that their experience doesn’t apply more generally - and I’d encourage everyone to share their experiences because we all learn from this
:42
Susie Skowronek
Major sticking point for them is reporting
How are others handling reporting in acquisitions?
Right now relying on the CSV exports in orders and invoices then manipulating those in excel.
Ann Crowley 8:43 AM At Cornell we use LDP and are converting to metadb
Lisa Smith, Mich State 8:43 AM We are doing the same, Susie. We also have a couple API reports that were created to help us with fund balance info.
Owen Stephens 8:44 AM The new Lists app may also cover some gaps
Scott Perry: Many are using LD Light, but if you have a large dataset LD light probably wouldn’t work well since it’s hitting the API’s directly, but for small things it’ll work.
Owen Stephens 8:44 AM
LDLite doesn’t need a separate reporting solution - it queries the data in Folio directly. LDP / Metadb create a copy of the data specifically to support reporting LDP/Metadb include manipulation of the data to make reporting easier / more straightforward
Owen: Perhaps a starting point would be to list the top priority reports you need and for what purpose (maybe on the Slack channel) and then we can get feedback from sites with different reporting solutions / skill sets as to how they do that?
Lisa Smith, Mich State 8:48 AM Our Library technology folks created our Acq API reports for us.
Q release will have a lot of updates in the List App.
Kristin Martin 8:50 AM Yes, that focused on new functionality on Lists app
Owen Stephens 8:52 AM Sorry it was CalTech that developed the Goolge Docs reporting pluging And there is also a document on linking Folio to Excel for reporting
Owen Stephens 8:55 AM I know Peter Murray is working
Ann Crowley to Everyone 8:55 AM You are seeing the beginning
Owen Stephens to Everyone 8:56 AM I think they will go on the OpenLibraryFoundation YT channel (as WOLFCon is for all OLF projects not just FOLIO) https://www.youtube.com/@OpenLibraryFoundation