![]() |
Service driven: The architecture for the DLs must be driven by the services it provides and tools required for |
| delivering the service. | |
![]() |
Open architecture: The architecture must be open, extensible and support interoperability among heterogeneous, |
| distributed systems. | |
![]() |
Scalability: The architecture must be robust, scalable and reliable in a high transaction rate production setting |
| thousands of patrons with a wide variety of backgrounds and information needs. | |
![]() |
Preservation: The architecture must ensure persistent access to collection of the DL, addressing such issues as |
| naming, digital archiving and digital preservation. | |
![]() |
Privacy: The architecture must be sensitive to privacy issues and support both anonymous and customized |
| access to resources. | |
![]() |
Practicality: The architecture should represent a flexible and practical approach to standards, recognizing the |
| need to balance the level of information collection with economic constraints. | |
![]() |
Modularity: The architecture should represent a mix of new technology and legacy pieces, all of which must inter |
| operate while involving at different rates. |
![]() |
Time frame: The time frame required to plan for system migrations in the next year as well as planning for a |
| technology generation framework should be approximately 3 to 5 years. |