I do not know about the speed and I'm not an expert either. The beauty of the reports is that we can borrow them from others, save them and change them as needed, right? It is the same as the former query 'ExtractValue(marcxml' changing to ExtractValue(metadata'. All of the reports in the reports library <https://wiki.koha-community.org/wiki/SQL_Reports_Library> should be and look to be updated for the new versions to help new and current users. I remember trying a number of reports in the library that did not work for me. Best, M. _________________________________________ *Michael J. Sutherland* University Libraries Virginia Tech sudrland@vt.edu | 540.231.9669 <+15402319669> On Wed, May 27, 2020 at 7:43 PM Mark Alexander <marka@pobox.com> wrote:
Excerpts from Michael Sutherland's message of 2020-05-27 16:59:50 -0400:
CASE SUBSTR(metadata,282,2)
I tried this myself, and it does seem to work. But I worry that the 282 value might not be correct in the future, should the XML format of the metadata change even slightly. In particular, the XML header has a field called xsi:schemaLocation that contains a URL that might change someday. I could very wrong about this, though; perhaps the format really is stable.
This does the same job and seems less obscure (to me, anyway):
substring(ExtractValue(metadata, '//leader'), 7, 2)
But perhaps it's not as fast? I'm not a MySQL expert by any means. _______________________________________________
Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha