| | |
| | |
| | h2. Section III: Purpose and Scope of this Document |
| | |
| | The purpose of this document is to define the OCKHAM Reference Model (ORM). The ORM is a framework which can be used as a guideline to develop NSDL Services in a manner that promotes ease of integration and interoperability with other NSDL services, as well as services and systems currently used by traditional libraries. This model is not intended to be a framework which is applicable to any and all services and systems; the domain is clearly within the NSDL, the digital library services which are created and provided by the NSDL program, and the set of currently utilized systems in traditional libraries. |
| | |
| | The ORM uses the term 'interoperable' to infer that the different services in the NSDL need to communicate with other services (both NSDL and otherwise); it does not infer, however, a specific level of communication. It also does not infer that a service must interoperate with all other NSDL services; it is assumed that access to a service will be defined and controlled by that service. |
| | |
| | The services provided and utilized by the NSDL are recognized to be useful to the Traditional Library Community. This community includes, but is not limited to, academic, public, and special libraries. Therefore, a major focus of this reference model is to ensure a low barrier to adoption of NSDL services by the Traditional Library Community. This reference model: |
| | |
| | * provides a set of principles and identifies relevent information for the understanding and increased awareness of interoperability concepts needed for NSDL Services; |
| | * provides the concepts and information needed by the Traditional Library Community to be adopters and users of NSDL Services; |
| | * provides a reference, including terminology and concepts, for describing and comparing current NSDL communication protocols and communication services; |
| | * provides a foundation of principles and best practices that may be extended by other efforts to cover greater-depth interoperability issues of NSDL services; |
| | |
| | The reference model addresses a broad range of interoperability issues. It provides various illustrative examples and some 'best practice' recommendations. It defines a minimal set of criteria that allow an NSDL Service to be labeled "ORM Compliant". |
| | |
| | This reference model *does not*: |
| | |
| | * specify which technical standards must be used in an implementation (though suggestions may be made based on current knowledge); |
| | * provide a basis for compatibility of OCKHAM instances; |
| | |
| | In other words, "ORM-Compliant" does not equal "Compatible". Multiple groups may produce OCKHAM system instances in different ways with no coordination, and the end result may be two systems that cannot talk to each other (or services that can only reside on one or the other system). This might be exactly what is desired, however, and we do not wish to rule it out. |
| | |
| | Put another way, the OCKHAM reference model is distinct from OCKHAM systems. There is only one reference model, but there may be multiple, mutually-exclusive OCKHAM systems based on it. However, due to being derived from the same reference model, all ORM-Compliant systems should be comprehensible to anyone who understands at least one of them. |
| | | |
| | ----- |
| | |
| | |
| | Here are two stories illustrating the benefitst of usign this particular reference model. The first story is from the prespective of a librarian. and the second is from the perspective of a patron. |
| | |
| | The services a library wants to provide are very similar to the services other libraries want to provide against their collections. Examples of such service could include: |
| | |
| | * whats new |
| | * random quote of the day |
| | * list of items held in the collection |
| | * search cabability |
| | * preserve their materials |
| | * provide access to their materials. |
| | |
| | The sense of sharing the work is common in the library community. Why duplicate the work? Why reinvent the wheel all the time.. This document describes/outlines many best practices for implementing commonly used digital library services. It is intended a guide book so librarians do not necessarily have to reinvent the wheel all the time. |
| | |
| | This model intends to foster innovating in library serivces by describing those library services. It can be used to pique a librarians interest and suggest ways digital library collections be implemented in new and different ways. The registry is a way of discovering these new sercvies. it is a way of ocomputers to discover theser serivces and save the time of the librarian. For example we wanted to havest the Dublin Core data from NSDL libraries, but there was no way to discover whether or not if the various NSDL collections were available via OAI-PMH. |
| | |
| | [INSERT HERE SCENERIO OF DOING PROVIDING A SET OF DIGIATAL LIBRARY SERVICES AGASINST A DIGITAL COLLECTION.] |
| | |
| | In the broadest sense, there are two types of library patrons: the student and the scholar. Again, in the the most general sense, the students is spending time trying to aquire knowledge. They are trying to learn. On the other hand, the scholar, in general, is try to create new knowledge. They are trying to increase the sphere of knowlege. Because of these two distinct purposes, the problems of students and scholars are different. |
| | |
| | Both students and scholars need to be able acquire the proper materials for their particular needs in a timely fashion. And they need those materials to be the materials that will satisfy their particular needs. A person does not need to know the birthdate of Ben Franklin many times over very quickly, they need the appropriate information at the approprate time. |
| | |
| | Ranganathan |
| | |
| | * Books are for use. |
| | * Every reader his or her book. |
| | * Every book its reader. |
| | * Save the time of the reader. |
| | * A Library is a growing organism. |
| | |
| | |
