Even if the 942 field is not mandatory, I think it's still a good practice to use it. The 942's itemtype allows you, when filtering by itemtype, to retrieve records that don't have items attached to it. Electronic resources for example.

Also, if you don't use the 942 field, be sure to set up the "item-level_itypes" system preference properly. In this case :  item-level_itypes = specific item.

Hope it helps.

François

François Charbonnier,
Bibl. prof. / Chef de produits

Tél.  : (888) 604-2627
francois.charbonnier@inLibro.com

Le 2016-11-30 à 05:56, Tomas Cohen Arazi a écrit :
You only need 952$y. 942 is a fallback because all items need an phenotype, but in the past it was not enforced, specially on import.

El mié., 30 de nov. de 2016 2:11 AM, Karen Myers <karenmyers1@hotmail.com> escribió:

Hi all


I am wanting to clarify the usage of the 942$c field versus the 952$y field as I am setting up a new bib framework.

I am wondering if it is necessary to have both the 942$c field and the 952$y field in the framework as they seem to record the same information i.e Koha item type. Is there an advantage to recording the same information in both fields and if not which is the preferred? We are using Koha 3.22
    thanks!
Karen

_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
--
Tomás Cohen Arazi
Theke Solutions (https://theke.io)
✆ +54 9351 3513384
GPG: B2F3C15F


_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/