Journal Structure

Structure 1

All files should reside within the directory tree of one directory, the home directory of the journal. The home directory shall contain the home page of the journal, which should be named index.html or index.htm.

Example:  Let us assume here and in the following that /usr/local/httpd/htdocs/EEJ/ is the home directory of EEJ, the "Example ELibM Journal". In this case, the home page is the file /usr/local/httpd/htdocs/EEJ/index.html. The URL of this document would look something like The corresponding EMIS URL will then most probably become

The main directory for HTTP documents assumed above to be named /usr/local/httpd/htdocs/ will be referred to as ~/ in the following, so that ~/EEJ/ becomes the root node of the journal's directory tree.

Caveat: In particular, images and other graphical elements must reside underneath the home directory. This is needed to ensure reliable and easy mirroring of these pages in ELibM.

Example: The journal logo of EEJ may be located in ~/EEJ/images/EEJ.gif. Images must not reside in ~/images/EEJ.gif, because ~/images/ is not a subdirectory of the home directory.

Structure 2

All links to journal pages or graphical elements should be relative links, here relative means that paths should be given relative to the home directory (the root of the journal directory tree).

Example: The home page of EEJ contains a link to the journal logo; this link should look as follows:

<img src=images/EEJ.gif>

because images/ is the path ~/EEJ/images/ relative to the home directory, the root of the journal directory tree.

Note: Absolute linking means that the URL is included in the link, such as in

forbidden: <img src=>

Caveat: In particular, all graphical elements have to reside on the same web server. If, for example, the journal's home page has the URL, the images must not be under, even if has the same IP number as

Structure 3

The home page should contain links to tables of contents of all journal volumes resp. issues that are present on the website. The journal volumes (and possibly issues) should be located in subdirectories of the home directory. Preferrably, the volume and issue numbers should also  be the names of the directories. Contents files should be made for either the whole volume or the single issues, not for both.

Example: The contents file for Volume 5, Issue 1 of EEJ is located in ~/EEJ/5/1/index.html, the contents file for Volume 5, Issue 2 is located in 5/2/index.html (relative to the home directory). The journal's home page contains thus the following links:

Volume 5 (1994): <A HREF="5/1/">No. 1</A>, <A HREF="5/2/">No. 2</A>

Alternatively, the whole Volume 5 (all issues) may be contained in one directory, with contents page 5/index.html (relative to the home directory). In this case, the home page would simply contain the link

<A HREF="5/">Volume 5 (1994)</A>

Structure 4

The content page of a volume or issue should contain links to separate abstract pages for each document of the volume (issue). These abstract pages should be in the same directory as the content page and may be named by the document number (e.g., 3.html for the third document in that colume resp. issue), by the first page of the printed article (e.g., 133.html for a document starting with page 133), or in some other way.

Example: The content page for Volume 5, located at 5/index.html, contains the following link:

H. Hermix: <A HREF="5/1.html"> On qualitative properties of residual equations on supercomplex subdomains</A>

and this article is the first of this volume.

Structure 5

The abstract page of an article is recommended to contain the following information:

  • metadata (see Section 3) (optional)
  • authors' names
  • title of article (with English translation)
  • MSC classifications (optional)
  • keywords (optional)
  • abstract (optional)
  • links to the article document files in DVI, PostScript, or PDF formats

The document files should preferrably reside within the same directory as the abstract page (and thus, in the same directory with all the document files of the given volume resp. issue).

Note: The naming of the document files is not specified. Possible schemes are:

  • last names of authors, e.g.: hermix.dvi., hermix.pdf
  • volume, issue, document number information: 5_1_1.dvi,, 5_1_1.pdf

European and International Mirror Servers

The EMIS services are available from a number of mirror sites that replicate the whole contents of the server.