[SJ Logo]SuperJournal Data Handling: Recommendations for Publishers

Home | Search | Demo | News | Feedback | Members Only

SuperJournal Conference, Birkbeck College, London, 21 April 1999

Ann Apps, Manchester Computing, University of Manchester

Recommendations on Journal Data

SuperJournal journal data production processed the data from receipt to data load. It involved writing the data conversion and data display software, and setting up the production process, as well as the actual handling of the data. The journal data was generally supplied as full articles with accompanying article metadata.

Article metadata was supplied to SuperJournal in SGML. Using SGML aware software, the metadata was processed not just for its display but also to derive tables of contents at all levels in the journal/issue hierarchy, again held in SGML, which effectively catalogued the journal data held within SuperJournal. The choice of DTD was left to each publisher. From analysis of those used in SuperJournal we would recommend:

Recommendations on Data Display

Data display included enhanced data functionality within the SuperJournal application. Most journals were supplied to SuperJournal with full articles in PDF format. Some also included SGML full articles, which was converted to HTML.

Recommendations on Usage Data

Usage data in the log files was processed on a monthly basis before the resulting extensive usage statistics were passed on to HUSAT and included on the SuperJournal Web site. The SuperJournal logging requirements were far more extensive than for a usual electronic journal application because of the nature of the project, but the processing required should not be underestimated.

User feedback data was sent to the SuperJournal email address.



This web site is maintained by epub@manchester.ac.uk
Last modified: May 14, 1999