SUHoldings - LUMP CGI XML API to return holdings information from an
    external source (eg Library Management System) for a given SU.

    The SUHoldings CGI script is designed to return holdings information
    from an external source (such as a Library Management System) for a
    given SU.

    *username* - Name of user running this CGI script. Required unless web
    server authentication is in use (when it is, the web server
    authenticated user is used instead).
    *password* - Password for the user. This is only required if the web
    server is not handling the user authentication and if no security hash
    parameter is being given.
    *security_hash* - An opaque value used to authenticate the user without
    requiring the password to be sent. This value is generated by a previous
    execution of a LUMP API script and may well be time limited. It is only
    required if no password or webserver authentication is done.
    *act_as* - Users in the SysAdmins group can elect to act on the behalf
    of other users once they are themselves authenticated. If this parameter
    is present it should contain the username of the user that should be
    switched to if this option is available and the real user has been
    authenticated successfully. Optional.
    *session_id* - An opaque string as far as the server is concerned that
    is intended solely to allow async clients to differentiate different
    results more easily. Optional.

  Specific for this script
    *suid* - The ID of the structural unit in question. This is a required
    parameter for this script.

    The script returns an XML document in the standard LUMP response format
    (as documented in LUMP-XML-Response). The <returns> section's contains
    the XML structure following this DTD fragment:

     <!ELEMENT returns (holdings+)>
     <!ELEMENT holdings (long_loan, week_loan, short_loan, reference)>
     <!ELEMENT long_loan (#PCDATA)>
     <!ELEMENT week_loan (#PCDATA)>
     <!ELEMENT short_loan (#PCDATA)>
     <!ELEMENT reference (#PCDATA)>

    For example:


    The <error> section contains SUCCESS in the <error_code> if the
    operation finishes successfully, or a failure error code if it doesn't.
    The <error_message> element contains a human readable message that can
    be used to inform the user of problems if desired.

    FindSuid GetStructuralUnit ListSUs SUOwner


    Copyright 2010 Loughborough University Library <>.

    Permission is granted to copy, distribute and/or modify this document
    under the terms of the GNU Free Documentation License, Version 1.2 or
    any later version published by the Free Software Foundation; with no
    Invariant Sections, with no Front-Cover Texts, and with no Back-Cover

Go to Top