Marc, Checking the MARC to Koha Mappings in the administration area will tell you what database table, if any, you've mapped 946$a into (depends on your MARC flavour, and any local changes you may have made). If you haven't mapped that subfield to a database table, the information is still in Koha, but buried in the MARC blobs. I would think it would be easiest to extract it from biblioitems.marcxml, but I happen to like XML. You'd need to use some fancy MySQL string manipulation to just show the value of 946$a, and searching on it would be even more complex, but it should work. Probably a combination of LOCATE, LIKE and SUBSTRING would be necessary to cleanly extract the data. Hope this helps, Ian Walls Systems Integration Librarian NYU Health Sciences Libraries 550 First Ave., New York, NY 10016 ________________________________________ From: koha-bounces@lists.katipo.co.nz [koha-bounces@lists.katipo.co.nz] On Behalf Of Marc Nürnberger [marc.nuernberger@gmx.de] Sent: Friday, October 30, 2009 11:17 AM To: Koha List Subject: [Koha] Reports: how to query MARC subfield 946a Dear all, We are working on koha 3.0.3 and would like to create a report within koha that includes the MARC Subfield 946a, in order to get a table with something like author, title, ... and the content of field 946a. How could we query this value? In which table.field can it be found? Appreciating any hints. Best, Marc _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha ------------------------------------------------------------ This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain information that is proprietary, confidential, and exempt from disclosure under applicable law. Any unauthorized review, use, disclosure, or distribution is prohibited. If you have received this email in error please notify the sender by return email and delete the original message. Please note, the recipient should check this email and any attachments for the presence of viruses. The organization accepts no liability for any damage caused by any virus transmitted by this email. =================================