FYRO discussions currently planned for this Friday, May 24, at 9 am Eastern
Business -
Joe has a list of features (both acq-sig-topics and other community contributed topics) they’d like to start discussing. Clean and prioritize feature backlog & more information - the first of a series of meetings on this (Acquisitions POs)
 Discussion topics
Time
Item
Presenter
Notes
Time
Item
Presenter
Notes
:01
Â
Â
Housekeeping -
FYRO discussions currently planned for this Friday, May 24, at 9 am Eastern
Possible aspects to consider/include in FYRO discussions
Experience sharing if you've done FYRO recently (how did it go, things others should take notes, etc.)
Preparation/cleanup work you do prior to running FYRO
Discuss encumbrances for "Ongoing Orders" (how it's handled in your library, pros & cons, etc.)
How long does it take for FYRO to complete (number of ledgers you have, the size/amount of orders to be rolled over, etc.)
Other questions regarding FYRO
We can continue with a second meeting to discuss FYRO in June if needed
Clean and prioritize feature backlog & more information - the first of a series of meetings on this (Acquisitions POs)
UAT for routing slips will be June 3rd
There is a list of features in Jira that haven’t been assigned yet
Would like to look at features and get feedback. Are they still relevant, how important are they, may need additional feedback…. Not all are necessarily ACQ SIG topics, but all will benefit from this SIF.
Â
:06
Â
Â
UXPROD-1527
Orders APP: Idea that within the orders app, users can search knowledge base to add a resource to a PO or PO Line. It would mirror the integration between Inventory and the Order.
Kristin: Right now we can do that from the agreement line.
Joe: Safe to say we do not need to need to do this?
It’s not talking about linking to the agreement line, if you don’t have it in inventory, only in the KB, it would pull the information from the knowledge base into Inventory.
Joe, so this is something that would be nice to have, but not impeding any workflows.
In Europe it seems more common to push orders from orders to vendors, where in the US we are the opposite. How does Europe?
Susanne Gill: Right now we use Sunrise from OCLC.
Sara: How do you get it into your pol?
Susanne: It’s part of the sunrise script
Sabrina: There is an API between our union catalog and the library system.
Sara: Can we broaden the access points so we have direct integrations to orders from different sources?
Joe: Looks like there is additional analysis to reframe the question based on what we discussed. Will give it an AcqSig tag to get it on the list of things to vote on.
Joe: Forgot to mention, in the validated column are features that we have already identified as things we are going to do.
Joe: We are not ready to assign releases to these, but don’t want to lose track of them.
:24
Â
Â
Suspend or delay orders;
Orders that are interrupted by unforeseen circumstances. Order is not cancelled. But postponed to a future fiscal year, or changing receive dates….
Kimberly Smith: I think the ability to post orders against future fiscal years would meet the needs of our library for what we need. This would allow us to suspend an order or delay until the following fiscal year would be the biggest use case.
Martina: This is probably no longer a thing. Because this was talking about the codex and the ability to search across multiple apps.
Lisa Smith - preorder searching is harder in folio than previous ILS. Especially in the Orders App. So improvements in searching is needed, but not necessarily solved by this feature.
Sara: You can change the model, but the Keyword says it includes all (UUID. HRID…) but it doesn’t.
Joe: There is interest in this and we will look at more closely.
:38
Â
Â
UXPROD-2390
Finance Fund Type usage information
User would like to delete a fund type but can't because it’s being used by one or more funds but it’s not clear how many funds a leveraging this fund type.
Aaron: Looks like the need here is to be able to deprecate a fund type. Ability to suppress, but not remove from the system to avoid the complexities of the referential
integrity of deleting a bunch of things that have a value that shouldn’t be deleted.