[Koha] Report schema questions re: mapping biblio.copyrightdate

[Jason Vasche]

Thank you Henry, I'll try that workaround!

Regards,
Jason

----------------------------------------------------------------------

Message: 1
Date: Wed, 6 May 2020 07:45:09 +0000
From: "BOLSHAW, Henry" <bolshawh at parliament.uk>
To: "koha at lists.katipo.co.nz" <koha at lists.katipo.co.nz>
Subject: Re: [Koha] Report schema questions re: mapping
        biblio.copyrightdate
Message-ID:
        <LO2P123MB20479EAF88F91E9242CAC721DBA40 at LO2P123MB2047.GBRP123.PROD.OUTLOOK.COM>

Content-Type: text/plain; charset=UTF-8

Hi Jason

We use RDA and have had this issue as well. As a workaround, we have added the 264 field as an additional mapping for biblio.copyrightdate using the ‘Koha to MARC’ mapping tool in the administration module. This seems to work for us although there may be unintended consequences that I’m not yet aware of.

Here’s the 19.05 manual entry for Koha to MARC mapping: https://gcc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fkoha-community.org%2Fmanual%2F19.05%2Fen%2Fhtml%2Fadministration.html%23koha-to-marc-mapping&data=02%7C01%7Cjvasche%40roundrocktexas.gov%7C76ab224805404c3f891c08d7f219c1d2%7Ca33c69e40e384e23b6380d6dd8fd2445%7C1%7C0%7C637244064767786817&sdata=71GyKLGcQAEdcGvL52U63akAEuXwX1YZDgVnuYY9xP8%3D&reserved=0

The manual says “It is possible to link more than one MARC field to a database field. For example, you could link both 260$a and 264$a to the biblioitems.place field.”

I hope that helps!

Kind regards
Henry

Henry Bolshaw
Systems Librarian
Library, House of Lords, London, SW1A 0PW