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

[BOLSHAW, Henry]

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://koha-community.org/manual/19.05/en/html/administration.html#koha-to-marc-mapping

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

From: Koha <koha-bounces at lists.katipo.co.nz> On Behalf Of koha-request at lists.katipo.co.nz
Sent: 06 May 2020 01:00
To: koha at lists.katipo.co.nz
Subject: Koha Digest, Vol 175, Issue 4

Send Koha mailing list submissions to
koha at lists.katipo.co.nz<mailto:koha at lists.katipo.co.nz>

To subscribe or unsubscribe via the World Wide Web, visit
https://lists.katipo.co.nz/mailman/listinfo/koha<https://lists.katipo.co.nz/mailman/listinfo/koha>
or, via email, send a message with subject or body 'help' to
koha-request at lists.katipo.co.nz<mailto:koha-request at lists.katipo.co.nz>

You can reach the person managing the list at
koha-owner at lists.katipo.co.nz<mailto:koha-owner at lists.katipo.co.nz>

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Koha digest..."


Today's Topics:

1. Report schema questions re: mapping biblio.copyrightdate
(Jason Vasche)
2. koha-US May 2020 Meetings & Events (Jason Robb)


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

Message: 1
Date: Tue, 5 May 2020 15:55:38 +0000
From: Jason Vasche <jvasche at roundrocktexas.gov<mailto:jvasche at roundrocktexas.gov>>
To: "koha at lists.katipo.co.nz<mailto:koha at lists.katipo.co.nz>" <koha at lists.katipo.co.nz<mailto:koha at lists.katipo.co.nz>>
Subject: [Koha] Report schema questions re: mapping
biblio.copyrightdate
Message-ID:
<SN6PR09MB320099B6F3D991A314E8A895C6A70 at SN6PR09MB3200.namprd09.prod.outlook.com<mailto:SN6PR09MB320099B6F3D991A314E8A895C6A70 at SN6PR09MB3200.namprd09.prod.outlook.com>>

Content-Type: text/plain; charset="iso-8859-1"

Greetings Koha community,

I recently ran a report that included biblio.copyrightdate as a display, but many of the records - including those with correct 008 and 264 _1 fields in the bib record - showed up in my report with no copyright date displayed. Upon further digging, I found that the date would only display in the report for bib records with a 260 field, but not a 264.

In the 19.05 SQL schema comments, biblio.copyrightdate is "publication or copyright date from the MARC record." Can anyone confirm that this means MARC 260 exclusively? Would it be possible to expand the schema mapping to include the 264 field(s) for the sake of RDA cataloging? Hope y'all are well, thanks for your time and attention!

Regards,

Jason

**
Jason Vasché
Cataloging Librarian
Round Rock Public Library
Round Rock, TX
512-218-7007


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

Message: 2
Date: Tue, 5 May 2020 11:16:18 -0500
From: Jason Robb <secretary at koha-us.org<mailto:secretary at koha-us.org>>
To: koha-US list <koha-us at koha-us.org<mailto:koha-us at koha-us.org>>, BW partners list
<partners at bywatersolutions.com<mailto:partners at bywatersolutions.com>>, Koha list <koha at lists.katipo.co.nz<mailto:koha at lists.katipo.co.nz>>
Subject: [Koha] koha-US May 2020 Meetings & Events
Message-ID:
<CAPEQLGpuybrY6NKoA_CAe8rwA5OxTnZJH8=JvTiqNVd5sePqjg at mail.gmail.com<mailto:CAPEQLGpuybrY6NKoA_CAe8rwA5OxTnZJH8=JvTiqNVd5sePqjg at mail.gmail.com>>
Content-Type: text/plain; charset="UTF-8"

koha-US online meetings and events are free and open to all.

See our calendar for a full list: http://koha-us.org/calendar/<http://koha-us.org/calendar>

*Meetings*
Board Meeting - Wednesday, May 6th @ 8:30-9:30 PT (9:30 MT / 10:30 CT /
11:30 ET)

- Meeting Link - https://zoom.us/j/293750042<https://zoom.us/j/293750042>
- Agenda -
https://docs.google.com/document/d/1GIZvunUKROy3-JvgHC10UGPF8S8Y8jaaTWKca7xQvLg/edit?usp=sharing<https://docs.google.com/document/d/1GIZvunUKROy3-JvgHC10UGPF8S8Y8jaaTWKca7xQvLg/edit?usp=sharing>

General Meeting - Wednesday, May 13th @ 8:30-9:30 PT (9:30 MT / 10:30 CT /
11:30 ET)

*Learning Opportunities*
Koha Documentation with Jessie Zairo - Friday, May 15th @ 8:30-9:30 PT
(9:30 MT / 10:30 CT / 11:30 ET)
jQuery Hacks with George Williams - Thursday, May 21st @ 8:30-9:30 PT (9:30
MT / 10:30 CT / 11:30 ET)

*Special Interest Groups*
Cataloging - Thursday, May 7th @ 8-9 PT (9 MT / 10 CT / 11 ET)
System Administration - Tuesday, May 12th @ 9-10 PT (10 MT / 11 CT / Noon
ET)
Web Development - Thursday, May 14th @ 8-9 PT (9 MT / 10 CT / 11 ET)
Acquisitions - Tuesday, May 19th @ 9-10 PT (10 MT / 11 CT / Noon ET)

Visit http://koha-us.org/special-interest-groups/<http://koha-us.org/special-interest-groups> to learn more about SIGs,
sign up for SIG mailing lists, and view recordings from past meetings.

Jason Robb
koha-US Secretary
secretary at koha-us.org<mailto:secretary at koha-us.org>


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

Subject: Digest Footer

_______________________________________________
Koha mailing list
Koha at lists.katipo.co.nz<mailto:Koha at lists.katipo.co.nz>
https://lists.katipo.co.nz/mailman/listinfo/koha<https://lists.katipo.co.nz/mailman/listinfo/koha>


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

End of Koha Digest, Vol 175, Issue 4
************************************
UK Parliament Disclaimer: this e-mail is confidential to the intended recipient. If you have received it in error, please notify the sender and delete it from your system. Any unauthorised use, disclosure, or copying is not permitted. This e-mail has been checked for viruses, but no liability is accepted for any damage caused by any virus transmitted by this e-mail. This e-mail address is not secure, is not encrypted and should not be used for sensitive data.