Other Uses of IESR
Other uses of IESR have been suggested, but have not been developed into detailed Use Cases.
Discovery of Service APIs for Web 2.0 Application Developers
Web 2.0 application developers could use IESR to find suitable services to embed into their applications and details of their APIs. For example, people building applications using Yahoo pipes could discover services such as RSS feeds in IESR.
Services using IESR Records
- Recommendation Service that passes log data. This could be a middleware service built on top of IESR.
- An application that uses IESR information, such as IP ranges and agent postcodes to find all resources in a region. For example this could be an NHS application.
Copac Planned Use of IESR
Copac would like IESR to contain details of library OPACS, including the IP ranges they are applicable to (IESR metadata already supports this). If a user is looking for a book but is not from one of the CURL library institutions, Copac could provide to them a search over their home University library's OPAC. [This is Use Case 2.7.]
Copac plan to provide electronic ILL. They would give the user a form to fill in and then send it electronically to their home institution library. They need to know where the user is [Note that there is a missing Shared Service in the JISC IE - an IP Range service]. The information they need to capture is similar to what Zetoc holds in a library profile to implement its simpler ILL support. Suggestions for implementation via IESR:
- ILL is a Service (ie service access method: ill), but not necessarily m2m. The information of what sort of ILL support a library agrees to could be captured in a Service record, with some information in the associated administrator's record.
- Expect the library to have the OPAC registered in IESR. This will have the library as agent. So maybe more details could be added to the Agent record to capture ILL preferences.
Central Resource Catalogue
- If IESR is regarded as the main record of a resource, details can be included, and thus documented, so that everyone can discover the information. In particular, technical service details can be recorded. Currrently this information is hard to find - possibly only one person in a company knows.
- A record of resources that a particular funding body provides, and details of the service access points. This enables the funding body, and its developers, to know what they've got and keep on top of what they are doing.
- Provide a search for discovery of resources provided by a particular funding body. Possibly this could interact with HILT to provide subject-based searching.
Contribution of Resources
- Local librarians could enter details of resources in IESR. Then other users, eg in the NHS, could make use of it.
27 October 2008