New Task Group on Journals in Aggregator Databases

In 1999, the Standing Committee on Automation Task Group on Journals in Aggregator Databases developed specifications for the content of aggregator analytic records, completed a demonstration project with EBSCO, met with representatives from aggregator database vendors, recommended maintenance specifications for vendor record sets, and communicated widely about their work. The first task group's final report is available on the SCA home page.

At its November 1999 meeting, the PCC Policy Committee recommended that the task group be reconstituted for two more years with a new charge, as follows:

1. Record sets. Continue to pursue creation of sets of records for major aggregations like ProQuest and Lexis-Nexis Academic Universe.
2. WorldCat Collections Sets. Make a list of desirable sets of human-created analytics and recruit WorldCat Collections Sets contributors from among the OCLC membership.
3. Maintenance. Test the feasibility of loading and maintenance arrangements for one or two sets of records.
   • To begin, conduct a survey of the libraries that have requested the EBSCO set, to get their views on loading and maintenance needs.
   • Include questions about loading and maintenance using both the single and separate record approaches.
4. E-books. Determine if the same specifications for serials are suitable for full-text monographs in aggregator databases, e.g. netLibrary.
5. Other solutions. Ascertain more systematically what others are doing to provide access to the contents of aggregators. Continue to monitor related developments pertaining to access to journals in aggregator databases.
6. PCC Tactical Plan. Mainstream bibliographic control measures for aggregators into the PCC tactical plan.
7. Communications. Continue raising awareness in the library community of issues pertaining to journals in aggregator databases.

An interim report is due at the November 2000 PCC Policy Committee meeting. The report should contain a description of progress on the charge and preliminary recommendations as appropriate.

A final report and recommendations are due in November 2001. The final report should identify implementation issues, formulate plans to be presented to vendors, and describe the support required from other appropriate organizations.