eResources Version 2 Outline
VERSION 2.0 OUTLINE [for September 2003 release]
Content & Intellectual Structure
1. Implement a feature to rank resources
Search
2. Make searches retrieve contents of a subject folder when appropriate
3. Include the basic search box on all screens in eResources, including within subject folders.
4. Revise eResources Help page
Browse
5. Display subject guides in subfolder index pages making the guides more visible at the second level of the folder structure
6. Create an eResources subject folder site map to display the entire hierarchy of subject folders.
7. Display the liaison field in the public interface.
8. Migrate to the use of 655 fields to identify format type.
9. Modify the system to accommodate multiple urls in records.
DEFINITIONS & EXAMPLES
Content & Intellectual Structure
1. Implement a feature to rank resources
The high number of resources in the eResources database makes it necessary to provide some guidance for users as to which are the most important resources in a subject folder. The eResources group has presented a proposal to the Digital Library Management group on the development of this feature (see attached).
Search
2. Make searches retrieve contents of a subject folder when appropriate.
This feature will ensure that a user searching for resources using a keyword, description, or subject search will retrieve the appropriate subject folder(s) in their search results, as well as individual resources. As the system is now, a keyword search on "nursing" retrieves many valuable resources but it might exclude important resources that are not primarily about "nursing" but are included in the nursing folder.
3. Include the basic search box on all screens in eResources, including within subject folders.
Many users would find it useful to be able to move easily from browsing to a quick search for a particular item. Making the basic search box available on all pages will enable users to browse, then search, without having to navigate back up two levels to the main Search/Browse page.
4. Revise eResources help page
The help screen provides an opportunity to define the scope of eResources. In addition to offering search tips it should also include the link to the "Browse eResources" video tour.
Browse
5. Display subject guides in subfolder index pages making the guides more visible at the second level of the folder structure
Currently, selecting a top-level folder (e.g. Chemistry) accesses a page listing subfolders in this category (subfolders exist for approximately 2/3 of the top-level folders). If, in addition to the subfolders, the user could see the subject guides associated with the folder, it would help provide a starting point for users and promote the subject guides that might otherwise be overlooked. This feature would only affect folders with more than one level.
6. Create an eResources subject folder site map to display the entire hierarchy of subject folders.
This would be a link from the main Search /Browse page, allowing all of the 229 folders in the eResouces hierarchy to be viewed at once.
Display
7. Display the subject folder liaison field in the public interface.
At present, users have no easy way to know whom to contact with questions about resources or for assistance with their research. Subject folders now require liaison and editor (bibliographer) entries. It will be possible to enter a "generic" contact such as Baker-Berry Reference or Kresge Reference.
Infrastructure
8. Migrate to the use of 655 fields to identify format type.
In order to simplify the data structure from which the "Type of Resource" folders are built, we propose using the MARC 655 field to provide data on all the formats in the eResources database. The 655 field is a heading indicating the form, genre and/or physical characteristics of the materials being described. It can accommodate locally created vocabularies.
9. Modify the system to accommodate multiple URLs in records.
Over the next year we anticipate changes to the way our electronic journals will be represented in the catalog and subsequently in eResources. Many of our records will include multiple 856 fields. eResources will have to accommodate multiple links from a single ejournal record.