1. "Smart" OpenURL Resolver: Professor Smith is a visiting faculty member at Foo University. Dr. Smith is looking for an article on dogmatic practices in software design, one that she knows has been published recently. She uses Foo University Library's metasearch service and finds a citation to the article. A "Get this item" button is located next to the citation, so Dr. Smith uses that button to retrieve the full-text article (via the library's OpenURL resolver). Unfortunately, she finds that the Foo University Library does not have a full-text subscription to the database which provides the article. She does remember that her home institution (Bar University) has a subscription. Luckily, one of the options she is given is to identify a secondary institution to use for resource resolution. She selects 'Bar University' from a drop-down list (a list that has been dynamically created via a query to a digital library service registry), and she is then presented with additional resource resolution options (via the 2nd resolver), one of which is to the online full text of the article she seeks. Dr. Smith chooses this option, authenitcates herself as she normally would when accessing Bar University Library's services from off-campus, and retrieves her article
2. Service Discovery and configuration: Jerry the systems librarian has been asked to add the database 'foo' to the general search profile of his library's metasearch application. The metasearch application can only include collections / databases which are available via Z39.50. Jerry searches the digital library service registry via the database name, and discovers that the database provides search access to their database. Jerry then looks to see what protocols for search are supported, and finds that the 'foo' database is searchable via Opensearch, SRU/W, and Z39.50. Discovering that Z39.50 access is indeed available to this particular database, Jerry then retrieves from the registry the necessary client configuration information for the metasearch application, and adds 'foo' to the general search profile for his library's metasearch.
3. Service Resolution and configuration: A library's metasearch application has not been able to connect to a particular database's Z39.50 server for the past 24 hours. The application automatically looks to verify the URL for the database's Z39.50 server through the digital library service registry. The application discovers the port number is now different from what it has configured for the database, and automatically updates its configuration with the new port number.
4. Personalized metasearching: Bernie the researcher is exploring the history science for a book he is working on. He uses his library's metasearch tool to search through history-related databases and collections. He also searches the web for collections and resources that do not reside within the context of his library's collections and services. During his web searching, he discovers the Linus Pauling papers at Oregon State University. Bernie would like to add the Linus Pauling collection to his default metasearch, so he goes into the metasearch tool, clicks the 'customize this search' button, and then searches for the Linus Pauling collection to see if he might be able to add it. The metasearch application searches the digital library service registry for the linus pauling collection, and shows Bernie that there are actually five collections which match his search. Bernie is delighted to find four more collections, and checks all of them to be added. The metasearch application then discovers that these collections are not immediately searchable via any standard protocol, but they are harvestable via the OAI-PMH protocol. The metasearch tool is intelligent enough to be able to automatically start harvesting the metadata from these collections into a local index, and then include them as part of Bernie's default search.
5. Resource Validation: Archie Vist is a cataloger. He oversees quality control on submissions to his university's institutional repository. In reviewing a particular submission, Archie attempts to view the submitted resource, which appears to be a PDF document. However, his PDF viewer cannot open the requested file. Archie clicks a 'validate format' button on the metadata edit screen. The repository software queries the service registry for a format validation service, and finds one at Harvard (attached to Harvard's Global Digital Format Registry). The resource in question is automatically passed to the validation service, which replies back that the object cannot be validated as a PDF, but did validate as a Microsoft Word document. The repository software corrects the file's extension, and Archie is able to finish his work on approving the submission.
6. Preservation: Lucy, the librarian in charge of a large image collection, is concerned about recent updates to a number of image format standards. To ensure the longevity of the collection, she would like to migrate images to updated formats. She is aware that a number of libraries provide migration services for a variety of digital document formats. Using the service registry, she locates these services, retrieving metadata about formats accepted, costs, and ability to handle large numbers of images. She sends the results of the search to the AUL in charge of preservation, and a proposal to develop a system that automates this process on a regular basis
7. Name Authority: Jim is in charge of setting up an OAI-PMH aggregator that will gather distributed metadata records and then reuse them in a science digital library. He is concerned about the quality of the collected records and would like to apply some normalization and cleanup to them. One particular area of concern is the uncontrolled use of personal and corporate names in the records. He uses the service registry to locate existing name authority services offered by various organizations, and plans an aggregation strategy that uses these services for metadata cleanup.