[OPEN-ILS-GENERAL] Migrating patron data

[Demian Katz]

I see the changes now -- perhaps it was just my browser cache fooling me!

Thanks also for the documentation update instructions.  Once I have something to share, I'll see which strategy makes the most sense.  Unfortunately, I won't be at the Evergreen conference this time around... but maybe next year!

- Demian

> -----Original Message-----
> From: open-ils-general-bounces at list.georgialibraries.org [mailto:open-
> ils-general-bounces at list.georgialibraries.org] On Behalf Of Soulliere,
> Robert
> Sent: Tuesday, April 12, 2011 9:33 AM
> To: Evergreen Discussion Group
> Subject: Re: [OPEN-ILS-GENERAL] Migrating patron data
> 
> Hi Damian,
> 
> Some changes should be appearing in both docs for 1.6 and 2.0:
> 
> http://docs.evergreen-ils.org/1.6/draft/html/migratingpatrons.html
> http://docs.evergreen-ils.org/2.0/draft/html/migratingpatrons.html
> 
> You might need to do a page refresh to update the changes if you
> haven't already.
> 
> Please let me know if you still see "program_number" and "program_code"
> in the steps for creating the table. I thought I got those but perhaps
> my old eyes are playing tricks on me. I made some other changes also
> but am doing some more clean up to the documentation today to fix up
> some wording and add a few missing steps.
> 
> Another place to track changes is in the github repository:
> https://github.com/rsoulliere/Evergreen-DocBook/commits/master
> 
> If you could share your notes and documentation regarding migration
> that would be excellent. There are several way to share documentation
> depending on your comfort level with the DIG (Git-DocBook) tool chain.
> 
> 1) The easiest way is to submit the documentation to this DIG list.
> Preferred format is DocBook, but we can accept documentation in other
> formats.
> 
> 2) If you would like to be more involved and you are comfortable with
> git, you could sumbit documentation to the repo directly.
> a. Install git,
> b. set up an account in github,
> c. request to be a collaborator for the DIG documentation repository,
> d. clone the documentation files
> e. and submit DocBook documentation directly into the repo.
> 
> There are also several other ways to contribute in between these two
> options. We will cover these at the Evergreen conference if you are
> attending.
> 
> Regards,
> Robert
> 
> 
> 
> 
> 
> Robert Soulliere, BA (Hons), MLIS
> Systems Librarian
> Mohawk College Library
> robert.soulliere at mohawkcollege.ca
> Telephone: 905 575 1212 x3936
> Fax: 905 575 2011
> ________________________________________
> From: open-ils-general-bounces at list.georgialibraries.org [open-ils-
> general-bounces at list.georgialibraries.org] On Behalf Of Demian Katz
> [demian.katz at villanova.edu]
> Sent: April 12, 2011 8:55 AM
> To: Evergreen Discussion Group; open-ils-
> documentation at list.georgialibraries.org
> Subject: Re: [OPEN-ILS-GENERAL] Migrating patron data
> 
> Thanks for the fast response -- I look forward to seeing these
> improvements to the documentation!  Where should I be looking for them?
> Your email implies that at least some edits have been made already, but
> the page I linked does not appear to have changed yet -- am I looking
> in the wrong place, or do I just need to be more patient?
> 
> Also, if I eventually have my own contributions to make to the
> documentation, what is the best way to share it?  I suspect that my
> migration will do a few things that the current example does not (i.e.
> migrate active and non-active patrons, possibly load multiple
> addresses); I'll be happy to share notes once the work is done.
> 
> thanks,
> Demian
> 
> > -----Original Message-----
> > From: open-ils-general-bounces at list.georgialibraries.org
> [mailto:open-
> > ils-general-bounces at list.georgialibraries.org] On Behalf Of
> Soulliere,
> > Robert
> > Sent: Monday, April 11, 2011 3:21 PM
> > To: Evergreen Discussion Group; open-ils-
> > documentation at list.georgialibraries.org
> > Subject: Re: [OPEN-ILS-GENERAL] Migrating patron data
> >
> > Thanks Damian,
> >
> > program_number and program_code information references have been
> > removed from the documentation. This was org specific and used by our
> > college for statistical purposes (e.g. populating the stat category
> > tables, etc. ) but would not be useful for a general migration.
> >
> > You  are exactly right about point #2. We need more explanation about
> > some of the more ambiguous fields in the evergreen database. I will
> add
> > a few notes on some of these fields in the migration steps.
> Hopefully,
> > in the long run we will have alternative migration methods added to
> the
> > documentation as well.
> >
> > Thanks,
> > Robert
> >
> >
> >
> >
> >
> > Robert Soulliere, BA (Hons), MLIS
> > Systems Librarian
> > Mohawk College Library
> > robert.soulliere at mohawkcollege.ca
> > Telephone: 905 575 1212 x3936
> > Fax: 905 575 2011
> > ________________________________________
> > From: open-ils-general-bounces at list.georgialibraries.org [open-ils-
> > general-bounces at list.georgialibraries.org] On Behalf Of Demian Katz
> > [demian.katz at villanova.edu]
> > Sent: April 11, 2011 1:54 PM
> > To: Evergreen Discussion Group
> > Subject: [OPEN-ILS-GENERAL] Migrating patron data
> >
> > Hello,
> >
> > I've started looking at the patron migration instructions in the 2.0
> > documentation:
> >
> > http://docs.evergreen-ils.org/2.0/draft/html/migratingpatrons.html
> >
> > I have a couple of questions:
> >
> > - There are some fields in the staging table which do not appear to
> be
> > used elsewhere: program_number and program_name.  Do these serve any
> > purpose, or should they be removed from the documentation?
> > - Is there any detailed documentation on the meanings of some of
> these
> > fields?  I see the links to the database schemas, but higher-level
> > information on things like profile, ident_type and home_ou would be
> > helpful to determine the correct mappings.  Any guidance would be
> > appreciated!
> >
> > thanks,
> > Demian
> >
> > This E-mail contains privileged and confidential information intended
> > only for the individual or entity named in the message.  If the
> reader
> > of this message is not the intended recipient, or the agent
> responsible
> > to deliver it to the intended recipient, you are hereby notified that
> > any review, dissemination, distribution or copying of this
> > communication
> > is prohibited.  If this communication was received in error, please
> > notify the sender by reply E-mail immediately, and delete and destroy
> > the original message.
> 
> This E-mail contains privileged and confidential information intended
> only for the individual or entity named in the message.  If the reader
> of this message is not the intended recipient, or the agent responsible
> to deliver it to the intended recipient, you are hereby notified that
> any review, dissemination, distribution or copying of this
> communication
> is prohibited.  If this communication was received in error, please
> notify the sender by reply E-mail immediately, and delete and destroy
> the original message.