Please DO NOT add enhancement requests to this page. Please go to the CUL FOLIO Support Portal to submit your FOLIO enhancement request.
# | Date Reviewed | Title | Submitter | Description | JIRA | Status | 31||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
32 | 91/ | 1016/ | 21Additional index from Hosting | Laura Daniels | This is a service enhancement request. The ERM team needs to be able to search by url/domain name in the "electronic access" instance field in Inventory. This can be done using a simple query search (which I've confirmed in one of the folio dev environments) but in our Production environment this search times out. I tried pre-limiting the search by holdings location (serv,remo), but the query still timed out. So, I'm hoping we can request the electronic access field in instances get indexed. | 2018 | Invoice report (with bib data) | Holly Mistlebauer | At Cornell, this report is used by Accounting and Selectors. It is the "Approved Invoice Report by Invoice Date and Title." It includes invoice number, invoice status, invoice status (approval) date, invoice payment date, invoice line item id, ledger, subject, selector, fund, group, ledger (will show statutory or endowed) invoice line item note, order format date invoice was approved, budget group, donor, language, BIB_ID, Call Number, invoice line item description, and invoice amount. List approved invoices in a selected date range by selector, subject, fund and format. Partially fulfilled In-app. CU Med requires invoice date and invoice payment date. Main sort: PO line or Invoice Lines/Transactions For Cornell - need to add tags with tag filters. | REP-83 | Ticket :
| Grey
| new
Governance:
| review
FOLIO:
| review
| |||||||||||||||||||||||||||||||
| 30
| /6/21
| ||||||||||||||||||||||||||||||||||||||||||||
31 | 9/10/21 | Additional index from Hosting | Laura Daniels | This is a service enhancement request. The ERM team needs to be able to search by url/domain name in the "electronic access" instance field in Inventory. This can be done using a simple query search (which I've confirmed in one of the folio dev environments) but in our Production environment this search times out. I tried pre-limiting the search by holdings location (serv,remo), but the query still timed out. So, I'm hoping we can request the electronic access field in instances get indexed. | Ticket :
Governance:
FOLIO:
| |||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||
30 | 7/6/21 | Pop-up settings for service points | Wendy Wilcox | Settings so pop-up's can be enabled or disabled. In particular, the pop-up for a patron having a request available at the service point is needless. Most of the time that is literally why we have scanned the barcode in the first place. Also it is redundant when we are processing grab&go or remote programs. | UXPROD-3482 | Ticket :
Governance:
| Pop-up settings for service points | Wendy Wilcox | Settings so pop-up's can be enabled or disabled. In particular, the pop-up for a patron having a request available at the service point is needless. Most of the time that is literally why we have scanned the barcode in the first place. Also it is redundant when we are processing grab&go or remote programs. | |||||||||||||||||||||||||||||||||||||
Status | ||||||||||||||||||||||||||||||||||||||||||||||
colour | Grey | |||||||||||||||||||||||||||||||||||||||||||||
title | new | |||||||||||||||||||||||||||||||||||||||||||||
Status | ||||||||||||||||||||||||||||||||||||||||||||||
colour | Grey | |||||||||||||||||||||||||||||||||||||||||||||
title | review | |||||||||||||||||||||||||||||||||||||||||||||
Status | ||||||||||||||||||||||||||||||||||||||||||||||
title | review |
Expand |
---|
Functional Area:Service points, Circulation Notes: |
Delete invoice lines but not invoices
We’d like a separate permission for deleting invoice lines. A hidden permission does exist (Invoice - delete an existing Invoice line), so staff will try that out. Jean Pajerek says: "it’s one thing to let people edit invoices and invoice lines, but it is quite another to allow them to delete invoices altogether. This is something staff outside of the finance office were never allowed to do in Voyager. I feel the more granular hidden permission is what’s called for here."
I poked around issues.folio.org but don't see that this has been requested yet.
Amy
Ticket :
Governance:
Status | ||||
---|---|---|---|---|
|
FOLIO:
Status | ||||
---|---|---|---|---|
|
Expand |
---|
Functional Area:InvoicesService points, Circulation Notes:8-9-2022: Linked JIRA to the issue. |
Delete invoice lines but not invoices
We’d like a separate permission for deleting invoice lines. A hidden permission does exist (Invoice - delete an existing Invoice line), so staff will try that out. Jean Pajerek says: "it’s one thing to let people edit invoices and invoice lines, but it is quite another to allow them to delete invoices altogether. This is something staff outside of the finance office were never allowed to do in Voyager. I feel the more granular hidden permission is what’s called for here."
I poked around issues.folio.org but don't see that this has been requested yet.
Amy
Ticket :
Status | ||||||
---|---|---|---|---|---|---|
|
Overview:
The lack of the Caption column on the Unreceive screen makes it very difficult for staff to know which item they wish to unreceive when there are multiple items on an order. See attached screenshots.
Scenarios:
- Scenario
- Given user Selects a receiving title in receiving app
- When user opens full screen unreceive view
- Then table includes a column for Caption that appears after Barcode column
Ticket :
Status | ||||
---|---|---|---|---|
|
Governance:
Status | ||||||
---|---|---|---|---|---|---|
|
FOLIO:
Status | ||||||
---|---|---|---|---|---|---|
|
Expand |
---|
Functional Area:InventoryInvoices Notes:
8-9-2022: This is also mentioned in the TS review. I cannot find any open JIRAs for this issue. Possible related JIRAs: |
Overview:
The lack of the Caption column on the Unreceive screen makes it very difficult for staff to know which item they wish to unreceive when there are multiple items on an order. See attached screenshots.
Scenarios:
- Scenario
- Given user Selects a receiving title in receiving app
- When user opens full screen unreceive view
- Then table includes a column for Caption that appears after Barcode column
Morning Glory
Ticket :
Status | ||||||
---|---|---|---|---|---|---|
|
Governance:
Status | ||||||
---|---|---|---|---|---|---|
|
FOLIO:
Status | ||||||
---|---|---|---|---|---|---|
|
Laura Daniels has some thoughts on this.
Ticket :
Governance:
FOLIO:
Expand |
---|
Functional Area:Inventory Notes: |
|
|
|
Laura Daniels has some thoughts on this.
Morning Glory
Ticket :
Status | ||||||
---|---|---|---|---|---|---|
|
Governance:
Status | ||||||
---|---|---|---|---|---|---|
|
FOLIO:
Status | ||||||
---|---|---|---|---|---|---|
|
Expand |
---|
Functional Area:Inventory Notes: |
* EHoldings, title record in a package: there are the three "loading" dots, which may be where proxy or no proxy shows up? This also happens in the edit view. If we can't see what is set for proxy, we can't adjust it either.
* Also the Holdings (Coverage settings) used to show up on this screen and now maybe they would if we had custom coverage, but really seeing what our holdings are is very important, and having to go in 2 levels to access is kind of a bummer.
* If we had our druthers Coverage dates (custom and default) would show up on the long list of available packages* (see last screen shot, below) - that would save a lot of time for us, this may already be in the queue of wishes for future versions
* EHoldings, title record in a package: there are the three "loading" dots, which may be where proxy or no proxy shows up? This also happens in the edit view. If we can't see what is set for proxy, we can't adjust it either.
* Also the Holdings (Coverage settings) used to show up on this screen and now maybe they would if we had custom coverage, but really seeing what our holdings are is very important, and having to go in 2 levels to access is kind of a bummer.
* If we had our druthers Coverage dates (custom and default) would show up on the long list of available packages* (see last screen shot, below) - that would save a lot of time for us, this may already be in the queue of wishes for future versions.
Ticket :
Governance:
FOLIO:
Expand |
---|
Functional Area:RA Notes:
|
A work around is to select all and then deselect the ones you do not want renewed.
It would be nice to be able to only select the ones you would like to renew.
Ticket :
Status | ||||||
---|---|---|---|---|---|---|
|
Governance:
Status | ||||||
---|---|---|---|---|---|---|
|
FOLIO:
Status | ||||
---|---|---|---|---|
|
Expand |
---|
Functional Area:RA Notes: |
|
A work around is to select all and then deselect the ones you do not want renewed.
It would be nice to be able to only select the ones you would like to renew
Ticket :
Status | ||||||
---|---|---|---|---|---|---|
|
Governance:
Status | ||||||
---|---|---|---|---|---|---|
|
FOLIO:
Status | ||||||
---|---|---|---|---|---|---|
|
Expand |
---|
Functional Area:LDP / ReportingRA Notes:8-9-2022: This sounds like the FOLIO Notes app; Selectors would need edit permissions in FOLIO and then training (highlight NOT deleting other notes). We can make a "Selectors Notes" field. Connect with Emma to set up/trainLoop in Sharon / Vandana for reporting No JIRAs found one may have to be created |
Ticket :
Status | ||||||
---|---|---|---|---|---|---|
|
Governance:
Status | ||||
---|---|---|---|---|
|
FOLIO:
Status | colour | Yellow|
---|---|---|
|
Expand |
---|
Functional Area: UXLDP / UIReporting Notes:This sounds like the FOLIO Notes app; Selectors would need edit permissions in FOLIO and then training (highlight NOT deleting other notes). We can make a "Selectors Notes" field. Connect with Emma to set up/train |
Ticket :
Status | ||||
---|---|---|---|---|
|
Governance:
Status | ||||
---|---|---|---|---|
|
FOLIO:
Status | |||
---|---|---|---|
|
|
|
Expand |
---|
Functional Area:InventoryUX/UI Notes:1/6/2022 Update: Ask Jesse to bring to Product Council the need for a dedicated for PO for Item State. Charlotte can partner with Laura and Andy to further describe. 7-27-2022: FOLIO currently does not have a PO for Item States. Charlotte is an interim PO but that means that no new features can be added only bug fixes. |
Ticket :
Status | ||||
---|---|---|---|---|
|
Governance:
Status | ||||
---|---|---|---|---|
|
FOLIO:
Status | ||||
---|---|---|---|---|
|
Expand |
---|
Functional Area:Inventory Notes:1/6/2022 Update: Ask Jesse to bring to Product Council the need for a dedicated for PO for Item State. Charlotte can partner with Laura and Andy to further describe. 7-27-2022: FOLIO currently does not have a PO for Item States. Charlotte is an interim PO but that means that no new features can be added only bug fixes. |
The ability to sort by LC call number at the Holdings record level
Thank you very much for considering this request. (PS - I've also brought this up to Angela Zoss as a critical need for reporting.) - Joanne
The ability to sort by LC call number at the Holdings record level
Thank you very much for considering this request. (PS - I've also brought this up to Angela Zoss as a critical need for reporting.) - Joanne
Ticket :
Status | ||||
---|---|---|---|---|
|
Governance:
Status | ||||
---|---|---|---|---|
|
FOLIO:
Expand |
---|
Functional Area:Inventory / MM Notes:1/5/2022 update: Holly says this is a Bug, not a new feature, and had moved it to Support. |
Ticket :
Status | ||||
---|---|---|---|---|
|
Governance:
Status | ||||
---|---|---|---|---|
|
FOLIO:
Status | ||||||
---|---|---|---|---|---|---|
|
Expand |
---|
Functional Area:RAInventory / MM Notes:When submitting phrase request as "add a text field" or add a "note" 1/5/2022 update: Holly says this is a Bug, not a new feature, and had moved it to Support. |
Thanks!
Andy Horbal
Ticket :
Status | ||||
---|---|---|---|---|
|
Governance:
Status | ||||
---|---|---|---|---|
|
FOLIO:
Status | ||||||
---|---|---|---|---|---|---|
|
Expand |
---|
Functional Area:RA Notes:Details in the TDX |
Jenn Colt Joanne Leary
Michael Cook
A feature request for FOLIO where we ask for the circulation count of an item in FOLIO to appear on the item record so it is easily accessible rather than needing to be calculated in LDP or inferred from the circulation log. See Michael’s use case below
A data request for Cornell that we pull circulation counts from the Voyager snapshot and add them to a note on the item in FOLIO. This could be either a new note type or a generic note type with contextual information. I think Joanne and I could work together on making sure the right information gets into the note but it will be a few days process to get all the information in over the API, and it seemed like a large enough endeavor that we should maybe ask steering to way in (now that weWhen submitting phrase request as "add a text field" or add a "note" |
Thanks!
Andy Horbal
Ticket :
Status | ||||
---|---|---|---|---|
|
Governance:
Status | ||||
---|---|---|---|---|
|
FOLIO:
Status | ||||||
---|---|---|---|---|---|---|
|
Expand |
---|
Functional Area:RA Notes:Details in the TDX |
Jenn Colt Joanne Leary
Michael Cook
A feature request for FOLIO where we ask for the circulation count of an item in FOLIO to appear on the item record so it is easily accessible rather than needing to be calculated in LDP or inferred from the circulation log. See Michael’s use case below
A data request for Cornell that we pull circulation counts from the Voyager snapshot and add them to a note on the item in FOLIO. This could be either a new note type or a generic note type with contextual information. I think Joanne and I could work together on making sure the right information gets into the note but it will be a few days process to get all the information in over the API, and it seemed like a large enough endeavor that we should maybe ask steering to way in (now that we are post-migration).
Use case from Michael Cook on Slack: so this info is not/will not be available at a glance via the item record as it was in Voyager. That’s going to be more work for selectors, as we often get questions/situations with materials where being able to see past circ patterns with the item in question is crucial to the decision making process. An example is that I was recently offered a donation of the second volume of a 2-volume set of a mono title (we lack the 2nd volume). I don’t know if there was enough interest (i.e. circ history) in vol. 1 to merit adding vol. 2 to the collection. Without a way to see that history, I can’t make an informed decision. In this case and given the staffing shortages in LTS I will turn down the offer, but this kind of thing happens all the time. Circ history is an important data point that should be readily available to selectors if at all possible without having to run reports. Dunno if that’s possible in Folio but thanks for considering!
Ticket :
Status | |||
---|---|---|---|
|
|
|
Governance:
Status | ||||
---|---|---|---|---|
|
FOLIO:
Status | ||||||
---|---|---|---|---|---|---|
|
Expand |
---|
Functional Area:LDP Notes:Internal dev - not FOLIO dev Vandana will check in with Sharon on whether or not this could be a report. Jenn/Joanne - give the green light |
8/ |
2/2022 update: ticket can be closed:
|
When you are in inventory on the item record, when you create a new request
on the item (done a lot for new books), can you have the requester
information automatically have the name or net id rather than the barcode?
It would save an additional step since LTS does not collect patron barcodes
and we have to do the additional click for "requester look-up".
We process holds for new books multiple times per day and it would make
things much easier to not have this additional step.
Ticket :
Status | ||||||
---|---|---|---|---|---|---|
|
Governance:
Status | |||
---|---|---|---|
|
When you are in inventory on the item record, when you create a new request
on the item (done a lot for new books), can you have the requesterinformation automatically have the name or net id rather than the barcode?
It would save an additional step since LTS does not collect patron barcodes
and we have to do the additional click for "requester look-up".
We process holds for new books multiple times per day and it would make
things much easier to not have this additional step.
Ticket :
Governance:
Status | ||||
---|---|---|---|---|
|
FOLIO:
Status | ||||||
---|---|---|---|---|---|---|
|
Expand |
---|
Functional Area:RA, Requests app Notes:Andy will write up - precedent in Users app in Note from Laura: in the Metadata Management SIG we specifically asked not to have identifying information display in the item in Inventory. This was based on concerns about user privacy. It would be great if this display could depend on a user's permissions. |
Ticket :
Status | ||||||
---|---|---|---|---|---|---|
|
Governance:
Status | ||||||
---|---|---|---|---|---|---|
|
FOLIO:
Status | ||||||
---|---|---|---|---|---|---|
|
Expand |
---|
Functional Area:Inventory Notes:"space" should be considered as a category, not a literal character, e.g., leading and trailing carriage returns & tabs should also be ignored SUBMIT as BUG - Changed to a NEW FEATURE |
Ticket :
Status | |||||
---|---|---|---|---|---|
|
|
Governance:
Status | |||
---|---|---|---|
|
|
|
FOLIO:
Status | |||||
---|---|---|---|---|---|
|
|
Expand |
---|
Functional Area:Inventory Notes:Update 1/05/2022: POSSIBLY Complete in KIWI - need to confirm with Laura Update: confirmed that ElasticSearch will address this problem. So we should prioritize https://issues.folio.org/browse/UXPROD-3046 (already ranked "R1" by Cornell) Cyrillic But Icelandic characters are not affected: |
This happens regularly at Olin because of the faculty and graduate students who have items checked out to their studies and carrels who then wish to take the items home with them.
Ticket :
Status | ||||||
---|---|---|---|---|---|---|
|
Governance:
Status | ||||||
---|---|---|---|---|---|---|
|
FOLIO:
Status | ||||||
---|---|---|---|---|---|---|
|
Status | ||||||
---|---|---|---|---|---|---|
|
Expand |
---|
Functional Area:RA Notes: |
The print pop-up should not queue if the print box setting is disabled. For high volume libraries, these additional clicks slow down our processing time which doesn't matter now but during peak times will be very problematic.
We need to make pop-ups a setting that can be turned on and off by
service point. There are entirely too many pop-ups that are unnecessary
and slows processing time down. In addition, the print pop-up should not
queue if the print box setting is disabled. For high volume libraries,
these additional clicks slow down our processing time which doesn't matter
now but during peak times will be very problematic.
Ticket :
Status | ||||||
---|---|---|---|---|---|---|
|
Governance:
Status | ||||||
---|---|---|---|---|---|---|
|
FOLIO:
Status | ||||||
---|---|---|---|---|---|---|
|
Expand |
---|
Functional Area:RA Notes:Existing JIRA for this issue, added to this request. |
Wendy Wilcox
Caitlin Mathes
We need to be able to view requests by effective location (which I assume feeds from the permanent and temporary locations). It is impossible to see how many pending requests are in the queue when you have staff moving on and off the desk and the only way we can view open requests by location
(not service point) is to print preview. We currently have to schedule call slips so that we don't mistakenly reprint request slips. Also, sorting by service point is not useful at all since that is where the book is being delivered, not where the book needs to be pulled from.
Ticket :
Status | ||||||
---|---|---|---|---|---|---|
|
Governance:
Status | ||||||
---|---|---|---|---|---|---|
|
FOLIO:
Status | ||||||
---|---|---|---|---|---|---|
|
Expand |
---|
Functional Area:RA Notes: |
Functional Area:
RA
Notes:
Expand |
---|
Functional Area:RA Notes:
|
Ticket :
Governance:
FOLIO:
Expand |
---|
Functional Area:RA Notes:
|
Ticket :
Governance:
FOLIO:
|
Ticket :
Status | ||||||
---|---|---|---|---|---|---|
|
Governance:
Status | ||||||
---|---|---|---|---|---|---|
|
FOLIO:
Status | ||||||
---|---|---|---|---|---|---|
|
Expand |
---|
Functional Area:raRA Notes:
|
Ticket :
Status | |||
---|---|---|---|
|
|
|
Governance:
Status | |||
---|---|---|---|
|
|
|
FOLIO:
Status | |||
---|---|---|---|
|
|
|
Expand |
---|
Functional Area:ra Notes:
Edge APIs, Intergrations Notes:
|
Wendy Wilcox
Ticket :
Status | ||||||
---|---|---|---|---|---|---|
|
Governance:
Status | ||||||
---|---|---|---|---|---|---|
|
FOLIO:
Status | ||||||
---|---|---|---|---|---|---|
|
Expand |
---|
Functional Area:ra Notes:
|
From the Old Support Page:
| ||||||||||||||||||||||||||||||
2 | 7/22/2021 | Close pop-up using the Enter key | Bethany Silfer | Ability to close a pop-up by pressing the Enter key. Current methods are: mouse click over to close button and clicking close or by pressing the Esc key | UXPROD-3212 | Ticket :
Governance:
FOLIO:
| ||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||
1 | 7/22/2021 | Disable pop-up upon check-out | Bethany Silfter Wendy Wilcox | Ability to disable the pop-up that appears upon checkout anytime a patron has an outstanding request such as a page request. Configure by service point. | UXPROD-3160 | Ticket :
Governance:
FOLIO:
| ||||||||||||||||||||||||
|