DataGuide (DG) data base

SC

- short code. This is the unique identifier for a record. SC is constructed automatically by the system from the first author's name, the last two digits of the year of publication, and a letter. This letter is appended only as necessary for uniqueness. For example : SC=ANTIPOV 78D;

R

- experimental document reference in PPDL. Allowed forms depend on the type of the document (i.e. on the value of TY). They are

1) for TY = JOUR;

R = < PPDL journal abbreviation > < volume > , < page > ; for example: R = NP B103, 255;

2) for TY = PREP; (or TY = CPRE,PROP,THES):

R = < report number > ; we use the following form:

R = < PPDL institute abbreviation > - < two digit year > - < preprint number > ;

for example: R = IFVE-86-101;

3) for TY = BART;

R = < conference abbreviation > - < two digit year > , p. < page >

for example: R = ROCHESTER-60, P. 1128;

4) for TY = PRIV;

R = PRIV;

TY

- document type (TY is subordinate to R). Allowed document types are:

JOUR

- published article in journal

PRER

- unpublished preprint or report

BART

- article in book, conference proceedings ...

BOOK

- book

PROP

- experimental proposal

CPRE

- conference preprint (not proceedings)

PRIV

- private communication

COMP

- compilation, should be second entry of TY

RVUE

- review ( or ...), should be second entry of TY

ERR

- used for erratum, should be second entry of TY

THES

- thesis

D

- document date (D is subordinate to R)

AUTHORS

- is a pure node which serves to link a group of authors with one or more institutions. AUTHORS is constructed automatically by the system. It takes on no values but is just a grouping of other DE's.

A

- author's name (A is subordinate to R)

I

- author's institution (I is subordinate to R).

RR

- related reference

L

- document language, omit if English

T

- document title

TW

- virtual key data element (words extracted from title)

TA

- title augmentation

COL

- collaboration note

CONF

- meeting note

COMMENTS on the RECORD

CB

- bibliographic comment

CR

- comment on record as a whole; Mainly contain description on Discovery or Nobel Prise experimental Papers.

ABS

- document's abstract

QUESTION

- problems in encoding, if any

ANSWER

- may be added when the answer to the above encoding problem is known

EXPERIMENT DESCRIPTION

EXPERIMENT

- Node data element to connect information on particular experiment if there are data from the several ones

PR

- proposal short code (see SLAC-LBL list of proposals: compilation LBL-92 and data base http://......)

ES

- experiment status. For proposals only

AC

- accelerator code

DE

- detector code or name

PL

- polarization of beam (PL=BEAM;) and/or of target (PL=TARGET)

CE

- comment on experiment ( number of events, comments to size, set-up, etc.)

CD

- comment on data and results

REACTION DESCRIPTION

REAC-DATA

- is a pure node which serves to link the subordinate data elements (RE, B, DD). REAC-DATA is constructed automatically by the system. It takes on no values of its own, but is a grouping of DE's.

RE

- reaction studied (RE is subordinated to REAC-DATA) See PPDL for a description of the syntax.

B

- beam momentum (B is subordinate to REAC-DATA) the general form is:

B = < m1 >, < m2 >,..., < mi > < units > < momentum variable >

the momentum variable can have any of the following forms:

PLAB

- beam momentum in the lab frame

ELAB

- beam energy in the lab frame

TLAB

- beam kinetic energy in the lab frame

ECM

- total energy in the CM frame

PLAB/N

- beam momentum per nucleon

ELAB/N

- beam energy per nucleon

TLAB

- beam kinetic energy per nucleon

Q2

- special case for deep>-inelastic scattering

NU

- special case for deep-inelastic scattering

W

- special case for deep-inelastic scattering

W2

- special case for deep-inelastic scattering

DD

- data descriptor ( DD is subordinate to REAC-DATA)

FSP

- contains a list of particles in the final state. Particles produced in resonance decays are not included in FSP. All particle names are codes which are given in PPDL. FSP is a virtual key, i.e. it is missing in the record itself, but it is possible to retrieve the record with the given value of FSP.

It is possible to search for particles with desired properties, due to an on-line vocabulary of particles with almost all general properties. FORMAT:

FSP PROP(...);**

where the ellipsis represents the desired property. The ' ' is necessary for the BDMS/4 query procedures, and should be understood to mean "contains" in this usage. The following properties are allowed:

HADRON - no appended value allowed

LEPTON - no appended value allowed

MESON - no appended value allowed

NUCLEUS - no appended value allowed

HYPERON - no appended value allowed

BARYON -

CHARGED -

STRANGE -

CHARMED -

ISOMUL -

BEAUTY -

MASS -

The meaning of each property is transparent. Most properties can have a value appended (with the exception of the first five properties), for example - CHARGED=-2, means particles with charge = -2. The value consists of an operation, selected from the following list, followed by an actual value.

Allowed operations:

=

equal to,

>

greater than,

< >

not equal to.

The presence of any property in the query string means that this property is at least not equal to zero, unless zero is explicitly requested. So, the strings

FIND FSP < PROP(CHARGED=0);** and

FIND FSP < PROP(CHARGED);**

One can list more than one property in a single query. In that case you must separate them by commas and they are understood to be "AND-ed" together. EXAMPLES:

to find all hyperons (FI:=FIND),

FI FSP < PROP(HYPERON);**

to find all negative charged hyperons,

FI FSP < PROP(CHARGED 0,HYPERON);**

to find all mesons with mass greater than 2. GeV and with CHARGE=+1,

FI FSP < PROP(CHARGED=1,MASS > 2.,MESON);**

Note, please! In the case of any contradictions in the query the only last value will be used! For example by the query

FI FSP < PROP(CHARGED=1,CHARGED=0,MESON);** only mesons with CHARGE=0 will be found.

BP

- beam particle code. It is similar to FSP. Search on particle properties also allowed.

TP

- target particle code. It is similar to FSP. Search on particle properties also allowed.

PARTICLE DESCRIPTION

PART-PROP

- a pure node which serves to link the subordinate data elements P and PP.

P

- particle studied (is subordinate to PART-PROP).

PP

- particle property (is subordinate to PART-PROP).

SERVICE ELEMENTS

DEN

- date and time of entry into system. DEN is constructed automatically by the system

DCH

- date and time of last change. DCH is constructed automatically by the system

SB

- status of document record encoding, plus encoder's initials

AV

- signifies if a hard copy is available