1. Putting Tables of Contents into Library Catalogues Paul Evans (Emerald) TOCRoSS Partners University of Derby Talis Information Limited Emerald Group Publishing Limited

2. Why TOCRoSS? Libraries invest a lot of money in journal subscriptions. They need to market these resources to their users. Currently only journals may be recorded in the library catalogue but not the articles contained in those journals. Could placement of articles in catalogue be automated and so increase visibility?

3. What we did... 1 Developed a standard for metadata transfer from a publisher to a library catalogue. Based on RSS 2.0 and ONIX SRD. Standard is simple to use and implement but flexible. Released project deliverables into the public domain: http://sourceforge.net/projects/tocross

4. TOCRoSS architectural design TOCRoSS Feed Listener Server Config Library OPAC Journal Aggregator ? ? ? ? Processor Publisher RSS feed Processor MARC conversion

5. What we did… 2 Imported one volume of article metadata into the Derby OPAC (6,000 records). Automated the ongoing import of data. Conducted user testing –Well received by undergraduates, faculty and librarians. –Demonstrated it was possible to discover articles in the OPAC and link to the full text.

6. Issues raised… Managing data after it has been imported: –Quantity of data in the OPAC (ability of server to cope, ageing old data) –Not swamping records for other content items (books, etc.) –Changes to subscriptions –Changes of publishers Tracking usage