Solved my question below -- created Auth value:XXXX first and now it appears as an option when I try to add the 952 $k to the framework (default and Books). But when I try to link the 952 $k to the Koha field the pick list does not include "biblioitems.cn_prefix Yet, when I check the the subfield structure admin for the 942 $k its constraints has the text "Koha field: biblioitems.cn_prefix.... even though biblioitems.cn_prefix does not appear in the picklist for a Koha link. How can you link the Koha field if it's not included on the pick list? Puzzled. Christine Mueller Database Administrator Office of Information Technology New Mexico State Library 1209 Camino Carlos Rey Santa Fe, NM 87507 Phone: 505-476-9744 christine.mueller@state.nm.us http://www.stlib.state.nm.us/ On Mon, Apr 6, 2009 at 2:30 PM, Chris Mueller <catsalsa@gmail.com> wrote:
In Koha 3-stable frameworks the 942 tag includes subfield "k", call no. prefix. The 952 tag does not have subfield "k".
I can add 952 $k to the frameworks -- Tab:10, | Koha field: biblioitems.cn_prefix, Not repeatable, Not mandatory, | Auth value:XXXX.
My question: Which needs to be created first? The "k" subfield for the 952 tag, or the "XXXX" authorized value.
Christine Mueller Database Administrator Office of Information Technology New Mexico State Library 1209 Camino Carlos Rey Santa Fe, NM 87507 Phone: 505-476-9744 christine.mueller@state.nm.us http://www.stlib.state.nm.us/