Important: This file is obsolete and only kept for purposes of documentation. Click here to get the current version.
The following are guidelines for mathematical journals included in the Electronic Library of Mathematics (ELibM). This library is a broadly based electronic distribution and archiving network for mathematics. It is provided by the European Mathematical Information Service (EMIS) under the auspices of the European Mathematical Society (EMS). Main URL: http://www.emis.de/
To relieve editors of awkward physical responsibilities, ELibM is willing to set up and hold the master posting (including all versions in all provided formats).
This document describes the technical procedures for automatic document delivery that will enable the EMIS system to process new journal issues by the use of fully automated procedures.
Any journal issue delivered to EMIS consists of
a) the single articles
b) contents and summary information
The single articles should be provided as Postscript, DVI, or TeX files. An additional special contents file should contain table-of-contents information and references to the respective article files (basically the file names). The format of this file is in detail described below. All these files should be put in one empty directory and delivered to EMIS (see below for the details).
While standards may change in the future, currently a complete PostScript file containing all the font information should be made available for every article in a journal participating in ELibM.
Provision of additional file formats (TeX, DVI, etc.) will be at the discretion of the editors of the corresponding journal. The contents of all versions should essentially agree, although there is no requirement that they all share any particular style.
Filenames should have a common structure. If there are multiple versions (DVI, Postscript, TeX) of the same article, the basename of the file should be the same (e.g. "mumble.dvi", "mumble.ps" etc.).
A special contents file will be used to link the bibliographic information to the real articles. This file will be used to generate all the necessary index- and table-of-contents pages as well as individual journal articles homepages out of the editor-provided information.
The editor-provided information will also be used for the public display of all articles in the framework of the CAP-EMS Database of current mathematical publications (under construction), and for the faster processing of bibliographic references at Zentralblatt fuer Mathematik.
Furthermore, it will provide the basic means of enabling online delivery of the publications irrespective of protocols and formats. This is an important point when it comes to technology changes.
The contents file is the core for all dissemination activities wrapped around the single articles, and its preparation requires special care.
An example contents file is give in the
appendix.
This example was used to create these
journal pages automatically.
The file consits of the following parts:
The format identification is a simple line stating
@version: EMIS-j-1.0
The general information on the issue gives
@journaltitle: (required) @ISSN: (optional) @year: (required) @volume: (required) @issue: (required) @remark: (optional)
This section is ended by a line stating
@EOH
Next, the single articles are listed:
@author: (required) @affiliation: (optional) @title: (required) @language: (required if other than English) @pages: (optional) @classification1: (optional) primary MSC classification @classification2: (optional) secondary MSC classification(s) @keywords: (optional) English keywords @abstract: (optional) @filename: (required) without filename extension (dvi,ps,...)
Fields marked as "required" must be given for every article. Fields marked as "optional" can be given as an additional information. They will be used to construct more convenient access paths to the articles and improve searchability, quality, and usability of the final product.
Each article is ended by a line stating
@EOI
An example contents file is give in the
appendix.
This example was used to create these
journal pages automatically.
All the above mentioned files should be put in one empty directory and delivered to EMIS. Preferrably, the directory should be put into one archive file using the tar command. This tar-archive should optionally be compressed using the gzip (not "zip"!) or compress command. The resulting file should be copied via ftp to a special incoming area on the EMIS server (please ask the EMIS tech. admin. for details). Finally, an e-mail message should be sent to the EMIS admin., announcing the availability of the new issue.