DIENST-ETRDL How to compile the Bibliographic Fields


Title

This is the title of the work as assigned by the author.

This field should include the complete title with all the subtitles, if any.

Format: <free text>

Example: Real-Time Multiprocessor Systems: Performability Evaluation

 

Obligatory field


Author(s)

The name of the author(s) of the document.

If there is one author for the document, use the following syntax:

Last-Name, First-Name

E.g.: Rossi, Mario

Otherwise, if there is more than one author, use the following syntax:

Last Name1, First-Name1 and Last-Name2, First-Name2 and Last-Name3, First-Name3 and ...

E.g.: Rossi, Mario and Bianchi, Paolo and Verdi, Carlo

 

Obligatory field


E-mail

The e-mail address of the person to be contacted with respect to the document. Enter the address with the following syntax:

name@domain

 

Obligatory field


Telephone

The telephone number of the person to be contacted with respect to the document.

 

Optional field


English Abstract

The abstract of the document. All documents, whatever their language, must have an abstract in English.

Format: <free-text>

 

Obligatory field


Other Language Abstract

If appropriate, please also include an abstract for the document in the source language and indicate the language using the pulldown menu.

Format: <free-text>

 

Optional field


Language of the "Other Language Abstract"

Select the language using the pulldown menu.

 

Obligatory field when the "Other Language Abstract" field has been used.


Publisher

The organization primarily responsible for the intellectual content of the resource. Please select the appropriate institution from the pulldown menu.

 

Obligatory field


Language

The language in which the document is written. Default is English. Otherwise, please select the appropriate language from the pulldown menu.

 

Obligatory field


Type

Indicates the type of publication (Technical Report, Thesis, EC Deliverable, Proceedings, Ercim News, Preprints, Project Reports, Others) as assigned by the issuing organization. Please select the appropriate type from the menu.

 

Obligatory field


Date

The publication date (normally the date of submission to the system).

The format is Year (four digits) Month (two digits) Day (two digits) as defined in ISO 8601 (Date and time format ).

Example: 1998-07-22

 

Obligatory field


File Name

This is the full pathname of the local file containing the document.

Example: C:\Documents\my_document.ps

Multiple files can be associated with the same bibliographic document. In this case, the file names must be entered one by one.

The file(s) will be transferred to the remote server.

If abstract only is selected, no file transfer will be executed.

 

Obligatory field unless only the document abstract is being inserted.


File Format

Indicates the file type. Select the appropriate file type format from the menu.

 

Obligatory field unless only the document abstract is being inserted.


Subject Indexing

The ERCIM DL provides three fields for the subject indexing of documents:

You are free to use one, two, or all three of these fields to describe the content of your submission. We encourage you to enter terms from at least one of the two classification fields.
ATTENTION: at least one of three subject fields must be filled in.


General instructions for indexing and classifying documents

There are some general principles one should adhere to when assigning classification codes/descriptors.

Originally classifications were designed with the "one document-one class" principle in mind. Try to assign as few codes as possible to a document while still covering all essential subject matter.
One way to do this is to first determine a "primary" code and assign it, i.e. a single class which best reflects the topic of the paper. Then proceed to assign as many "secondary" codes as necessary to cover the rest.

A good way to find the most specific appropriate term is to proceed "top-down" through the classfication until the next level of specificity is too narrow for your needs. However, note that the AMS-MSC schema also offers analytical access.

Always be as specific as possible.

Examples:

  1. ACM-CCS
    The examples of the ACM-CCS codes/descriptors here below refer to the following ACM-CCS section:

    D. Software

    If you are using the ACM-CCS schema and your document deals with concurrent programming, enter the code/descriptor

        D.1.3 Concurrent Programming

    and not the broader code/descriptor "D.1 PROGRAMMING TECHNIQUES"

    If your document deals with distributed programming, enter the uncoded descriptor "Distributed programming" adding it to the coded descriptor of higher level. See the example below:

        D.1.3 Concurrent Programming: Distributed programming

    ATTENTION: Note that in the example above the ": " symbol must be inserted between the coded descriptor "D.1.3 Concurrent Programming" and the uncoded descriptor "Distributed programming".

    The ACM-CCS allows the use of proper names as "implicit" descriptors, e.g. names of programming languages or persons can be entered under the appropriate alphanumerical code although they are not explicitly given in the ACM-CCS.

    Example: with code D.3.2 Language Classifications, you could enter "C++" in the form

        D.3.2 Language Classifications: C++

  2. Please refer also to the guidelines provided by ACM for using its Computing Classification Schema (http://www.acm.org/class/1 998/ccs98-intro.html)

  3. AMS-MSC
    The examples of the AMS-MSC codes/descriptors here below refer to the following AMS-MSC section:

    18Exx Abelian categories
    • 18E05 Preadditive, additive categories
    • 18E10 Exact categories, abelian categories
    • 18E15 Grothendieck categories
    • 18E20 Embedding theorems [See also 18B15]
    • 18E25 Derived functors and satellites
    • 18E30 Derived categories, triangulated categories
    • 18E35 Localization of categories
    • 18E40 Torsion theories, radicals [See also 13D30, 16S90]
    • 18E99 None of the above, but in this section

    If you are using the AMS-MSC schema and your article deals with Grothendieck categories, enter the code/descriptor

        18E15 Grothendieck categories

    and not the broader term "18Exx Abelian categories"

    The membership of a specific term in a broader category is implicitly evidenced by the code. Only if the document really deals with a broader group of topics should the broader term itself be explictly assigned.

    Please refer also to the guidelines provided by the AMS for its MSC schema (http://www.ams.org/msc/).


Comments and errata corrige are welcome! Please email them to etrdl@iei.pi.cnr.it