10/06/2026
In Aeon 7 you can see who has a request open, what they changed, and the moment they let it go.
Katie Gillespie ran the fourth Aeon 7 webinar with two browser windows side by side, signed in as two different staff members, to show exactly what two people working the same queue see. Five things worth knowing:
• A record lock now does what the Request in Processing queue used to do — and tells you more. The desktop client moved a request into that queue while someone had it open, then moved it back. Aeon 7 leaves the status where it belongs and names the person instead, so you know who to go and ask • Editing and routing are separate decisions now. A saved field change leaves the request exactly where it is, so you can correct a record without committing it to the next step. Routing is its own deliberate action when you're ready • Locks look after themselves. Aeon takes the lock the moment you change a field and releases it when you save. Idle for five minutes and you get a countdown with the option to keep it; about a minute later it releases on its own. Close your laptop and it clears after roughly thirty seconds • You're never looking at a stale record. A viewing indicator shows who has the request open, stacked if several people do, and the moment a colleague saves you get a note telling you what they changed • Batch process columns are yours to set. Title, call number, photoduplication status, scheduled date — pick what's useful and leave out what isn't. This one came in through customer feedback.
Recordings and registration for next webinar in the first comment 👇