Highlights of the History E-Book Library License Broad definition of "authorized users." Includes not only students, faculty and staff, but also anyone present in the library. Site license: access is not limited to the library building. Links into History E-Book Project staff who will work with libraries to achieve stability and standardization by e-mail, phone or fax from 9 am to 5 pm EST, Monday through Friday, for feedback, problem-solving, or general questions. Help files and user documentation will also be available online. Hardware and software requirements: Macintosh, PC or UNIX workstations with Internet connectivity and TCP/IP installed. A monitor with resolution of at least 800x600 is recommended for optimal performance. Netscape Communicator 6.0 and above, or Microsoft Explorer 5.5 and above, minimum standard. Internet connectivity of at least 1.5 mbits/sec data transfer capacity is helpful for fastest access. Initial term of three years, with automatic one-year renewal terms. Monitoring Access The HistoryEbook Library will employ an authentication approach that allows access to all users on the campus or off-campus. Without authentication, even the most straightforward access schemes exclude legitimate members of the campus community and run the risk of jeopardizing the site license for both libraries and publishers, as well as participation in intercampus agreements that may offer significant financial benefits. While electronic libraries use a variety of mechanical proxies, application proxies, and credential-based approaches, the HistoryEbook Library will employ an approach similar to that already used successfully by the JSTOR, OCLC, and other services and one that is also fully within the technical capabilities of DLPS: currently proxy/credential hybrid access. While approaches to authentication will vary and evolve, use of such hybrids will allow campuses to avoid the cost of managing certificates. In addition, apart from having to enter a user name and password, the access schemes adopted will be invisible to the end user and have low overhead. Resource requirements will be more modest, and there will be less degradation of performance.