Defining Use Cases for Federating Library Services

I've attached a jpg, showing the various system components/actors 
that a user's browse might move thru, after they click on a link on a 
campus library's "navigation page" and get redirected thru various 
components, eventually arriving at the resource.....

Is this the sort of diagram that people were expecting?

Thoughts on how to produce a more understandable depiction ?

thanks!

Attachment: simple-flow.jpg
Description: JPEG image