lewellyn
Database Manager
Bibliomation, Inc.
Middlebury, CT
mllew...@biblio.org
From: open-ils-general-boun...@list.georgialibraries.org
[mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of
Chris Spradling
Sent: Sunday, March 10, 2013 5:37 AM
To: Evergreen Discussi
Hi,
On Fri, Mar 8, 2013 at 5:52 AM, Donald Butterworth
wrote:
> Based on insights from the listserv and some serious cogitation, we have
> created hierarchies, parameters, and values that we hope will take advantage
> of Evergreen’s architecture. All along my expectation has been that we would
>
> 2. Use staging tables.
I'll second this. The documentation
(http://docs.evergreen-ils.org/2.1/html/migrating_records_using_migration_tools.html)
doesn't reflect this, but those migration tools can help you create
staging tables.
Let's say you have a migration schema foo. Then you can create a
Hi Don,
I have two pieces of advice:
1. Migrate early and often.
Prior to our migration I did several full data loads on our production
hardware. After each I would empty the database and do it again. Each
time I learned something new or found a better way to migrate the data.
I also got a
Good morning Donald,
On Fri Mar 8 07:52:19 2013, Donald Butterworth wrote:
Colleagues,
We are approaching the point of migrating records from our Symphony
system into Evergreen, and we are unsure what the best method is to
accomplish this.
We have migrated several different ILS systems to
Colleagues,
We are approaching the point of migrating records from our Symphony system
into Evergreen, and we are unsure what the best method is to accomplish
this.
Based on insights from the listserv and some serious cogitation, we have
created hierarchies, parameters, and values that we hope
