The Library of Congress intends to negotiate on a sole-source basis with Mark Logic Corporation for the following services: XML DATABASE IMPLEMENTATION AT THE LIBRARY OF CONGRESS A.1 Solicitation A.1.1 The Library Services Technology Policy Directorate (LS/TECH) at the Library of Congress desires to implement an XML database to encompass their current collections. The XML database will aggregate all of the metadata from their current collections as well as be the data store for all XML data. This database will provide a single access point for the various collections and must be kept synchronized with the other databases. B.1 Background B1.1 The Library of Congress has millions of items in various types of media stored across the globe in many collections. Library Services creates and manages the databases for each collection. Access to a collection is provided by a user interface specific to that collection which has Library Services creating and maintaining multiple access interfaces. By consolidating all of the databases and content into an XML database, Library Services will be able to provide a single access interface to all of the collections. C.1 Scope C.1.1 In order to provide consistent access to the databases, they will be aggregated into a centralized XML database and the Library will develop a unified access portal. The XML database vendor must supply the XML database that meets the Library’s technical, performance, documentation, training, and support requirements. C.2 XML Database Technical Requirements In general, the XML database should be compliant with the XQUERY 1.0 standard, be scalable to a large number of objects and provide high indexing and loading performance. The vendor needs to have applicable experience, be committed to complying with the standards, and be financially stable. C.2.1 The following requirements are the highest priority and considered critical. • Native XML o Not mapping on top of a relational model. Creation, update, and deletion of data in the database are based on XQuery and/or use of network protocols such as XML-RPC, REST or WebDAV. No use of SQL or creation of common RDBMS constructs such as tables and columns shall ever be necessary at any point in database administration. o Default support for UTF-8 character set. • Scalable o Must handle at least 100 million objects o Must handle large individual XML files (up to 1GB) o Must be able to completely index (every node) text objects o Must support over 1,000 simultaneous users without degradation o Must provide load balancing • Full text indexing o Must provide incremental indexing on documents being added, updated, or deleted without requiring system shutdown or unavailability of querying. o Must be able to find and return an XPATH element or hierarchy o Ability to do full text search of mixed content across tags • Geospatial support o Indexing o Searching • XQUERY support o Must be fully 1.0 compliant o Must support modularization o Extensibility to support modules written using other programming languages like Java or .NET languages, or support for direct Java-XQuery binding. • ACID compliant • SOA-based • XLink / XInclude / Xpointer support • Alerts o Must provide persistent queries  Automatically query new content and provide notifications • Faceting • Turnkey web development environment o Integration with J2EE o Integration with .NET • Configurable via web, XQUERY, and shell • SQL connector to relational databases C.2.2 The following requirements are considered highly desirable but not critical. • Ability to rewrite URLs similar to Apache’s mod_rewrite upon serialization to aid REST web service application development. • Built in native support for XSLT 2.0 transformations as a XQuery function without requiring additional web service applications. • Built in XQuery module supporting HTTP calls (GET, POST, DELETE, PUT, HEAD) to remote resources. • Built in query syntax parsing • XQuery Full Text 1.0 standard support strongly preferred over proprietary search functions. • Language support o Stemming / tokenizing o Sorting of data based on collations, supporting internationalized languages and locales. • ATOM publishing protocol support C.3 XML Database IT Requirements The database must run on at least one of the following configurations: Hardware Platforms • Sun • IBM • Hewlett Packard (Windows) Operating System Options • Solaris • AIX • Linux • Windows C.4 XML Database Vendor Requirements The vendor must meet the following requirements • Financial Stability o 2 References o At least 3Years of Operation • Commercial Support o IT Consulting  Installation  Configuration  Deployment o On-site Training o Development Consulting o Provide multiple environments  Production  Development o Maintenance Agreement D.1 Deliverables D.1.1 An XML Database product that meets the technical and IT requirements See F.1 D.1.2 Financial stability references and required information See G.1 D.1.3 IT Installation; Training; and Development Consulting The vendor will provide on-site training for developers for XQuery programming and application-specific functionality. The vendor will provide remote and after-hours support for development issues. • One week administration class for up to 10 • 40 days of consulting with a senior developer: o Up to 15 days for installation and configuration o The remaining time for development support D.1.4 Communications Plan The vendor will provide a detailed plan for communicating with the various Library of Congress contacts with roles, responsibilities, and availabilities for each contact. D.1.5 License Delivery Schedule The vendor shall deliver and install licenses for immediate use by the Library of Congress. • 1 development license • 1 production license D.1.6 Deployment Plans The vendor shall provide a detailed project plan for deployment including IT and developer training. D.1.7 Reports The vendor shall provide weekly progress reports on the status of the deployment plan. D.1.8 Remote Technical Support The vendor shall provide technical support: • Unlimited support requests via e-mail, chat or telephone: o 6:00 AM - 6:00 PM eastern standard time Monday - Friday except for holidays o For Critical issues, a one-hour response time is required  The system or major application is down or seriously impaired; data is lost or destroyed; and there is no reasonable workaround. o High priority issues require at 4-hour response time  The system is moderately impacted and there is no reasonable workaround. o Medium priority issues require a 24-hour response time  The system has not failed and no data is lost or at risk. A workaround may temporarily resolve the issue. o Low priority issues require a 4-day response time  Any non-critical issues; enhancement requests; or general questions. D.1.9 On-site Technical Support The vendor shall provide on-site technical support: • Within 48 hours of a request o E.1 Period of Performance E.1.1 The period of performance for this contract shall be in two parts: • Phase 1 - the purchase and installation of the Development software – approximately July 1, 2009. • An option for Phase 2 - the purchase and installation of the Production Software – the goal of which is to purchase in FY2010. E.1.2 Final payment will be made upon satisfactory completion of the acceptance criteria. G.1 Instructions, Conditions, and Notices to Offerors or Quoters G.1.1 Offerors will provide two references as examples of similar work done. G.1.2 Offerors will stipulate a continuity of staff for the duration of the project. G.1.3 IP and data rights AI: Contracts F.1 Acceptance Criteria The following use cases must be passed and accepted by the Library of Congress. The detailed use cases are provided as a separate attachment. F.1.1 Administration User Interface: Users and Permissions Allow administrators to create users, groups and access control lists and specific permission. F.1.2 Authentication Allow the Library of Congress to utilize its own authentication application or be compliant with applicable C&A requirements. F.1.3 Format Conversion on Ingest Accept documents in native formats (e.g. Word and PDF) and automatically convert to XML and index. F.1.4 Interfaces: File System Demonstrate the ability to access available file systems (Windows, Unix, Linux) and perform permissible file operations (create, read, update, delete). F.1.5 Interfaces: Relational Databases Demonstrate the ability to access relational databases via SQL statements in XQuery programs. F.1.6 Performance: Loading Meet the benchmark for record loading. F.1.7 Performance: Indexing Meet the benchmark for record indexing. F.1.8 Programming Language Support Demonstrate compatibility with the desired programming languages. F.1.9 Toolset Demonstrate that programmers can execute queries without requiring and external integrated development environment. F.1.10 URL Rewriting Demonstrate acceptable URL rewriting support. F.1.11 WebDAV Support Demonstrate support for the WebDAV protocol. F.1.12 XQuery Language Support: Compliance Demonstrate full compliance to the 1.0 XQuery specification. F.1.13 XQuery Language Support: XInclude / XPointer Demonstrate support for XInclude and XPointer. F.1.14 XQuery Language Specific Queries: Control Field Empty String Demonstrate that specific queries for identifying records which have a controlfield tag attribute value that is an empty string work as expected. F.1.15 XQuery Language Specific Queries: Control Field not a 3-digit Number Demonstrate that specific queries for identifying records which have a controlfield tag attribute value that is not a three-digit value and is not an empty string work as expected. F.1.16 XQuery Language Specific Queries: Data Field Asterisk Demonstrate that specific queries for identifying records containing an asterisk character in the LCCN value work as expected. F.1.17 XQuery Language Specific Queries: Data Field Empty String Demonstrate that specific queries for identifying records with a datafield code attribute value that is an empty string work as expected. F.1.18 XQuery Language Specific Queries: Data Field Multiple Tags Demonstrate that specific queries for identifying records with a datafield code attribute value containing more than one LCCN tag work as expected. F.1.19 XSLT and XLSFO Support Execute an XSL Transformation inside a XQuery given a large XML file as the source data. F.2.1 Backup and Restore The system and the database must be successfully backed up and recovered using existing ITS infrastructure and backup & recovery strategies.

Bid Protests Not Available