An institution’s Library and Information Services (LIS) should be able to offer its students, faculty and staff access to a number of web applications for teaching, learning and research as services.  Users should be able to easily find a list of available web applications and then chose to create content/resources/assets in any one of these applications using their institution user accounts. 

There should be one web application that is the system of reference.  This application should interface with administrative systems and be able to access information about academic roles, course enrollment and administrative groups as well as create custom groups.  This system of reference should be able to use this group and role information to define access control within it as well as pass this authorization information to other supported web applications.  As well, this system of reference should contain a record of authentication, authorization and node connections to all supported web applications that a given user has added, edited or deleted.

From within any supported web application, users should be able to create connections to other supported web applications and pass role and group information from one system to another.  Additionally, users should be able to connect content/assets/modules in one system to content/assets/modules in another system or include content/assets/modules in one system that were created in another system as copies and/or references and apply access control to these.

Each supported web application should include a persistent and consistent display (as a discrete page header) of the user’s status in that system that includes their name (and optionally their role), a link back to the system of reference and/or links to other supported web applications.  For at least a subset of supported systems, users should be able to layout and theme content/assets/modules consistently across these systems.