1 / 37

Orbis/PORTALS E-journal Workshop May 9, 2002

Orbis/PORTALS E-journal Workshop May 9, 2002. E-journal Issues. Bonnie Parks - Oregon State University. Aggregations and Packages. What kinds of e-serial aggregations and packages are available? How can libraries provide access to titles and content in these packages?.

Télécharger la présentation

Orbis/PORTALS E-journal Workshop May 9, 2002

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Orbis/PORTALS E-journal WorkshopMay 9, 2002 E-journal Issues Bonnie Parks - Oregon State University

  2. Aggregations and Packages • What kinds of e-serial aggregations and packages are available? • How can libraries provide access to titles and content in these packages?

  3. What are Aggregations?(aka Aggravations) • A collection of publications in electronic form, commonly full-text versions of print journals. • Some aggregations are stable and well maintained (e.g. Project Muse, JSTOR) • Some are of the “31 Flavors” variety (e.g. Lexis/Nexis, Bell + Howell (Proquest))

  4. Stable Aggregations • Have a common element (usually publisher or subject) • Have complete full text (or, if not complete, differences are made clear) • Articles are accessible by journal title and issue • Stable title list (often aggregator notifies subscriber of changes or additions to collection) • Close correspondence between print and online (makes cataloging relatively easy)

  5. Stable Aggregation : JSTOR

  6. “31 Flavors” • Large, amorphous collections • Titles come and go (what’s available today might not be available next month) • Users frequently cannot designate specific journal title and issue • Often lack full text of a journal or some issues of a particular journal

  7. 31 Flavors example : LexisNexis

  8. How Do You Provide Accessto the various Electronic Journal Packages in Your Library? • Catalog them and make available in OPAC? • A-Z list of journal titles? • Separate database? • Other means?

  9. Sample E-journal Catalog Record

  10. Sample A-Z E-journal List

  11. Aggregators and the OPAC • The library catalog should provide users with a record of all selected and available material regardless of format • Users tend to expect aggregator database titles to appear in the OPAC • Conventional cataloging could solve problems of aggregations, but most cataloging departments do not have the resources to provide this access)

  12. Aggregator Access • In addition to access via the OPAC, consider alternative means • Through web lists, databases and gateways • Through online indexes and databases

  13. Access : Traditional Cataloging • Titles individually cataloged following the same procedures as for other serials • Advantages • Benefits of complete MARC records (authorized subject headings, names, classification) • Consistency within the catalog • Cataloging copy often available for larger packages

  14. Access : Traditional Cataloging • Disadvantages • Cataloging e-serials can be more time-consuming than cataloging print • Since e-resources are prone to change, more record maintenance is needed than with print (and you thought maintaining print serials was a lot of work!)

  15. Access : Single-Record Approach • The single-record approach notes the existence of an online version on the record for the print serial • Advantages • Complete print serial records (authorized subject headings, names, classification) • Doesn’t require a lot of cataloging expertise to add access points for online version • Large packages can be processed with less work on each title.

  16. Example of Single-Record Approach

  17. Access : Single-Record Approach • Disadvantages • Cataloging is still required for titles not held in print collection • Loss of access points unique to electronic version • have the option of adding it locally, but that, too, requires maintenance (e.g. Adding 710 JSTOR (Organization) to all your JSTOR titles) • Still difficult to keep up with maintenance in dynamic aggregators like Bell + Howell, Ebsco, etc.

  18. Access : Aggregator Record Sets • MARC record sets are available from several sources, e.g. OCLC (Worldcat), Bell + Howell (Proquest), Ebsco • Commercial services are developing customized MARC record sets for a variety of packages

  19. Considerations when looking into record sets • Record completeness • Maintenance and updates • Cost • Relation to records already in your catalog • Ease of removing records from your local system If your library’s subscription to 3,000 EBSCO titles is cancelled today, how will get those records and links out of your catalog tomorrow?

  20. Some Questions to Ask • How complete and authoritative are the records? • E.g. Ebsco derives records from CONSER records, so generally, the records are complete and authoritative • Gale generates their records from their own data, which doesn’t include authorized headings or complete description. • Are record updates distributed? How frequently? Is there an added cost? Per record? Per set? Per load? • Is the entire record set redistributed or only records to be deleted, added or changed? Maintenance and cost issues here!

  21. Access : Journal Title Lists • “In the beginning ...” users accessed e-journals through alphabetic lists on web pages • These lists still are popular, though now there are more and more titles to maintain! • Some libraries are unable to provide online access through the catalog, so A-Z lists continue to be be an option

  22. Example of E-journal Database that Generates Web Pages(Scripps Research Institute)

  23. Access : Separate Database Some libraries have created a separate database of their aggregator e-journal coverage • Advantage • Requires no cataloging resources • Disadvantages • Users must consult two sources to determine journal holdings • Still subject to maintenance • Individual libraries must do the work themselves • Potentially no subject or corporate body access

  24. Example of Comprehensive Database JAKE is probably one of the more well-known early databases.

  25. Access : Local Scripting What is it? Minimal records are created by the library from vendor-supplied title/ISSN listing • Advantage • Provides online access to large packages for which no record set is available • Disadvantages • Libraries must do the work themselves • Vendor-supplied lists usually don’t include OPAC access points (subject, corporate body) or title history • If ISSN isn’t available, it’s tough to match records

  26. Local Scripting and OSU : the Ebsco Records Wizard • What is it? • GUI-based collection of vbscripts created by Terry Reese • What does it do? • Provides access to individual Ebsco titles • De-dups the Ebsco Records sets on OCLC number and ISBN • Generates a new overlay point • Provides a method to globally add/delete fields.

  27. Ebsco Records Wizard:Getting Help • The Ebsco Records Wizard uses a web-based help system. • System facilitates local use and remote use. • Help system and the program can be downloaded from: http://ucs.orst.edu/~reeset/ebsco/html/

  28. Service Benefits : a comparison • April 2001 and April 2002 were used as a test month for comparison. • Based on usage stats from these two months, Ebsco usage increased by approximately 70%.

  29. Service Benefits: a comparison • Moreover, including titles in the OPAC decreased the amount of patron time needed to spend searching for a resource. Again, using the same two test months, one can see that they amount of searches performed on the database actually went down 25%. This is due largely to the fact that users are being taken directly to their desired journal, rather then having to search each individual subscription database for the Journal title.

  30. Service Benefits: a comparison cont. • In addition to decreased searching on EBSCO, we can see that many of the new users coming to EBSCO are coming through Oasis. Again, using out two test months, we can see that once the EBSCO records were provided in the OPAC, they were immediately utilized.

  31. Accessing Ebsco Records • Ebsco Titles are now accessible directly through the library’s OPAC! • On the right: an author search in the OPAC. Using this search, a patron can locate all the Ebsco titles currently in the local catalog.

  32. Accessing Ebsco Records cont. • All Ebsco records are • Searchable within an electronic resources scope • Are noted with [electronic resource] in the GMD for easy identification

  33. Accessing Ebsco Records cont. • Accessing titles via the catalog:

  34. Other Means of Access : Vendor Solutions • Printed lists • Title and holdings data • Record sets • Searchable tables of contents • Management information Vendor solutions cover a wide range of possibilities including:

  35. Aggregations : Summary • There are many ways to provide access to serials in packages and aggregations • Depending on the packages your library uses, there might be one solution or several solutions • Libraries should include catalog access but also should think beyond the catalog • It’s all about ACCESS!

  36. Suggested Reading Li, Yiu-On and Shirley W. Leung. Computer Cataloging of Electronic Journals in Unstabe Aggregator Databases: The Hong Kong Baptist University Library Experience. Library Resources and Technical Services 45, no. 4 (Oct. 2001): 198-211. PCC Standing Committee on Automation, 2nd Task Group on Journals in Aggregator Databases. Final Report. http://lcweb.loc.gov/catdir/pcc/aggtg2final.html Schultz, Nathalie. E-Journal Database: A Long-Term Solution? Library Collections, Acquisitions, & Technical Services 25, (2001): 449-459.

More Related