<div dir="ltr"><div><div>I'm all for seeing biblioitems disappear.  The only bib of data that I reference (in migration or support work) is the biblioitems.itype and biblioitems.marcxml.  A lot of the other fields appear to be dupes of items (volumenumber, volumedate, etc.) or more correctly belong in biblio (isbn, publication year, etc).    <br>
<br></div>I like Galen's idea of the biblio_metadata table and dropping (or moving as appropriate) columns from biblioitems as seems appropriate.<br><br></div>Joy Nelson<br><font color="#888888"><div>Director of Migrations<br>
<br></div><div><a href="http://bywatersolutions.com" target="_blank"><span style="font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)">ByWater Solutions</span></a><span style="border-collapse:separate;color:rgb(0,0,0);font-family:Helvetica;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;font-size:medium"><span style="border-collapse:separate;color:rgb(0,0,0);font-family:Helvetica;font-style:normal;font-variant:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;font-size:medium"><span style="border-collapse:separate;font-family:Helvetica;font-style:normal;font-variant:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;font-size:medium"><span style="border-collapse:separate;font-style:normal;font-variant:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;font-size:medium;font-family:Helvetica"><span style="border-collapse:separate;font-family:Helvetica;font-style:normal;font-variant:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;font-size:medium"><span style="border-collapse:separate;font-family:Helvetica;font-style:normal;font-variant:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;font-size:medium"><span style="border-collapse:separate;font-family:Helvetica;font-style:normal;font-variant:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;font-size:medium"><span style="border-collapse:separate;font-family:Helvetica;font-style:normal;font-variant:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;font-size:medium"><span style="border-collapse:separate;font-style:normal;font-variant:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;font-size:medium"><span style="border-collapse:separate;font-style:normal;font-variant:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;font-size:medium"><span style="border-collapse:separate;font-style:normal;font-variant:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;font-size:medium"><span style="border-collapse:separate;font-style:normal;font-variant:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;font-size:medium"><span style="border-collapse:separate;font-style:normal;font-variant:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;font-size:medium"><span style="border-collapse:separate;font-style:normal;font-variant:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;font-size:medium"><span style="border-collapse:separate;font-style:normal;font-variant:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;font-size:medium"><span style="border-collapse:separate;font-size:medium;font-style:normal;font-variant:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="border-collapse:separate;font-size:medium;font-style:normal;font-variant:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><font color="#1e39f6" face="Calibri" size="3"><span style="font-size:12pt;font-family:Calibri"></span></font></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span><br>
<span style="font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)">
Support and Consulting for Open Source Software<br>Office: Fort Worth, TX<br>Phone/Fax <a value="+18889008944" style="color:rgb(0,0,204)">(888)900-8944</a></span><br><span style="font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)"><a href="http://bywatersolutions.com/what-is-koha/" target="_blank">What is Koha? </a><br>
</span></div></font><div><div><div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, May 3, 2013 at 9:38 AM, Galen Charlton <span dir="ltr"><<a href="mailto:gmc@esilibrary.com" target="_blank">gmc@esilibrary.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,<br>
<br>
On Fri, May 3, 2013 at 6:20 AM, Mathieu Saby<br>
<<a href="mailto:mathieu.saby@univ-rennes2.fr">mathieu.saby@univ-rennes2.fr</a>> wrote:<br>
> Thank you.<br>
> So, just to know, do you think it would be<br>
> 1. - a total waste of time ?<br>
> 2. - a strange idea ?<br>
> 3. - a good idea (for performance and code maintenance) ?<br>
> 4. - harmful ?<br>
><br>
> to merge the biblio and biblioitem tables ?<br>
<br>
My gut feeling is #3, but a lot of testing would be needed to avoid<br>
#4.  Possibly one way to reduce risk and improve testability would be<br>
to move columns over to biblio one at a time.<br>
<br>
Here are a couple additional thoughts if we undertake this:<br>
<br>
[1] We should decide whether we want to keep both bibilioitems.marc<br>
and biblioitems.marcxml.  I think we can get rid of the former.<br>
<br>
[2] Even if we merge the tables, I think we should still keep the<br>
marcxml column in its own table, e.g., one called biblio_metadata:<br>
<br>
CREATE TABLE biblio_metadata (<br>
   biblio_metadata_id INTEGER NOT NULL AUTO_INCREMENT; -- for the future!<br>
   biblionumber INTEGER,<br>
   metadata_type VARCHAR(10), -- for the future!<br>
   blob LONGTEXT NOT NULL,<br>
   -- and relevant FK contraints<br>
);<br>
<br>
The bits about slipping in multi-metadata-schema support aside, for<br>
many queries there's no reason to pull in largish XML columns.<br>
<br>
[3] We should see if we can drop some columns.  As a rule of thumb, I<br>
suggest that if a biblio/bilbioitems column isn't referred to in the<br>
code. any of the default MARC frameworks, or the SQL reports library,<br>
it's probably not being used.<br>
</blockquote><div> <br><span style="font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)"><br></span></div></div>
</div></div></div></div></div>