<div dir="ltr">Bob --<br><br>It looks like state doesn't get a separate field, it is just a part of city. So, in my test database, for example:<br><br><span style="font-family: courier new,monospace;">mysql> select DISTINCT city from borrowers WHERE city IS NOT NULL LIMIT 3,5;</span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;">+----------------------+</span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;">| city |</span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;">+----------------------+</span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;">| Portland, OR | </span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;">| Santa Cruz, CA | </span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;">| Mayfield Heights, OH | </span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;">| Athens, OH | </span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;">| Atwater, OH | </span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;">+----------------------+</span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;">5 rows in set (0.01 sec)</span><br><br>Other more reliable sorting and batching can still be achieved with zip codes, if you wanted to do something like targeted mailing. <br>
--joe <br><br><div class="gmail_quote">On Tue, Jul 22, 2008 at 1:02 PM, Bob Ewart <span dir="ltr"><<a href="mailto:bob-ewart@earthlink.net">bob-ewart@earthlink.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Joe and Nicole,<br>
<br>
Thanks for your quick responses.<br>
<br>
They will make this part of the conversion easy.<br>
<br>
Joe, where do you record the state?<br>
<br>
The fun part of the conversion is going to be the catalog.<br>
<div><div></div><div class="Wj3C7c"><br>
<br>
<br>
Joe Atzberger wrote:<br>
> Bob -<br>
><br>
> The borrowers table contains all the fields you're looking for, I think,<br>
> with perhaps the exception of country. That shouldn't be a major<br>
> limitation, if you record the Canadian's state as something<br>
> recognizeable like "Ontario".<br>
><br>
> Here are the table fields.<br>
><br>
> mysql> describe borrowers;<br>
> +---------------------+--------------+------+-----+---------+----------------+<br>
> | Field | Type | Null | Key | Default |<br>
> Extra |<br>
> +---------------------+--------------+------+-----+---------+----------------+<br>
> | borrowernumber | int(11) | NO | PRI | NULL |<br>
> auto_increment |<br>
> | cardnumber | varchar(16) | YES | UNI | NULL<br>
> | |<br>
> | surname | mediumtext | NO | |<br>
> | |<br>
> | firstname | text | YES | | NULL<br>
> | |<br>
> | title | mediumtext | YES | | NULL<br>
> | |<br>
> | othernames | mediumtext | YES | | NULL<br>
> | |<br>
> | initials | text | YES | | NULL<br>
> | |<br>
> | streetnumber | varchar(10) | YES | | NULL<br>
> | |<br>
> | streettype | varchar(50) | YES | | NULL<br>
> | |<br>
> | address | mediumtext | NO | |<br>
> | |<br>
> | address2 | text | YES | | NULL<br>
> | |<br>
> | city | mediumtext | NO | |<br>
> | |<br>
> | zipcode | varchar(25) | YES | | NULL<br>
> | |<br>
> | email | mediumtext | YES | | NULL<br>
> | |<br>
> | phone | text | YES | | NULL<br>
> | |<br>
> | mobile | varchar(50) | YES | | NULL<br>
> | |<br>
> | fax | mediumtext | YES | | NULL<br>
> | |<br>
> | emailpro | text | YES | | NULL<br>
> | |<br>
> | phonepro | text | YES | | NULL<br>
> | |<br>
> | B_streetnumber | varchar(10) | YES | | NULL<br>
> | |<br>
> | B_streettype | varchar(50) | YES | | NULL<br>
> | |<br>
> | B_address | varchar(100) | YES | | NULL<br>
> | |<br>
> | B_city | mediumtext | YES | | NULL<br>
> | |<br>
> | B_zipcode | varchar(25) | YES | | NULL<br>
> | |<br>
> | B_email | text | YES | | NULL<br>
> | |<br>
> | B_phone | mediumtext | YES | | NULL<br>
> | |<br>
> | dateofbirth | date | YES | | NULL<br>
> | |<br>
> | branchcode | varchar(10) | NO | MUL |<br>
> | |<br>
> | categorycode | varchar(10) | NO | MUL |<br>
> | |<br>
> | dateenrolled | date | YES | | NULL<br>
> | |<br>
> | dateexpiry | date | YES | | NULL<br>
> | |<br>
> | gonenoaddress | tinyint(1) | YES | | NULL<br>
> | |<br>
> | lost | tinyint(1) | YES | | NULL<br>
> | |<br>
> | debarred | tinyint(1) | YES | | NULL<br>
> | |<br>
> | contactname | mediumtext | YES | | NULL<br>
> | |<br>
> | contactfirstname | text | YES | | NULL<br>
> | |<br>
> | contacttitle | text | YES | | NULL<br>
> | |<br>
> | guarantorid | int(11) | YES | | NULL<br>
> | |<br>
> | borrowernotes | mediumtext | YES | | NULL<br>
> | |<br>
> | relationship | varchar(100) | YES | | NULL<br>
> | |<br>
> | ethnicity | varchar(50) | YES | | NULL<br>
> | |<br>
> | ethnotes | varchar(255) | YES | | NULL<br>
> | |<br>
> | sex | varchar(1) | YES | | NULL<br>
> | |<br>
> | password | varchar(30) | YES | | NULL<br>
> | |<br>
> | flags | int(11) | YES | | NULL<br>
> | |<br>
> | userid | varchar(30) | YES | MUL | NULL<br>
> | |<br>
> | opacnote | mediumtext | YES | | NULL<br>
> | |<br>
> | contactnote | varchar(255) | YES | | NULL<br>
> | |<br>
> | sort1 | varchar(80) | YES | | NULL<br>
> | |<br>
> | sort2 | varchar(80) | YES | | NULL<br>
> | |<br>
> | altcontactfirstname | varchar(255) | YES | | NULL<br>
> | |<br>
> | altcontactsurname | varchar(255) | YES | | NULL<br>
> | |<br>
> | altcontactaddress1 | varchar(255) | YES | | NULL<br>
> | |<br>
> | altcontactaddress2 | varchar(255) | YES | | NULL<br>
> | |<br>
> | altcontactaddress3 | varchar(255) | YES | | NULL<br>
> | |<br>
> | altcontactzipcode | varchar(50) | YES | | NULL<br>
> | |<br>
> | altcontactphone | varchar(50) | YES | | NULL<br>
> | |<br>
> | smsalertnumber | varchar(50) | YES | | NULL<br>
> | |<br>
> +---------------------+--------------+------+-----+---------+----------------+<br>
> 58 rows in set (0.00 sec)<br>
><br>
> The fields with NULL=NO are requried. Any additional fields that you<br>
> cannot easily map yet, I suggest you incorporate into the "contactnote"<br>
> or "opacnote" fields, using some consistent mechanical format (e.g.,<br>
> "message_flag=y, other_flag=3"). Then later you can still extract that<br>
> info for use in an extended attribute, custom report, etc.<br>
><br>
> All Koha's date fields are represented internally as ISO format dates<br>
> (YYYY-MM-DD).<br>
><br>
> --Joe Atzberger<br>
> Systems Administrator, LibLime<br>
><br>
> On Tue, Jul 22, 2008 at 11:34 AM, Nicole Engard<br>
</div></div><div class="Ih2E3d">> <<a href="mailto:nicole.engard@liblime.com">nicole.engard@liblime.com</a> <mailto:<a href="mailto:nicole.engard@liblime.com">nicole.engard@liblime.com</a>>> wrote:<br>
><br>
> I want to point you to the working manual:<br>
> <a href="http://sites.google.com/a/liblime.com/koha-manual/" target="_blank">http://sites.google.com/a/liblime.com/koha-manual/</a><br>
><br>
> I don't know how to answer all of your questions, but as for the<br>
> street type - this is because there is an authorized value you can<br>
> assign to that to make it easier for people to add patrons.<br>
><br>
> As for missing fields, you can set up your own custom fields by<br>
> going to the patron attribute types:<br>
> <a href="http://sites.google.com/a/liblime.com/koha-manual/Home/Table-of-Contents/administration/Patrons---Circulation/patrons--circulation-patron-attribute-types" target="_blank">http://sites.google.com/a/liblime.com/koha-manual/Home/Table-of-Contents/administration/Patrons---Circulation/patrons--circulation-patron-attribute-types</a><br>
><br>
><br>
> ---<br>
><br>
> Nicole C. Engard<br>
> Open Source Evangelist, LibLime<br>
> (888) Koha ILS (564-2457) ext. 714<br>
</div>> <a href="mailto:nce@liblime.com">nce@liblime.com</a> <mailto:<a href="mailto:nce@liblime.com">nce@liblime.com</a>><br>
<div class="Ih2E3d">> AIM/Y!/Skype: nengard<br>
><br>
> <a href="http://liblime.com" target="_blank">http://liblime.com</a><br>
> <a href="http://blogs.liblime.com/open-sesame/" target="_blank">http://blogs.liblime.com/open-sesame/</a><br>
><br>
> On Tue, Jul 22, 2008 at 11:29 AM, Bob Ewart <<a href="mailto:bob-ewart@earthlink.net">bob-ewart@earthlink.net</a><br>
</div><div><div></div><div class="Wj3C7c">> <mailto:<a href="mailto:bob-ewart@earthlink.net">bob-ewart@earthlink.net</a>>> wrote:<br>
><br>
> I'm in the process of converting our library from DBText to koha<br>
> 3.00<br>
> RC1 and have a couple of questions about the fields in the<br>
> patron record.<br>
><br>
> I see address, city and zipcode for the addresses, but no state or<br>
> country fields. Being in south Florida, we do get a number of<br>
> Canadians.<br>
><br>
> I'm also curious about why street number and street type are<br>
> separate<br>
> fields.<br>
><br>
> We also have a number of flags like 'mailing list' (which indicates<br>
> whether or not the patron wants to get general mailings) which<br>
> don't map<br>
> to anything in the patron record.<br>
><br>
> What format should the dates have? I don't have a sex or<br>
> date-of-birth<br>
> field (I'll probably use 1/1/1969 for date of birth which will make<br>
> everyone 39 years old. They're all adults.)<br>
><br>
> I see that the branch and category codes must be valid for importing<br>
> patrons. Are there any other fields that are required or<br>
> checked. I<br>
> guess that cardnumber, zipcode and surname are required.<br>
><br>
> Thanks for any suggestions.<br>
> --<br>
> Bob<br>
><br>
<br>
<br>
</div></div>--<br>
<div><div></div><div class="Wj3C7c">Bob<br>
<br>
_______________________________________________<br>
Koha mailing list<br>
<a href="mailto:Koha@lists.katipo.co.nz">Koha@lists.katipo.co.nz</a><br>
<a href="http://lists.katipo.co.nz/mailman/listinfo/koha" target="_blank">http://lists.katipo.co.nz/mailman/listinfo/koha</a><br>
</div></div></blockquote></div><br></div>