Use cases:

• Putting loan/due date reminders in a portal
• RSS feed of loans, fines, etc.
• Asking for status of books I have or want (includes holds)
• Access borrower record information (name, address, blocks, messaging, etc)
• Find out if someone can access or can place or can cancel a request on a resource

Security issues involved: You don't want to give out patron info to unauthorized persons. (Or you may need to blur info: "book is checked out" but you don't say by whom) Either the client is trusted or we need authentication/authorization.

Functions:

GetPatronRequests (take a patron identifier of some sort)
GetPatronFines
GetPatronMessages
GetPatronInfo - name, address, email, etc.

GetPatronStatus
(as a cheap working proxy for a more sophisticated "can I do this?" function)

Bindings:

Object library (in some language, e.g. a Perl script doing SQL queries)
NCIP?
XServer?
(check penn portal binding)

Who will work on this further: Same folks as delivery; and John will ask Mike about what structures we're passing back in our portal

To move to real-time search:

GetCourseReserves (belongs in other section, but we thought of it here; takes course arguments - this might be an important real-time search, appropriate when material is only made available for purpose of specific course) - takes course if argument