University Libraries > Libraries & Departments > Systems > Chinook Corner > ERM Task Force Minutes

ERM Minutes

4/4/2007

Present:  Baia, Callahan, Culshaw, Gobrecht, Graber, Jobe, Kellsey, Moeller, Holladay, Wakimoto,Wicht

Find Articles and More

The committee examined the draft version of the ERM-generated Find Articles and More page http://libraries.colorado.edu:2082/screens/findarticles.html

Baia shared the Cataloger Guidelines for Enhancing Resource Records with the committee members.  Launch of WebPacPro and the ERM-generated version of Find Articles is slated for June 1.  In preparation Serials Cataloging is completing and cleaning up the resource records.

Although the committee has long been aware of problems, the draft pages spurred a lengthy discussion on ERM-generated subject and title pages.  Because ERM records are sorted alphabetically by title, the pull-down subject menus are problematic.  Sorting alpha by title means that the most significant resource may not display first in a list.  Research has shown that students click on the first item in a list in most instances.   The committee discussed various potential solutions to the problem including maintaining the old pages as is until III creates an enhancement allowing for weighted search results, creating an in-house database, and using III modules and enhancements to create a short-term, automated method of weighting the search results more appropriately.  While bibliographers are generally satisfied with the existing pages, the sheer numbers of e-resources have outstripped the Libraries’ abilities to maintain a manual environment.  ERM was chosen because it allows libraries to automate and integrate e-resource activities within the existing environment.   Creating an in-house database was viewed as an unrealistic option.  Even the most sophisticated search engines struggle with relevancy, weighting and ranking.   Culshaw commented that the newly-purchased RSS feed module or featured lists might be used to create a short-term solution until such time as III enhances ERM.  If these cannot be used to generate an automatic page, it might be possible to harvest the search results and create static html pages that are updated on a regular basis.

Wicht observed: 

I was just looking at the Serials Solutions usage stats for the past six months and thought this might be of interest, in regards to our lengthy and interesting discussion of the A-Z and Subject pages. 

The point I made during the meeting is that “Browse by subject” is used quite a bit, certainly more than I would have guessed.  I know that there are many differences between the way e-journals and databases are used, but I still thought this may be somewhat relevant.

Search Types

10/2006 to 03/2007

 

 10/2006

 11/2006

 12/2006

 01/2007

 02/2007

 03/2007

 Total

Title begins with

19,126

17,812

11,484

9,706

12,901

14,069

85,098

Title contains

3,511

3,593

1,988

930

2,283

2,197

14,502

Title equals

840

852

403

269

443

475

3,282

ISSN equals

466

484

268

76

165

173

1,632


Total title searches

23,943

22,741

14,143

10,981

15,792

16,914

104,514


Browse by alphabet

7,621

7,851

4,676

3,656

4,882

5,668

34,354

Browse by subject

3,536

3,483

2,079

953

2,089

2,233

14,373


Total browse searches

11,157

11,334

6,755

4,609

6,971

7,901

48,727


Total browse & title searches

35,100

34,075

20,898

15,590

22,763

24,815

153,241

There was also considerable discussion about how to highlight the availability of custom-crafted Subject Guides.  The current draft has the following text below the search boxes:

Need more guidance? Try using a subject guide.  There may be a way to reposition this to make it more prominent.  There was also discussion of a brief explanatory note about the alphabetic sorting of the titles in the Subject box.  At the time of the meeting, it was thought that only Bowling Green is using ERM to generate A-Z and subject pages.  Deakin University is also using the system.  See http://library.deakin.edu.au/screens/srchhelp_databases.html.   Deakin advises, directly below its subject pull-down, “ Not sure where to start? Check out our Subject Guides”.

Several at the meeting commented that too many titles appear in some of the subject lists.  Moeller volunteered to “clean up” the Religion list.  It might be for a bibliographer to request deletion of a local subject than addition.  This raised the question of an appropriate mechanism for requesting additions or deletions of local subjects, creation of new records, and corrections to existing resource records.  Wicht suggested that this issue should be referred to the Work Flow subgroup.

Jobe raised an issue brought to her attention by Knievel who questioned why there is a separate record for each JSTOR package.  Knievel thinks that patrons may find it confusing.  Since Moeller and Wakimoto confirmed that it unnecessary for soft-linking, the committee was uncertain of what its rationale had been for separate records.  Although they may be needed for management purposes, it might be possible to suppress or consolidate some of the records.  Follow-up?

The WebPacPro implementation team is presenting the draft pages at the April 12 Bibliographers meeting.  Since discussion is likely to be lively, Jobe urged all committee members to attend the meeting if possible. 

Multiple Records for Different Versions of Databases

Working with students and faculty, Graber finds that while faculty tend to use the FirstSearch version of the ERIC database, she trains students to use the CSA version.  There is also a publicly-accessible version mounted at http://www.eric.ed.gov.  After discussion the committee concluded that three separate records are the only solution.  Although you can put multiple URLs into resource records, only one will display to the public.  In an earlier e-mail Helgoth had suggested using an approach similar to uniform titles qualifying by provider:

        1.  ERIC (CSA)
        2.  ERIC (eric.ed.gov)
        3.  ERIC (FirstSearch)

Softlinking E-Book Bib Records To Resource Records

Wakimoto and Moeller raised several display issues related to soft-linked bib records for book titles.  Although ERM can be used for monographic titles, it’s clear that ERM is, at the current time, a very serials driven module.  Moeller and Wakimoto expended a considerable amount of time and energy soft-linking titles in the ACLS Humanities e-book collection.  Because of a recent title change for the collection, Wakimoto hoped to use soft-linking as a substitute for revision of the hundreds of MARC records for titles included in the package.  Furthermore softlinking is crucial for setting e-book packages as “targets” in WebBridge.  That technology relies on linking via ISBN.   Although the original softlinks did not include ISBNs for this package, Moeller is going to repeat his work with the ISBNs included.  He also expressed a willingness to experiment with a small number of records for NetLibrary and other e-book packages. 


The following screenshots illustrate some of the problems:

This screen shot (from the current version of Chinook) shows the empty box where dates of coverage associated with serial titles would normally be placed. 

This screenshot shows the same title in the WebPacPro environment.  Although the empty box for coverage dates is still present, it doesn’t show because the cells in the table are white. 

This screen shot shows the resource record in the WebPacPro environment. Two issues emerge.   “Coverage” is one of the three default elements (Title and Full Text being the others) that appear in the bar above the softlinks. The word is meaningless for monographs.  Callahan thinks it’s probably not possible to remove the word “Coverage” without creating problems for the packages with serials titles attached.  Additionally Wakimoto expressed the concern that the user needs to scroll down the page before seeing the softlinked titles.  Because Database Title, Other Title, Description, Coverage, General Subject are all included in one “token” Callahan cannot cause selected elements  to display at the end of the softlinked titles without moving all of these elements.

Next Meeting

Because the committee was unable to get through its complete agenda during the monthly meeting, the next meeting of the full committee has been scheduled for April 18 at 12:30.  The next meeting will be in the Engineering Conference Room because of a scheduling conflict in N410.