[FOLIO-870] Integrate Equipment Loan Form (ELF) with Check-Out app. Created: 29/Sep/17  Updated: 18/Jan/22

Status: Open
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Task Priority: P3
Reporter: Peter Murray Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: 2 hours, 45 minutes
Original estimate: Not Specified

Attachments: PDF File EBSCO-interim-report-hoot-elf-march-30.pdf    
Sprint:

 Description   

High-level ticket for tracking the integration of Illinois' Equipment Loan Form with FOLIO for their EBSCO Innovation Grant work.



 Comments   
Comment by Peter Murray [ 29/Sep/17 ]

From email thread.

On Sep 29, 2017, 3:49 PM -0400, Hahn, Jim <jimhahn@illinois.edu>, wrote:

We've had some very high level implementation questions about how to integrate our Equipment Loan Form (ELF) into FOLIO. Our broad question is related to ELF – 1) should we implement an app/module in FOLIO, or 2) was the expectation really that we would somehow be adding code changes directly to the Circulation Module.

We understand from the recent Resource IG report that there are design patterns for Circulation that are being iterated on, so we wondered if it made more sense to have the Equipment Loan Form be implemented as a new module that depends on the Circulation Module.

On Sep 29, 2017, 5:05 PM -0400, Peter Murray <peter@indexdata.com>, wrote:

Thanks for checking in. We talked a little bit about this during the Montreal tech meeting last week. Our current thinking is that the ELF should be a separate module that will be triggered by a loan rule executing. We're not entirely set on how that trigger will happen – and how much manual intervention will be needed in the functionality being developed for version 1 – but starting with the ELF as a stand-alone module (e.g. not something embedded in the existing check-out app) gives us the most flexibility.

Jakub Skoczen and Cate Boerema – can you help me figure out how to help Illinois start to map this out?

Comment by Jakub Skoczen [ 02/Oct/17 ]

Peter Murray can you provide more details? How/when should ELF get displayed?

Comment by Peter Murray [ 03/Oct/17 ]

In their current workflow, the ELF would be displayed after the item barcode was scanned as part of the loan-out process. In Montreal we talked about using the emerging workflow mechanism for this, but there were objections about how we didn't want workflows to throw pop-ups as a potential for bad UX design down the line. The compromised talked about at the time was to put an unobtrusive message at the bottom of the screen with a link to the ELF app. The thought was that since the operator would be checking out a piece of equipment they would know to find the link to the ELF app and that pop-up dialog box wasn't needed.

Jim Hahn and Nathaniel Ryckman – feel free to chime in on the ticket!

Comment by Jim Hahn [ 05/Oct/17 ]

We have been using an ELF in the UIUC Undergraduate Library for almost 2 years now. It creates special agreement loan forms for circulating, renewing, and discharging technology items in a busy media commons.

Our observation is definitely in line with the use case described, the circulation staff are aware that the items they are scanning are a special type of loan. Therefore, I think that the unobtrusive message at the bottom of the screen would work nicely for special types of loans.

We are loaning everything from cameras to laptops to projectors and presentation equipment ( https://www.library.illinois.edu/mc/lt/ ) . Recently we extended the functionality to be able to loan out the keys to an audio recording studio ( https://www.library.illinois.edu/mc/studios/ ).

I do have a question about the FOLIO circulation app: is there going to be functionality that allows booking an item of equipment in advance? In my Voyager experience, these have been processed under "short loans" where circulation staff can basically reserve a camera or other technology in advance for a patron so that the user can pick it up in the future. It has been the case that the technology loans get quite a few advance bookings on them that we have a special web app (separate from the ELF app) to show when loanable technologies are booked in the future, which helps desk staff see available slots for advance bookings. This was done to address shortcomings in how the ILS we have displayed short-loans at copy levels not the broader equipment level.

  • Jim H.
Comment by Peter Murray [ 20/Oct/17 ]

Thanks for posting this, Jim – and I apologize for the long delay in getting some comments back to you. Knowing that a simple notification message on the screen will be enough certainly helps with the integration at this stage.

I do have a question about the FOLIO circulation app: is there going to be functionality that allows booking an item of equipment in advance?

To the best of my knowledge, there has not been a discussion of being able to book an item in advance. It does seem closely related to the holds functionality, so I'm going to loop Cate Boerema and Tania Fersenheim (product owners) into the conversation as well as Darcy Branchini (user experience designer). Andrea Loigman is the convener of the Resource Access SIG, so I'm adding her as well.

Comment by Peter Murray [ 08/Apr/18 ]

Posting the Interim report from Univ of Illinois from Jim Hahn, Nathaniel Ryckman and Benjamin Ryckman.

Comment by Nathaniel Ryckman [ 17/Apr/18 ]

Resources

Below are links to the repositories we have uploaded along with demo videos that demo and explain each piece of software that we have uploaded.

Demos Videos

elf.mov
waitlist.mov
folio-config.mov

ELF Repositories

mod-elf
db-elf
ui-elf

Waitlist Repositories

mod-waitlist
db-waitlist
ui-waitlist

FOLIO Config Repositories

folio-docs
folio-config

Peter Murray, Jim Hahn

Comment by Andrew Nagy [ 18/Jan/22 ]

Cheryl Malmborg Is this something that could be looked at by the Circulation group to determine if this is still feasible or is something that is no longer valid? Its a feature that was developed many years ago and never was implemented into the code base. I think this has gone into a black hole because there is no assignee.

Generated at Thu Feb 08 23:08:56 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.