Memo CP-D/347
Date:
To:
From:
Subject:

15 November 2002
Distribution
M. Lammer
Report codes

During his conversion of the old CINDA file into the new CINDA 2001 format, Viktor Zerkinhas produced a list of all reference codes found in CINDA and compared them to the EXFOR
dictionaries. I have looked into all those report codes, which had no corresponding EXFOR
codes. The results are presented here.
1) Restriction of code length in CINDA 2001
An addition to Memo CP-D/246: the need to insert a blank before the report number if thecode is shorter than 4 characters, can be dropped (obviously also blanks required for journal
codes before the volume number). Also, longer codes can be accepted (cf. item (7) below:“…. simple corrections”).
2) Proposal for presentation of code in EXFOR Dictionary 6
As a requirement of coding rules, some of the codes in EXFOR dictionary 6 are so different
from the codes printed on the cover of reports, that I propose to add in all such cases (not justa few like CEC- or INR-) the actual code on the cover in the text of the expansion orsomewhere thereafter. This should avoid a number of coding errors (see part on coding errorsin (6) and (7) below) by compilers or related problems. Example:
EXFOR: PNR/SETR-R-25
code on cover: PNR/SETR
on 2 lines
R.0253) New codes (confirmed) for inclusion in EXFOR Dictionary 6
The “confirmed” codes, I have either found on actual reports or in INIS (in a retrieval or thebook IAEA-INIS-6: the INIS authority list for “report number prefixes”).
AES-

2SWDAE

Aktiebolaget Atomenergi, Studsvik, reports

BNWL-TR-(same expansion as BNWL-)

CEA-CONF-

2FR FR

Commissariat a L’Energie Atomique (NOTE: not confined to alab, includes publications by BRC,CEL,CAD,GRE,SAC,…)

GSI-J-2GERGSI(same expansion as GSI-)KAERI/GP-

3KORKAE Korean Atomic Research Institute reports

JINR-D6JINR-E4JINR-P12JINR-P14(same as other JINR- reports)

OKTAV-C-

2JPNOSA(same expansion as OKTAV-A-) Note: why not use full name
OKTAVIAN-? (see comment (1) above)

PNR/SETR-

2FR CAD(same expansion as PNR/SETR-R-) code on report cover e.g.:
PNR/SETR 65.010, to be coded as PNR/SETR-65-10;

RD/B/N-

2UK CEG(same expansion as RD/B/M-)

TIB/FICS-

2ITYITY

ENEA Dipmt. Tecnologie Intersettorali di Base/Div. FIsica e
Calcolo Scientifico reports; code on cover: TIB/FICS (83) 4(“ENEA” expanded: Comitato Nazionale Ricerca e Sviluppo
Energia Nucleare e Energia Alternativa)

4) New codes (unconfirmed) for possible inclusion in EXFOR Dictionary 6
These codes, found in CINDA, I could not confirm via the sources mentioned above. They
will have to be checked and confirmed by the responsible center, as well as the proposedlabcode and expansion, which are only my assumptions.
AD-A-

1USADOD origin: 1 entry in CINDA coded as AD-A009563, with
lab=4CCPLEB, comment indicates translation from book LEB;
INIS-6: “Defense Documentation Center, Alexandria, VA,USA, (assigned to unclassified documents …)”.

AE-RFT-

2SWDAE

AERE-NP/PR-

2 entries, both with lab 2UK ALD; code not found anywhere; could be missspelt, or confused with AERE- PR/NP- or AERE-NP/R-: to be checked.

ANL-AJD-

1USAANL probably same as ANL-

FOA4-D-2SWDFOA probably same as FOA4-A- and FOA4-C-

GA-B-?1USAGA suggests same as GA- (GA-A- and GA-C- found in INIS-6, butnot GA-B-), but lab in CINDA entry is 1CANCRC???

MON-C-

1USAUSA probably expansion as MON-N-;

UNC-PH/M-

1USAUNC found (libraries, INIS-6) only code UNC-, probably same.

(all entries have lab=2SWDAE, probably expansion as AE-)

5) Proposed or possible corrections for EXFOR Dictionary 6
AFWL-TDR-

does not occur in CINDA nor in EXFOR, but several entries in both withcode AFWL-TR-; neither code could be confirmed; to be checked by
NNDC (see EXFOR# 10022 and 12069).

AWRE-CNR/PR change to AWRE-CNR/PR- (add dash at end of code);
CEA-, CEA-N-, CEA-R-: according to INIS-6, published by different CEA labs (as item (3)above: CEA-CONF-) => propose to change lab to 2FR FR (or introduce
code for CEA).
IPNO-THchange to IPNO-TH- (add dash at end of code);

NIIAR-P1-

needs clarification (see also item (6) below): entry EXFOR40469 contains
NIIAR-P1-335, the corresponding CINDA entry contains NIIAR-P-335(possibly because of limited space); INIS sources contain only NIIAR-P; conclusion: NIIAR may have part -P1,-P2, etc. similar to JINR-, which
may have been partially omitted; has to be checked and clarified by CJD.

6) Obvious coding errors in CINDA
Several more such errors I could correct easily without checking the original reference.
EANDC(U)76U175

CINDA entry for Mo-97 RES, lab=2FR SAC: check and correct;

INDC(EUR)14374

this number does not exist (several entries);

NEANDC(E)-GE/R

CINDA entry for U-238 TOT 2ZZZGEL: check and correct;

NIIAR-

several ways of coding that are inconsistent and partially do notconform with coding rules; some have to be corrected:
NIIAR-P-335
NIIAR-P22(356)
NIIAR-1(360)
NIIAR-2(361)
NIIAR-P-5,
NIIAR-52

The different ways of coding NIIAR- reports support my proposal to include in the EXFOR
dictionary, in some doubtful cases, the codes printed on the report cover.
7) Coding errors in CINDA requiring simple corrections
The following coding errors can easily be identified and corrected by a small computer
program. In particular could corrections be implemented during conversion to CINDA 2001,
also because for some of the errors, the correct coding would exceed the field length foreseenin the old system, and hence cannot be corrected there. In most cases listed below, “no” stands
for report number and “yy” for year.
wrong coding

correct coding

comment

AAEC/AP-PR1986
AAECAP-PR-1986

AAEC/AP/PR-1986

correct coding exceeds field length;
total of 7 entries

AERE-PR/NPno

AERE-PR/NP-no675 wrong entries (only 1 correct)

AWRE-CNRPR/10

AWRE-CNR/PR-10

correct coding exceeds field length; 58 wrongentries

CEC(yy)-no

CEC-(yy)-no266 wrong entries; code on report: CEC(yy)no

EANDC(E)no

EANDC(E)-noover 1500 wrong entries

EANDC(J)22

EANDC(J)-22

5 wrong entries

EANDC(OR)no

EANDC(OR)-no85 wrong entries

EANDC(UK)151
EANDC(UK) 151

EANDC(UK)-151

3 wrong entries
73 wrong entries

FOA4-Ano
FOA4-Cno
FOA4-Dno

FOA4-A-no
FOA4-C-no
FOA4-D-no

total of 22 wrong entries
code on report (example): FOA 4 Rapport(printed on 2 lines)
A 4410-411

HEDL-TMEyy-no

HEDL-TME-yy-no

5 entries; on report: HEDL-TME yy-no

INDC(EUR)noINDC(EUR)-no264 wrong entries

JAERI- no
JAERI-C- no
JAERI-D- no
JAERI-M- no
JAERI-R- no

JAERI-no
JAERI-C-no
JAERI-D-no
JAERI-M-no
JAERI-R-no

total of 357 wrong entries

JUELSPEZ-no

JUEL-SPEZ-no

5 wrong entries

NAA-SR-TDRno

NAA-SR-TDR-no24 wrong entries

NEANDC(E)noNEANDC(E)-no18 wrong entries

NEANDC(J)no

NEANDC(J)-no24 wrong entries

NEANDC-J-no
NEANDC-Jno

NEANDC(J)-no

total of 69 wrong entries

NEANDC(UK) no

NEANDC(UK)-no4 wrong entries

PNR/SETRyy-no

PNR/SETR-yy-no

24 wrong entries; code on report: see (3);UKNDC(75)P71

UKNDC-(75)P71

or UKNDC-(75)-P71, or? code on report:
UKNDC (75) P71

Distribution:
oblozinsky@bnl.gov
vml@bnl.gov
nordborg@nea.fr
kellett@nea.fr
manokhin@ippe.obninsk.ru
maev@ippe.obninsk.ru
may@obninsk.ru
feliks@polyn.kiae.su
chukreev@polyn.kiae.sudunaeva@expd.vniief.ru
taova@expd.vniief.ru
varlamov@depni.sinp.msu.ru
chiba@earth.sgu.ac.jp
kato@nucl.sci.hokudai.ac.jp
oba@nrdf.meme.hokudai.ac.jp

yxzhuang@iris.ciae.ac.cn
cndc@mipsa.ciae.ac.cn
tarkanyi@atomki.hus.takacs@atomki.hu
hasegawa@ndc.tokai.jaeri.go.jp
vlasov@kinr.kiev.ua
kaltchenko@kinr.kiev.ua
ogritzay@kinr.kiev.ua
jhchang@kaeri.re.kr
ohtsuka@nucl.sci.hokudai.ac.jp
m.wirtz@iaea.org
m.lammer@iaea.org
v.pronyaev@iaea.orgschwerer
zerkin