Core Services Goals for 2003-2004

Goals for the current planning year

Goals for previous years

Overview

In this fiscal year, as with the last, we expect activity on the LMS project to have a significant impact on our time. Supporting the transition to the new LMS is our highest priority in the areas where it impacts Core Services. Many goals left unmet last year due to this activity are left as stated, or are only reworded slightly to reflect additional thinking and/or planning that was done.

Nevertheless, certain non-LMS-related objectives that would significantly improve our efficiency and ability to scale our operation have become more critical, and so have been added or spelled out in greater detail for this year. We intend to prioritize as high as possible the transition to network-attached storage and load-balanced web services and the integration of COSIGN authentication.

• Refining and Improving Core Infrastructure
• New storage model. Continue to refine recommendations for network-attached storage (NAS) to increase reliability, ease of management, and scalability.
• Specifics:
• Test the basic NAS model using available equipment.
• Develop a matrix of critical product features by which to compare NAS products.
• Research NAS product features and costs.
• Select a NAS product that offers the best feature/price balance; purchase, install, and test it.
• Manage the transition to NAS.
  
• Redundant web services.
• Specifics:
• For servers in disparate physical environments, do a one-time synchronization of storage, support the use of existing synchronization tools (rdist and loadcd) for continuing synchonization, and enable load-balanced web service.
• For servers in the same physical environment, use the new storage model above to separate web services from storage and enable load-balanced web service. 
• Integration of COSIGN single sign-on web authentication. Integrate COSIGN with the authorization functionality in Library Authentication for all resources currently using Library Authentication using a phased rollout strategy.
• Specifics:
• Develop a plan and impact statement, and receive approval from NISC for a phased rollout.
• Create an inventory of resources currently using Library Authentication and classify them according to transition strategy.
• Develop proof-of-concept functionality by choosing a service that will be easy to transition and changing it to use COSIGN for authentication.
• Transition the remaining services.
  
• Production server replacements/upgrades. Increasingly formalize the server replacement process, and work to equalize its annual cost and improve its efficiency.
• Specifics:
• Complete pending FY2003 server upgrades.
• Complete pending Solaris upgrades (version 2.6 to version 8) for servers which use the CAEN operating system load.
  
• Initiate FY2004 server upgrades.
• Development server replacements/upgrades. Conduct periodic assessments of development servers and identify areas of need. With input from users, consider a) consolidating services, b) repurposing retired production servers (if still viable), and/or c) purchasing new equipment or upgrades as appropriate. Work to achieve a balance between a robust environment and management overhead.
• DHCP/DNS services.
• Specifics:
• Fully migrate DHCP from DSS and consider running DHCP for DLS staff work areas.
• Fully migrate DNS services from the old DNS server.
• Image and OCR processing workflows. Support the design and development of image and OCR processing workflows, using LLMC as a pilot.
• Digital object integrity. Explore Tripwire or a similar tool for automated integrity checking on digital objects.
• Cost model. Continue development of the model for core service costs based on a simple, known variable such as page or image count, to better quantify resources needed in Core Services.
• Documentation. Organize and fill gaps in documentation of the current environment and normal operations.
• Specifics:
• Develop a comprehensive list of items that need documentation, organize this list into a hierarchy, and assign responsibility for sections.
• Devote time each month to writing sections of documentation according to priority.
  
• Security assessment. Conduct an assessment of security practices, document them, and make improvements where necessary.
• Technology trends awareness. Pursue a modest number of options such as trade magazine subscriptions or technology conferences to stay abreast of development in relevant technologies.
• Support and Development for Access Systems
• Library management system implementation. Support the implementation of this system in coordination with the Technology implementation team.
• Specifics:
• Support the design of, and put in place, a high-end server environment.
• Acquire additional Oracle expertise.
• Form support agreements with CAEN, ITCS, and MAIS to extend depth.
• Conduct drills to test redundancy features, including but not limited to
• system board replacement without downtime
• storage device replacement without downtime
• recovery from backup
  
• DLXS. Support and improve infrastructure for DLXS.
• Specifics:
  
• Develop a lightweight authorization solution for DLXS.
• Develop an authentication and authorization management system.
• Develop enhancements to authentication system:
• Test for cookie support and warn the user of detected improper cookie settings.
• Improve performance with path caching.
• Add proper path handling for Java servlets.
• Fix handling of Kerberos passwords containing spaces.
• Research off-the-shelf solutions to replace the existing usage statistics system to facilitate operation by collection management staff and release of the system via DLXS.
• Support the migration from MySQL to Oracle for the production DLXS database.
• Re-sequence MOA journal pages for proper PDF generation.
• Continue to refine the model for hosting the DLXS workshop.
• Set up anonymous CVS to distribute DLXS.
• Persistent URLs. In coordination with DLPS, improve or replace the current stopgap solution for persistent inbound volume-level links.
  
• Institutional repository initiative. Support the exploration of this service, particularly in the area of technological feasibility.
• Collaborating with Other Areas of the Library and the University
• Library/Core Services coordination. Continue to improve the efficiency of services provided to DLS and other library units, including installation and upgrades of servers and software.
• Integration with campus authentication. Continue to pursue options to further integrate campus authentication schemes into the library environment.
• Specific: Collaborate with ITCS on Shibboleth initiatives: contribute knowledge, identify synergies, and ensure the results are consistent with library requirements (e.g. licensing).