Enhancement Request: added feature or functionality requiring developer time to complete
Process for Enhancement Requests
Request is added to the form below
LSIS reviews list and assigns a Product Owner on a regular basis
Product Owner contacts Requestor to get more information, if needed
Product Owner brings details to LSP Steering Group for prioritization
Product Owner works with agile team to develop enhancement
# | Enhancement Idea | Requestor | Submission Date |
---|---|---|---|
1 | Hide the fines section on the My Accounts page if the patron has no fine transactions |
| |
2 | Display the total debit/credit on top of page if patron owes library money or has credit amount |
| |
3 | Remove authority record URLs from author field on My Accounts page |
| |
4 | Incorporate Scan and Deliver functionality for Rubenstein - e.g., allow a request scan for Rubenstein that goes into their scanning workflows |
| |
5 | Improve handling of analyzed set records in CRS when they appear |
| |
6 | Integrate “Patron card will expire soon” messaging into CRS |
| |
7 | Limit pickup location to owning sublibrary in cases where that is part of the requesting rules |
| |
8 | Migrate FOLIO ERM Organization Contacts and Interfaces to Alma. Already documented as a sub-project of the Alma Integration Project. |
| |
9 | Migrate Aleph Order/Subscription Log Notes to Alma Orders. Already documented as a sub-project of the Alma Integration Project. |
| |
10 | Update orders that were migrated from Aleph to add order reporting codes, if possible.
|
| |
11 | Migrate notes on tracked resources in 360 to Alma - we track owning library in 360 note and that data didn’t migrate to Alma. |
|