• Describe general architecture and design
• Identify platform issues and options
• Address scalability potential and performance
• Is there an API to access your content? Are they available for evaluation?
• Describe how institutions can interface with hosted, indexed data, including native interfaces, customization of those interfaces and APIs
• Please provide any examples of institutions that are employing APIs or other means of customizing your interface for local implementations.
• Do customers have ability to modify indexing parameters, algorithms or facets?
• Can our data (local collections, etc.) be merged into your content? Briefly explain the process including any pre-processing requirements, etc
• Language/character set support?
• What kinds of content are you indexing? (Bib data, article metadata, full text, digital collections)
• What data formats and schemas can you index? (MARC, EAD, MODS, METS, TEI, Dublin Core, others?)
• Provide examples of your support of various data formats
• How often is content updated?
• Does your product support harvesting of local UW digital collections? If so, how does the process work and when are items then available in your index?
• Does your system run on hosted hardware or does the customer host?

Technical overview The University of Wisconsin System "one system, one library" philosophy promotes an integration of services across all System libraries. The technical environment seeks to support this goal by fostering integrated discovery and delivery across all collections of the consortium. Underlying much of the UW Libraries' technical infrastructure is the ExLibris Voyager ILS. Characterized by 14 separate instances of the Voyager ILS and OPAC, the primary means of resource sharing and delivery is through the Voyager Universal Borrowing module. SFX and MetaLib are used by most schools for Open URL linking and the management/delivery of database content. Many of the UW-System schools share a single Sun server for the hosting of their individual Voyager instances along with a separate shared server for SFX/Metalib hosting.
Patron authentication is managed by each institution using a variety of methods. However, the UW-System has a central authentication hub and Shibboleth architecture to support greater integration of authentication and authorization services.