<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hi Marcel and Christopher,</p>
<p>maybe to explain this a bit more, Koha will already display all
the information from 260 and 264 in the detail view and result
lists, because in those views the full MARC record is used as the
source for the displayed information.</p>
<p>There are other, brief views, that pull information from the
columns in the biblio and biblioitems tables only. The mappings
define, how these columns are filled with information. For example
the default mapping for copyrightdate is 260 at the moment. An
example for a 'brief' view would be the list of records in the
cart, or the information shown in the acquisitions module.<br>
</p>
<p>Christopher got me thinking: For 260 and 264 are repeatable, as a
side effect of cataloguing rule changes, they might even appear
both in a record (even if they shouldn't). Which year will be
given priority? For display purposes in the brief views, only one
year should be displayed.</p>
<p>I agree with the idea of making the mapping on the default
framework the standard to use for all MARC records. If we support
other formats at some point, we could add a default BIBFRAME or
default Dublin Core mapping maybe?<br>
</p>
<p>Katrin<br>
</p>
<p><br>
</p>
<br>
<div class="moz-cite-prefix">On 09.08.2017 16:05, Christopher Davis
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CACFiFkb0S2bJdP4Q724YfQjKmQj=4z1AdhrvAZNwCM-nmpVG_g@mail.gmail.com">
<div dir="ltr">
<div class="gmail_default"
style="font-family:verdana,sans-serif">Marcel,</div>
<div class="gmail_default"
style="font-family:verdana,sans-serif"><br>
</div>
<div class="gmail_default"
style="font-family:verdana,sans-serif">Thank you for
clarifying my understanding. It sounds like Koha will
simultaneously pull and display copyright date information
from more than one MARC subfield and that's great. What would
happen if a MARC record only has, for example, a 264$c and no
260$c? Will Koha throw an error if it encounters scenarios
like this? I hope that those questions do not sound stupid.</div>
<div class="gmail_default"
style="font-family:verdana,sans-serif"><br>
</div>
<div class="gmail_default"
style="font-family:verdana,sans-serif">As far as non-MARC data
is concerned, if Koha can pull copyright date from two MARC
subfields, then it stands to reason that it could pull the
date from two MARC subfields and a Dublin Core field/element,
yes?</div>
<div class="gmail_default"
style="font-family:verdana,sans-serif"><br>
</div>
<div class="gmail_default"
style="font-family:verdana,sans-serif">Regards,</div>
</div>
<div class="gmail_extra"><br clear="all">
<div>
<div class="gmail_signature" data-smartmail="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div dir="ltr">
<div><font face="verdana, sans-serif"> <br>
Christopher Davis</font></div>
<div><font face="verdana, sans-serif">Systems
& E-Services Librarian<br>
</font></div>
<div><font face="verdana, sans-serif">Uintah
County Library</font></div>
<div><font face="verdana, sans-serif"><a
href="mailto:cgdavis@uintah.utah.gov"
style="font-size:12.8px" target="_blank"
moz-do-not-send="true">cgdavis@uintah.utah.gov</a><br>
</font></div>
<div><font face="verdana, sans-serif"><a
href="tel:14357890091" target="_blank"
moz-do-not-send="true">(435) 789-0091</a>
ext.261<br>
<a href="http://uintahlibrary.org"
target="_blank" moz-do-not-send="true">uintahlibrary.org</a><br>
<a href="http://basinlibraries.org"
target="_blank" moz-do-not-send="true">basinlibraries.org</a><br>
<a
href="http://facebook.com/uintahcountylibrary"
target="_blank" moz-do-not-send="true">facebook.com/uintahcountylibrary</a><br>
<a
href="http://instagram.com/uintahcountylibrary"
target="_blank" moz-do-not-send="true">instagram.com/uintahcountylibrary</a></font></div>
<div><img
src="https://drive.google.com/a/uintah.utah.gov/uc?id=0B3CXDpFsfriXUHpVNjFKZ25QckU&export=download"
moz-do-not-send="true"><br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<div class="gmail_quote">On Wed, Aug 9, 2017 at 5:34 AM, Marcel
de Rooy <span dir="ltr"><<a
href="mailto:M.de.Rooy@rijksmuseum.nl" target="_blank"
moz-do-not-send="true">M.de.Rooy@rijksmuseum.nl</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div id="m_-3619264837064238647divtagdefaultwrapper"
style="color:rgb(0,0,0);font-family:Calibri,Helvetica,sans-serif,'EmojiFont','Apple
Color Emoji','Segoe UI Emoji',NotoColorEmoji,'Segoe UI
Symbol','Android Emoji',EmojiSymbols;font-size:12pt"
dir="ltr"><span class="">
<p>> Thank you for seeking input from the Koha
Community before making this decision.
</p>
</span>
<p>Thanks for responding :)</p>
<span class="">
<p><br>
</p>
<p>> If I understand your message correctly, you
are saying that if the "Default" MARC framework has
kohafield mappings which are configured to pull
copyright date from MARC 260$c *and* MARC 264$c, and
if Koha sometimes only "asks" for the kohafield
mapping codes from the "Default" MARC framework,
then why rewrite the code to pull kohafield mappings
from MARC frameworks other than "Default" if the
mappings of the other frameworks are identical to
"Default's" mappings (i.e., MARC 260$c *and* MARC
264$c). Is this correct?</p>
<p><br>
</p>
</span>
<p>Not sure if you fully got my point. I propose to
always check kohafield mappings from Default, and at
the same time keep kohafield in all frameworks in
sync. This requires some code changes of course. New
would be that a kohafield may have two mappings. This
approach would make Koha more consistent, since it
currently is somewhat ambiguous in this regard (also
partly as a result of having no frameworkcode in
indexed records).</p>
<div style="color:rgb(0,0,0)">
<div>
<div dir="ltr"><span class="">
<div class="gmail_default"
style="font-family:verdana,sans-serif"><br>
</div>
<div class="gmail_default"
style="font-family:verdana,sans-serif">> In
answer to your question, I think that prudence
demands that we rewrite the code. For example,
if the records with MARC framework "A" were
cataloged according to AACR2 standards
(copyright recorded in MARC 260$c) and the
records using framework "B" were according to
RDA (copyright in 264$c), then a code rewrite
would be necessary. My library has both AACR2
MARC records and RDA MARC records, so, for the
time being, as long as Koha can displays the
copyright information from both MARC 260$c
*and* 264$c, I'm happy. When the day comes,
however, when Koha will finally index non-MARC
metadata records such as Dublin Core and
BIBFRAME, It would be wise to have the code
always "ask" for what bibliographic framework
a record uses.</div>
<div class="gmail_default"
style="font-family:verdana,sans-serif"><br>
</div>
</span>
<div class="gmail_default"
style="font-family:verdana,sans-serif">We agree
on the need for code changes. They are inspired
by the fact that we want to show copyrightdate
from both 260 and 264. Since this is all about
Koha to MARC and vice versa, indexing other data
is out of scope. But surely, it needs proper
attention in the future.</div>
<span class="HOEnZb"><font color="#888888">
<div class="gmail_default"
style="font-family:verdana,sans-serif"><br>
</div>
</font></span></div>
<span class="HOEnZb"><font color="#888888">
Marcel<br>
</font></span></div>
</div>
</div>
</div>
<br>
______________________________<wbr>_________________<br>
Koha-devel mailing list<br>
<a href="mailto:Koha-devel@lists.koha-community.org"
moz-do-not-send="true">Koha-devel@lists.koha-<wbr>community.org</a><br>
<a
href="http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel"
rel="noreferrer" target="_blank" moz-do-not-send="true">http://lists.koha-community.<wbr>org/cgi-bin/mailman/listinfo/<wbr>koha-devel</a><br>
website : <a href="http://www.koha-community.org/"
rel="noreferrer" target="_blank" moz-do-not-send="true">http://www.koha-community.org/</a><br>
git : <a href="http://git.koha-community.org/"
rel="noreferrer" target="_blank" moz-do-not-send="true">http://git.koha-community.org/</a><br>
bugs : <a href="http://bugs.koha-community.org/"
rel="noreferrer" target="_blank" moz-do-not-send="true">http://bugs.koha-community.<wbr>org/</a><br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Koha-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Koha-devel@lists.koha-community.org">Koha-devel@lists.koha-community.org</a>
<a class="moz-txt-link-freetext" href="http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel">http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel</a>
website : <a class="moz-txt-link-freetext" href="http://www.koha-community.org/">http://www.koha-community.org/</a>
git : <a class="moz-txt-link-freetext" href="http://git.koha-community.org/">http://git.koha-community.org/</a>
bugs : <a class="moz-txt-link-freetext" href="http://bugs.koha-community.org/">http://bugs.koha-community.org/</a></pre>
</blockquote>
<br>
</body>
</html>