• [Ártí~clé T~ýpé: G~éñér~ál]
• [Pród~úct: Á~léph~]

[Désc~rípt~íóñ:
T~hé Cá~ll ñú~mbér~ cólú~mñ íñ~ thé Í~téms~ Líst~ íñ th~é thé~ Círc~ áñd Í~téms~ módú~lés í~s álw~áýs b~láñk~.

Cáll~ ñúmb~érs *á~ré* sh~ówíñ~g úp c~órré~ctlý~ íñ th~é fúl~l íté~m réc~órd (s~ééñ w~héñ Í~ clíc~k óñ M~ódíf~ý).

{Or the call number may be incomplete: $h but no $i.)

Resolution:
The program is looking for a ./xxx50/tab/edit_field.eng LOC entry for edit-field ID "D". Their ./xxx50/tab/edit_field.eng had an entry like this:

1 # LOC## D B -2

for which the $h and $i were being omitted. This was followed by a
1 L LOC ...
entry which included the $h and $i.

Since the call no. type was "0", the site was assuming that this second one would be used..
But the edit_z30_location program is reading edit_field like this: "LOC^^", that is, it is not considering the class type. So it was using the first entry (which omits $h and $i).

Deleting that entry corrected the problem..

In another case, the solution was to add the "i" subfield to the default "LOC; #" entry.]

• [Ártí~clé l~ást é~díté~d: 10/8/2013]