GEOINFORMATICS RESEARCH PAPERS, VOL. 3, BS1001, doi:10.2205/2015BS016, 2015


Record of science technologies. I. Online journal

V. A. Nechitailenko

Geophysical Center RAS, Moscow, Russia.

Abstract

[1] The development of technologies for record of science is one of the important parts of the current revolution in science. i.e. transition to the so-called "Fourth paradigm" for science. Scientific article today involves the insertion of modern data display and analysis, dynamic and interactive components, as well as compatibility with the latest modern systems of indexing and dissemination of scientific content. This article examines the concept and results of R&D in the electronic publishing area carried out in the Geophysical Center RAS, which has more than half a century history of publications in geophysics, in particular the results of research on international geophysical projects, and active participation in international activity in this field.

Introduction

[2] Articles and books containing the results of research in geosciences are among the most complex types of scientific publications. This is due to the fact that most of it, along with the text (often only a small portion of the volume of publications), also presents a complex mathematical and/or chemical text, graphics, often voluminous and complex that requires equipping articles with various means of visualization and multimedia.

[3] ELXpaper (ELectronic eXtended paper style) – LaTeX package is designed for journals and books published by Geophysical Center RAS. The package is an extension of the standard class article.cls and supports two-column journal format, internal and external active hyperlinks, monitoring "anchor-target" compliance and generating error or warning messages while the source translation. The result is presented in DVI and PDF formats of translated document, as well as in XML meta descriptions of published documents for registering the latter with CrossRef (in accordance with the XML Schema CrossRef 4.3.3.) and loading to Scientific Electronic Library (eLIBRARY.RU) (in accordance with the XML Schema eLibrary CE 7.1.4.1284).

Software Environment

[4] Taking into account the above-mentioned features of publications in geosciences, LaTeX publishing system seems to be the most preferable[1] . Particularly interesting is the ability to generate XML meta descriptions for index systems simultaneously with the generation of jobname.pdf, jobname.dvi and other auxiliary files during translation of the original text of the article, typed in LaTeX. This translation requires an expansion of the standard LaTeX class (article.cls or book.cls) with the set of macros that describe the semantic definitions included in the corresponding XML schemas.

[5] This package is the component part of software developed for supporting full cycle of article's preparation and publication, from writing and marking up LaTeX source file to generation PDF, HTML, and EPUB3 versions of the article. We aimed to minimize an amount of work at preparatory stage, i.e. markups, composition, hyperlinking, etc., as well as minimize staff qualification at the TeX nician level (as defined by D. Knuth [1992]).

[6] An example of such a solution was proposed by the author [2011] and has been successfully used as a basic tool for publication of GC RAS journals. LaTeX simpletexml package provided generation "on the fly" XML meta descriptions for the so-called CrossRef response page.

[7] Unfortunately, LaTeX as a programming language is not universal. Output XML files can be easily generated from the input stream if all semantically important elements are defined directly. If the sets of these elements are presented in the LaTeX source file as fragments of a relational base with a number of cross-referenced links, or the source file includes multilanguage fragments, generated XML files require postprocessing using programming or scripting tools. It should be emphasized that this approach is not universal and can not, in particular, be considered as a way to convert any arbitrary LaTeX document into its XML version.

[8] This article is an attempt to write a three-fold document which is (i) an article describing concept and approach to creating an effective tool for online publishing, (ii) a sample of article produced using this tool, and (iii) a template for authors and typesetters.

[9] Considered here ELXpaper package retains a number of components of the simpletexml package, but significantly extends the capabilities of providing, besides other things, the generation of meta descriptions in accordance with the eLIBRARY.RU XML Schema. The package also contains a number of macros required for conversion of the source LaTeX document to XHTML/EPUB3 formats.

[10] The problem of converting LaTeX source files to ebooks is actually the problem of converting LaTeX to XHTML. The last step – arranging the XHTML into EPUB3 archive – is rather obvious. Correct converting LaTeX to XHTML in general case is not possible, even theoretically, because TeX/LaTeX generically is not SGML-compatible. The partial solution can be found if we restrict the used LaTeX style to fixed list of commands and redefine some of them (those which have semantical meaning) to emulate XML-compatible structure. At the same time we can ignore commands which have no semantical meaning and used only for presentational needs. They should be replaced with CSS definitions developed for any particular journal, book, etc.

[11] With these limitations creating of not so comprehensive converting software becomes possible. The sample of such solution is realized by author [2015] and was successfully used for converting "in one click" the LaTeX source file of this article to PDF, HTML5, and XHTML/EPUB3.

[12] Perhaps even more important factor is that the documents published in XML-compatible format are more suitable for machine processing in indexing and reference systems, at least at a representative level.

Packet Structure and the Basic Options

Packet Structure

[13] ELXpaper package extends and modifies article.cls class and represented as LaTeX file elxpaper.sty. Additional style files are called directly from the package ELXpaper except hyperref package, which is called from the preamble of translated articles for easy switch on/off of some options of hyperref package, in particular, disable generating PDF table of contents when working with text in a language not supported by the current version of Adobe Reader. The package defines the following components and commands:

and macros that are included in the preamble of LaTeX version of the article, and commands used for CrossRef and eLIBRARY.RU metadata.

[14] Generation of Article Metadescription. For this purpose the set of macros, comprising the steps of creating and opening files jobname.xml (for CrossRef) and jobname-neb.xml (for eLIBRARY.RU) are followed by recording elements in them, selected from the input data stream into a two- or three-step process of translation of the document (article). Supported in LaTeX opportunity of multipass translation allows to avoid including in the original document of some secondary values, such as the number of pages, authors, affiliations, and other elements necessary for the correct formatting of the article, considering, in particular, the syntax used for language (in our case, English and Russian). In general, this process takes place "behind the scenes", XML files are created along with other additional files (jobname.pdf, jobname.aux, jobname.log etc.).

[15] Hyperlinks to Internal and External Objects based on macro definitions of hyperref package. Hyperlinks to internal floating objects are defined as "behind the scenes", that allows to simplify typeset and eliminate typesetting errors. The links to documents with known DOI indices are also based on hyperref package definitions.

[16] Supported Styles. ELXpaper package supports the following styles of journals:

[17] This list could easily be expanded as made, for example, in one of our first developments (package agupaper.sty).

Basic Package Options

[18] The following options should be defined in the ELXpaper package before it starts:

[19] The options' first values are set by default. Alternative options should be explicitly defined. For example, this document was translated by setting options silent,pdf,rus, par, i.e. \usepackage[silent,pdf,par]{elxpaper}. The number and order of customizable options are arbitrary.

[20] Both latex or pdflatex drivers can be used for translation of articles (documents) with elxpaper.sty package. Version 1.0 of the package together with a brief guide and auxiliary scripts is available on the GC RAS website dedicated to electronic publishing (elxpaper.zip).

Structure of the Paper

[21] Article source file in LaTeX prepared for translation should have the following structure:

\documentclass[twoside]{article}
\usepackage[<options>]{elxpaper}
\usepackage[<options>]{hyperref}
<preamble_text>
\begin{document}
<title/author[s]/affiliation[s]>
\abstract{<abstract_text>}
<structured_article_text>
[\acknowledgement[s]{<text>}]
\begin{references}
<reference list>
\end{references}
\noreferences - used if reference list is empty
[\appendices]
[\supplement] - section for electronic supplement
\end{document}

Preamble

[22] The preamble should include the following minimal set of parameters:

\journalid{<journal_code>}{<volume>}{<issue>}
{<publication_date>}
\cpright{<copyright_holder>}{<copyrigth_year>}
\paperid{<reserved_(CCC_code)>}
{<article_number_in_issue>}
\papertype{<article_type = RAR|EDI|REV|ABS|REP|COR|
MIS} % required by eLibrary XML Schema
\papercode{<DOI_suffix>}
\lefthead{<running_head_(first_author)>}
\righthead{<running_head_(short_title)>}
\received{<day>}{<month>}{<year>}
[\revised{<day>}{<month>}{<year>}]
\accepted{<day>}{<month>}{<year>}
\published{<day>}{<month>}{<year>}
\indexterms{<keywords_from_standard_list>}
\authaddr{<name_and_address_of_author[s]>}

[23] Keywords defined by the author are not included in the preamble. Instead they are placed inside the article's body just before the abstract. This is due to the fact that XML schema eLIBRARY.RU requires to submit each author's keyword individually.

[24] The <journal_code> is the main parameter settings, determining first, the choice of the journal from the number of supported by the package, selection fonts and composition of the title page of the article, as well as journal meta parameters such as ISSN code, et al.

[25] Codes of the following journals are defined as follows:

BS Geoinformatics Research Papers
ES Russian Journal of Earth Sciences (RJES)
NZ Vestnik Otdelenia nauk o Zemle RAN
PO Geophysical Papers Online – Preprints
MS Manuscript (unformatted article version)

[26] The parameter <DOI_suffix> is a string of 12 characters. The suffix may be arbitrary. Usually it is composed according to the rules set by the publisher. For GC RAS journals the first four characters – the year of acceptance of an article for publication, the fifth and sixth characters – journal code (capital letters), the last six characters – the registration number of an article. For example, DOI suffix of the original version of this article, published in Russian in December 2014 is 2014BS015.

[27] The running head is composed of two parameters \lefthead and \righthead, defined in the preamble. Parameters \received, \revised, \accepted and \published are used to generate the imprint data.

[28] The parameter \authoraddr contains the address(es) of authors in the following format: A. First, B. Second, First Organization, City, State/Region, Country (email address). If authors present more than one organization it is necessary to add additional instructions \authoraddr, whose number must match the number of organizations.

[29] Some additional parameters, such as \subident, \xmldepositor, \xmlregistrant are also included in the preamble (details are given in the ELXpaper package).

Title Page

[30] The main elements of the cover page are inserted after the command \begin{document}. Among them \title{ <article_title>}, set of commands describing the author(s), organization(s) and their internal links, set of keywords and the abstract content (\abstract{<abstract_text>}).

[31] A description of each author includes seven parameters, of which 1–3 and 5 are mandatory, others may be absent.

\author{<author_number>}{<last_name>}{<given_names_
or_initials>}{[<suffix>]}{<organisation_number>}
{[<alternative_organisation>]}{[<initials>]}

For example,

\author{1}{Bender}{Ostap-Suleyman Berta-Maria}{}
{1}{}{O.-S. B.-M.}
\author{2}{Jonson}{Joe H.}{}{2}{}{J. H.}

or

\author{1}{Bender}{O.-S. B.-M.}{}{1}{}{}, \author{2}{Allen}{J. H.}{}{2}{}{},

Here <suffix> – name suffix, e.g., Jr., Esc. and the like.

[32] The description of each organization consists of five parameters, all of them except the fourth one, are mandatory, for example,

\affil{<organisation_number>}{<organisation>}
{<city>}{<[region/state]>}{<country>}

[33] Below is an example of authors' block description. Some complexity of the structure of the block is caused by the necessity to transfer the set of semantic elements and quantitative characteristics (number of authors, organizations, etc.) to the TeX engine. The TeX engine does not allow to provide character-wise analysis, moreover, the system does not work with arrays. In the process of interpreting the input stream, we need, on the one hand, to ensure independent processing of input (semantic) elements, without which it is impossible to construct a valid jobname.xml file, on the other, to format grammatically correct strings (with the correct punctuation) before these strings will be sent to an output stream. This problem can be solved by the two-step translation. At the first step the basic syntactic structure is determined by the analysis of input parameters, which are written then into jobname.aux file, at the second step, with the use of TeX registers, semantically and syntactically correct line of authors, organizations, string citation lists of referred literature, etc. are formed.

\author{1}{First}{A. B.}{}{1}{}{}
\author{2}{Second}{C. D.}{}{2}{}{}
\author{3}{Third}{E. F.}{}{3}{4}{}
\author{4}{Fourth}{G. H.}{}{5}{6}{}
\author{5}{Fifth}{I. J.}{}{1}{}{}
%
\affil{1}{Institute or Irreproducible Physics}
{Bigcity}{}{Gallardia}
\affil{2}{Institute of Cosmetic Physics}{Smalltown}
{}{Gallardia}
\affil{3}{Center of Paranormal Studies}{Miraclecity}
{}{Gallardia}
\affil{4}{Also at Virtual Affiliation}{Moon City}{}
{Gallardia}
\affil{5}{Unknown Affiliation}{Somewhere}{}
{Gallardia}
\affil{6}{Also at Institute of Cosmetic Physics}
{Smalltown}{}{Gallardia}

[34] The number of authors, which is used by template for putting commas correctly, is defined during the first translation and saved in the .aux file. A warning message appears on the screen and in the .log file with the request to repeat translation. Double translation is also necessary if the number of authors in the editing process was changed, though in this case the warning is not generated.

[35] Numbers of reference links to affiliations should be in ascending mode, i.e. 1, 2, 3, 4, 5, but not 1, 3, 2, 4. Repeating of reference already used is possible, e.g. 1, 2, 2, 3, 4, 1. See also the sample above.

[36] Basic and alternative addresses should be placed in the same order as in the authors' string. This is checked during the translation and warning is issued. Addresses of alternative affiliations may start with Also at, Formerly at, On leave from, and the like, as appropriate.

[37] Please look at the sample above. If the same affiliation is mentioned as a basic one (for the author Second) and as an alternative one (for the author Fourth) it should appear twice in the list of affiliations, the second time starting with Also at.

[38] The command \keywd{<value>} refers to one or group of words and phrases that are recommended for using as arguments in the context search. Below is the block of keywords selected for this article.

\keywd{scientific journal}
\keywd{electronic publishing}
\keywd{information technologies}
\keywd{record of science}
\keywd{semantic inclusions}
\keywd{metadescription}
\keywd{CrossRef}

[39] The \abstract{<abstract_text>} command is the mandatory component of the title page. At least the empty \abstract{} command should appear if the article has no abstract. It is necessary because this command starts the process of converting input to output and the formation of the title page. At the same time all other page elements are generated "behind the screen" using the data defined in the preamble.

Mathematical and Chemical Texts

[40] The in-text anchors to formulas should be marked as \eqref {<formula_number>} without parentheses (see formula (1) as an example), the program will insert their own. Automatical numbering of formulas is allowed only in cases where the LaTeX source file is used for the conversion to the PDF format only.

\begin{equation} \tag*{(1)} \mathrm{Demo\quad formula}\qquad -> \qquad A + B = S \end{equation}

[41] In cases where the LaTeX source file is used for conversion it to HTML5/XHTML/EPUB3 formats, one must follow certain restrictions, namely: (i) displayed unnumbered equation should be included in

\begin{eqnarray*}
....
\end{eqnarray*},

while (ii) numbered equations should have a coercive numbering, i.e. corresponding target tag should be included in the

\begin{equation}\label{<formula_number>}
....
\end{equation}

[42] Using \eqnarray* (with asterisk) for an array of unnumbered equations is allowed. The use of \eqnarray (without an asterisk) for a mixed array of numbered and unnumbered equations should be avoided, as the current version of the software for conversion TeX to MathML does not support hyperlinks in such complex structures.

Lists and Tabulated Materials

[43] LaTeX supports basic formats of lists which are used to build a number of LaTeX's display-like environments, i.e. unnumbered (itemize), numbered (enumerate), and description (description) lists. With adding some LaTeX packages one can build rather complicated lists with inclusions of sublists and customizing the list elements. Not all of these features can be easily converted to HTML format and especially to more strong XHTML/EPUB formats.

[44] ELXpaper package contains a few commands to support fragmented and broken lists which are not used when converting source file to PDF. Some samples of lists, which are successfully processed by our software from LaTeX source to HTML5/XHTML/EPUB3 can be seen in the article doi:10.2205/2014ES000538.

[45] For arranging in-text tabulated materials LaTeX suggests a number of formats, like tabular, tabularx, tabulary, etc. For converting source file to HTML we recommend to use only tabular environment, because HTML format has no simple and effective tools to support sophisticated tabulated fragments. Note, that in opposite to tabulated material included into the float environment, in-text tabular appears in the same place as it was put in the source file. See the demo sample below.

Element 1 2 3 4 5 6 7
Li 3.1 2.8 3.4 3.1 2.9 1.9 2.5
Rb 5.0 8.4 7.8 10 10 12 17
Cs 1.6 0.88 2.9 2.8 2.1 3.2 5.1
Cr 1800 1500 1100 3000 1800 900 900
Mn 790 740 690 700 660 790 710
Co 78 30 35 25 115 40 35
Ni 2000 2000 2000 1800 1900 2400 2200
Cu 25 73 25 63 90 30 20
Zn 56 91 51 74 100 73 79
Note: numerals 1 through 7 correspond to the numbers of cubes in Figure 1. (See doi:10.2205/2015ES000546)

Floating Objects

[46] Floating objects (floats in LaTeX terms) are elements of articles, not having a fixed point in the text. Place of their appearance is determined by the program in the translation process in accordance with the algorithm implemented in the used class or package. The main float environments processed by the current version of ELXpaper, are figures, tables, and plates.

[47] In-text references to Figure 1 and Figures 1 and 2 should be marked up as \figref{1} and \figrefs{1 and 2) or \figrefs{1, 2}.

[48] In-text references to Table 1 and Tables 1 and 2 should be marked up as \tabref{1} and \tabrefs{1 and 2) or \tabrefs{1, 2}.

[49] In-text references to Plate 1 and Plates 1 and 2 should be marked up as \plaref{1} and \plarefs{1 and 2) or \plarefs{1, 2}.

[50] The value in curly brackets for the expressions of the type Figure 2a, Table 3b, use only the digital part number, i.e. \figref{2}a and \tabref{3}b, since it is the numeric part of numbers used by the appropriate macro to generate "anchor-target" pairs.

Figures

[51] Graphic files should be named in the order they are mentioned in the text, for example, f01, f02, etc. The full name of the graphic file may be arbitrary, but it is recommended to use \paperid command of the preamble as the prefix in graphics name. That is, the full name of the graphic file in the caption, i.e. the second figure of the article should be \setimage{}{}{}{<height>}{2010nz000062-f02} for \paperid{2010NZ000062}.

[52] The sample of figure description is given below:

\begin{figure*}[t] % Fig 5
\figurewidth{35pc}
\setimage{}{}{}{33pc}{2010nz000062-f05}
\caption{Areas of daily driven fire from June to
August 2010 in the European part of Russia (a) and
the Moscow region (b) ("Aerocosmos" data).}
\end{figure*}

[53] The generalized command for image file insertion \setimage{<x_shift>}{<y_shift>}{<width>}{<height>} {<image_file>} requires an image file in .eps format for translation to DVI/PS or in .png format for translation to PDF format. This selection is determined by specifying corresponding option of ELXpaper package. At least one value (width or height) should be given for proper scaling of image at the output. The \setimage command generates also a target mark matching to corresponding anchor incorporated into \figref command.

Tables

[54] There is no special requirements for composing tables until you do not plan to convert LaTeX document to XHTML/EPUB3 format. In the latter case some restrictions should be taken into account.

[55] The current converter LaTeX to XHTML/EPUB3 supports vertical or slanted text strings in tables. For rotating separate fragments of the text or table cells on arbitrary angle the environment turnbox, defined in the rotating package should be used, i.e.

\begin{turnbox}{<rotating angle in degrees>}
{<rotated object>}
\end{turnbox}

[56] To rotate on fixed angle $\pm90\mbox{°}$ one can use the macro \vtcell[<direction>]{<rotated object>}, which is a simplified version of the shown above construction. Parameter <direction> should have values: l to rotate to $90\mbox{°}$ anticlockwise, or r to rotate to $90\mbox{°}$ clockwise.

Table 1
Table 1

[57] The demo Table 1 was built using the following code:

\begin{table}[b]
\tablewidth{20pc}
\caption{VTCELL – Demo table with vertically
oriented column subtitles}\vspace*{6pt}
\begin{tabularx}{20pc}{XXXX}
\hline [-20pt]
\vtcell[l]{First column} &
\vtcell[l]{Second column} &
\vtcell[l]{Third column} &
\vtcell[l]{Fourth column} \vspace*{-1pc}
[-1pc] \hline [-7pt]
AAAA & BBBB & CCCC & DDDD
aaa & bbb & ccc & ddd \hline
\end{tabularx}
\end{table}

Table 2
Table 2

[58] The environment turnbox gives much more freedom in placing subtitles and other objects. See demo Table 2 which was built using the following code:

\begin{table}[b]
\tablewidth{20pc}
\caption{TURNBOX – Demo table with arbitrary
oriented column subtitles}\vspace*{6pt}
\begin{tabularx}{20pc}{XXXXXX}
\hline [4pc]
{\begin {turnbox}{40}{First column}\end {turnbox}} &
{\begin {turnbox}{50}{Second column}\end {turnbox}} &
{\begin {turnbox}{60}{Third column}\end {turnbox}} &
{\begin {turnbox}{70}{Fourth column}\end {turnbox}} &
{\begin {turnbox}{80}{Fifth column}\end {turnbox}} &
{\begin {turnbox}{90}{Sixth column}\end {turnbox}}
[4pt] \hline [-7pt]
AAAA & BBBB & CCCC & DDDD & EEEE & FFFF
aaa & bbb & ccc & ddd & eee & fff \hline
\end{tabularx}
\end{table}

Landscape Oriented Figures and Tables

[59] To rotate floats (tables and figures) on $\pm90\mbox{°}$ the environment \sideways[figure[*]|table[*]] should be used. It is necessary to replace \begin{figure} and \end{figure} with \begin{sidewaysfigure} and \end{sidewaysfigure} as well as \begin{table} and \end{table} with \begin{sidewaystable} and \end{sidewaystable}. For two-column floats the forms with asterisk (*) should be used, i.e. sidewaysfigure* and sidewaystable*.

[60] The rotating package is called from elxpaper.sty with the rotating option set to [figuresright] which corresponds to rotating floats on $90\mbox{°}$ anticlockwise. If the rotating option is set to [figuresleft] floats are rotated on $90\mbox{°}$ clockwise, the latter is not recommended by the most Russian scientific journals.

Internal and External Hyperlinks

[61] Along with the basic hyperlink commands included into hyperref package by Sebastian Rahtz and Heiko Oberdiek [2012], i.e. \url, \href, \hyperlink, \hypertarget, \eqref, \hyperref, \hyperdef, a few more commands are defined for internal links to floats and external links to documents with DOIs.

[62] A few samples of links to floats are shown in the Floating Objects section, samples of external links to documents with DOIs are shown in the Reference List section.

[63] Hyperlinks inserted by the author in the article text must be reconciled not only for correctness of their syntax, but also on the performance, i.e. they should be checked for compliance with the URL address or DOI index of requested document. The main command for the hyperlink is \href{<URL_address>}{<anchor_text>}, for example, \href {http://ebooks.wdcb.ru}{Geoinformatics Research Papers}.

[64] Sample 1

"... Dr. So-and-so published in Russian Journal of Earth Sciences an article related to..."

After marking up this fragment to LaTeX format we have

"...Dr. So-and-so published in \href{http://rjes. wdcb.ru}{Russian Journal of Earth Sciences} an article related to ...",

which then converted by \pdflatex engine to

"... Dr. So-and-so published in Russian Journal of Earth Sciences an article related to ..."

with the active hyperlink from PDF file to the shown address.[2]

[65] Sample 2

A fragment "...data obtained from AIRS device of AQUA satellite [http://mirador.gsfc.nasa.gov] ..."

in general case should be converted to

"...data obtained from AIRS device of AQUA satellite [\href{http://mirador.gsfc.nasa.gov}{http://mirador. gsfc.nasa.gov}] ..."

If both arguments of \href{<target_address>} {<anchor_text>} are equal the command \href{}{} can be replaced with the command \url{<target_address>}

[66] Both fragments, namely

"...data from AIRS AQUA [\href{http://mirador.gsfc. nasa.gov}{http://mirador.gsfc.nasa.gov}]..." and

"...data from AIRS AQUA [\url{http://mirador.gsfc. nasa.gov}]..."

produce the same result after \pdflatex, namely,

"...data from AIRS AQUA [http://mirador.gsfc.nasa.gov]..."

[67] However, if <target_address> is too long and the compiler can not break a string or breaks it incorrectly, the command \href{}{} becomes more preferable. In this case, the first parameter in the command (URL address or DOI index) is constant, which ensures the correct construction of hyperlinks, whereas the second parameter (<anchor_text>) may be forcibly torn inclusion of extra space at the desired point, as it is the second parameter which is displayed in the translated text, for example, as shown here: "... according to the AIRS data of AQUA satellite [http://mirador. gsfc.nasa.gov]...".

Hyperlinks to DOI Indices

[68] While forming the hyperlinks to the DOI indices hyperlink in the text consists of two parts: the DOI resolver address (http://dx.doi.org/) and DOI index, i.e. to form hyperlink to this article one should write http://dx.doi.org/ 10.2205/2015BS016

Reference List

In-text Reference Links

[69] In-text references to the items of Reference list, for example, fragment

"... as is shown in [Brown, 1967] effect ..."

must be converted into the LaTeX form

"... as is shown in [{\it Brown}\reflink{brow67} {1967}] effect ...",

and after translation to the PDF version looks as

"... As shown in [Brown, 1967] effect ...".

[70] For other form of reference the fragment

"Sweet [1958] showed that ...

must be converted to the form

{\it Sweet} [\reflink{swee58}{1958}] showed that...

and after the translation to PDF version it looks like

"Sweet [1958] showed that ..."

[71] The command \reflink{<citation_key>}{<year>} includes two parameters: <citation_key> and <year>. The first parameter, which is used as an anchor in "anchor-target" pair for the current hyperlink can be any text string, but must be unique in this article, the second parameter is the year of publication.

Format and Structure of the Reference List

[72] For historical reasons the journals published by GC RAS have format and structure of reference lists similar to that developed for AGU journals.[3]

[73] The format and structure of the reference list substantially modified in order to simplify their conversion to the structures defined in the CrossRef and eLIBRARY.RU XML schemas. In the reference list included links with the mandatory minimum parameters that allow processing and their inclusion in the bibliographic databases and search engines. Other links (private communications, work in the press, unpublished material, etc.) can be informally described in the text.

Table 3
Table 3

[74] Table 3 shows the format of the six major types of bibliography items supported by ELXpaper package. For each type defined mandatory parameters (marked with an asterisk) and the recommended settings (marked with a plus sign). At least one author must be included in the parameter \refauthf{}{}{}. If the names of the authors are not defined in the cited publication, it is possible to use the name of the editor(s) to fill in \refauthf with inclusion Ed[s] as a third (suffix) parameter. (See. Samples of reference... subsection in the LaTeX version of this article).

[75] If there are two or more authors the second and subsequent ones should be included in the parameter \refauth. In case of more than nine authors it is recommended to include the first three names with the addition of a parameter \refgroup{}. By default, the expansion (et al.) or (и др.) will be added to the output version of the document, depending on the language of the translated document. If the items of the reference list are presented in two languages, argument parameter \refgroup{} must be specified explicitly. The \endreference{} value may include information about the language of publication, update time of cited databases, etc. Inside the blocks describing items of the reference list, no punctuation characters are permitted, all necessary punctuation is added by the software during translation.

External Links From Reference List to Publications With DOI

Acknowledgment

Author would like to express the special thanks of gratitude to colleagues A. Astapenkova and E. Kedrov for their helpful discussions and valuable help in preparation of this article.

References

Hildebrand, A. R., G. T. Penfield, et al. (1991), Chicxulub crater: A possible Cretaceous-Tertiary boundary impact crater on the Yucatan peninsula, Mexico, Geology, 19, p. 867, doi:10.1130/0091-7613(1991)019<0867:CCAPCT>2.3.CO;2.

Goossens, M., F. Mittelbach, A. Samarin (1993), The LaTeX Companion, 530 pp., Addison-Wesley, London.

Knuth, D. (1992), The TeXbook, 483 pp., Addison-Wesley, New York.

Lamport, L. (1994), A Document Preparation System LaTeX, 272 pp., Addison-Wesley, London.

Mittelbach, F., M. Goossens, et al. (2006), The LaTeX Companion, Second Edition, 1087 pp., Addison-Wesley, London.

Naumova, V. V., A. V. Belousov (2014), Digital repository "Geology of the Russian Far East" – an open access to the spatially distributed online scientific publications, Russ. J. Earth. Sci., 14, p. ES1004, doi:10.2205/2014ES000538.

Nechitailenko, V. A. (2011), Manual to the SimpleTEXML package: 1. Structure and basic macrodefinitions, Vestn. Otd. nauk Zemle, 3, p. NZ1002, doi:10.2205/2011NZ000101.

Nechitailenko, V. A. (2015), Record of science technologies. II. Electronic book, Geoinf. Res. Papers, 3, p. BS2001, doi:10.2205/2015BS017 (in press).

Plyusnina, L. P., T. V. Kuzmina, G. G. Likhoidov, et al. (2015), Experimental modeling of platinum sorption on organic matter, Applied Geochemistry, 15, p. 777, doi:10.1016/S0883-2927(99)00092-X.

Brophy, J. G., E. M. Klein, M. A. Stewart (1999), Textural (Nomarski interferometry) studies of plagioclase phenocryst zonation styles in MORB dikes and lavas from the north wall of the Hess Deep Rift, Eos Trans. AGU, 80, no. 46, p. Fall Meet. Suppl., F985.

Sentman, D., H. Stenbaek-Nielsen, M. McHarg, J. Morrill (2007), Plasma chemistry of sprite streamers, Eos Trans. AGU, 88, no. 52, p. 52 (Abstract AE42A-08).

Liu, H.-L., J. W. Meriwether (2004), Analysis of a temperature inversion event in the lower mesosphere, J. Geophys. Res., 109, p. D02S07, doi:10.1029/2002JD003026.

Ma, J., D. W. Waugh, A. R. Douglass, S. R. Kawa, S.-J. Lin (2003), Evaluation of the transport in the Goddard Space Flight Center three-dimensional chemical transport model using the equivalent length diagnostic, J. Geophys. Res., 108, no. D6, p. 4201, doi:10.1029/2002JD002268.

Schrëder, M., M. Kënig, J. Schmetz (2009), Deep convection observed by the Spinning Enhanced Visible and Infrared Imager on board Meteosat 8: Spatial distribution and temporal evolution over Africa in summer and winter 2006, J. Geophys. Res., 114, p. D05109, doi:10.1029/2008JD010653.

Gaines, S., P. Hataway, S. Hipskin Eds. (1992), Airborne Arctic Stratospheric Expedition II [CD-ROM NASA/UARP-004], NASA Ames Res. Cent., Moffett Field, Calif.

McDougall, I., T. M. Harrison Eds. (1999), Geochronology and Thermochronology by the $^{40}$Ar/ $^{39}$Ar Method, 2nd ed., 269 pp., Oxford Univ. Press, New York.

Scholz, C. H., T. C. Hanks (2004), The strength of the San Andreas fault: A discussion, in Rheology and Deformation of the Lithosphere at Continental Margins, edited by G. D. Karner et al., Columbia Univ. Press, New York (in press).

Sweet, P. A. (1958), The neutral point theory of solar flares, Electromagnetic Phenomena in Cosmic Physics, edited by B. Lehnert, p. 123–134, Cambridge Univ. Press, New York.

Tullis, T., J. Tullis (1986), Experimental rock deformation techniques, Mineral and Rock Deformation: Laboratory Studies, The Paterson Volume, Geophys. Monogr. Ser., edited by B. E. Hobbs and H. C. Heard, p. 297–324, AGU, Washington, D. C.

Monger, J. W. H., J. M. Journeay (1994), Guide to the geology and tectonic evolution of the southern Coast Mountains, Open File Rep. 2490, Geol. Surv. of Can., Ottawa, Ont.

Schiarizza, P., R. G. Gaba, J. K. Glover, J. I. Garver, et al. (1997), Geology and mineral occurrences of the Taseko-Bridge River area, Bull. 100, B. C. Minist. of Employ. and Invest., Energy and Miner. Div., Geol. Surv. Branch, Vancouver, B. C., Canada.

Campbell, J. K. (1970), Mariner Mars 1969, report, Jet. Propul. Lab., Pasadena, Calif.

Kineman, J. J., M. A. Ohrenschall (1992), Global Ecosystems Database, version 1.0, A documentation manual [CD-ROM], Key Geophys. Rec. Doc. 27, Natl. Geophys. Data Cent., Boulder, Colo.

Brown, R. J. E. (1967), Permafrost in Canada, Map 1246A, Geol. Surv. of Can., Ottawa, Ont.

Henderson, T. (2000), High-pressure metamorphism in the western Llano uplift, M. S. thesis, Univ. of Tex. at Austin, Austin, Texas.

Hall, D. K., G. A. Riggs, V. V. Salomonson (2000), MODIS/ Terra Snow Cover 5-Min L2 Swath 500m, Version 4, Natl. Snow and Ice Data Cent., Boulder, Colo., http://nsidc.org/data/mod10_l2.html, October 2007 to April 2008 (Updated daily).


Received 6 March 2015; accepted 15 March 2015; published 25 March 2015.


      Powered by MathJax


Citation: Nechitailenko V. A. (2015), Record of science technologies. I. Online journal, Geoinf. Res. Papers Ser., 3, BS1001, doi:10.2205/2015BS016.


Generated from LaTeX source by ELXpaper, v.1.3 software package.