Fixed field 008 Time Tech do not display in fixed field grid

[Lindsay Stratton]

We have noticed that when importing videorecording MARC records the 008 field codes for Time and Technique (Tech) are being stripped from display in the Fixed Fields grid, although they continue to appear in the actual 008 field.

Pioneer is running version 2.2.

An example problem 008 field for a videorecording: "150126p20152014cau123 vleng d" - the "123" is the Time, and "l" (within the "vleng" chunk) is the technique.

Posted this issue to evergeen-catalogers list, this response from Mike Rylander:

It turns out that Time and Technique (Tech) are not configured with position information in the database, so the MARC editor does not know how to pull that data from the record. I think an LP bug to improve the coverage of the data in config.marc21_ff_pos_map would be a good thing -- it looks like there are others that are not represented either. Here's the list of existing fixed fields and their record type mapping:

 Alph | SER
 Audn | BKS, COM, REC, SCO, SER, VIS
 BLvl | BKS, COM, MAP, MIX, REC, SCO, SER, VIS
 Biog | BKS
 Conf | BKS, SER
 Cont | BKS, SER
 Ctrl | BKS, COM, MAP, MIX, REC, SCO, SER, VIS
 Ctry | BKS, COM, MAP, MIX, REC, SCO, SER, VIS
 Date1 | BKS, COM, MAP, MIX, REC, SCO, SER, VIS
 Date2 | BKS, COM, MAP, MIX, REC, SCO, SER, VIS
 Desc | BKS, COM, MAP, MIX, REC, SCO, SER, VIS
 DtSt | BKS, COM, MAP, MIX, REC, SCO, SER, VIS
 ELvl | AUT, BKS, COM, MAP, MIX, REC, SCO, SER, VIS
 Fest | BKS
 Form | BKS, MAP, MIX, REC, SCO, SER, VIS
 GPub | BKS, COM, MAP, SER, VIS
 Ills | BKS
 Indx | BKS, MAP
 Lang | BKS, COM, MAP, MIX, REC, SCO, SER, VIS
 LitF | BKS
 MRec | BKS, COM, MAP, MIX, REC, SCO, SER, VIS
 RecStat | AUT
 S/L | SER
 Subj | AUT
 TMat | VIS
 Type | BKS, COM, MAP, MIX, REC, SCO, SER, VIS

[Jane Sandberg (sandbergja)]

In the Web client in 2.12, I'm seeing the Time and Tech fixed fields (see attached). Is it fair to say that this issue is fixed?

[Elaine Hardy (ehardy)]

Also seeing fixed field elements in 3.2 (web client). Issue appears to be fixed.