[Calendula-devel] data migration

[Thomas Panzarella]

With all of the Calendula movement (list, etc.) could you (Darryl) quickly =
send out an email that says where the lists are, where the CVS is located, =
and any other pertinent info for contributors?

Also, at this point, I think we should turn discussions to finializing requ=
irements, building a clear project plan document, and building out technica=
l specifications -- I'd suggest we try to stick with some "standards" when =
trying to communicate technical aspects of the project (i.e. UML Diagrams, =
Use Cases, etc.).  I feel sort of lost as to how to intelligently contribut=
e here.  We are talking data migration but what is the context?  We looked =
at a code snippet that connects to a database but, (again) what is the cont=
ext?

Who on this list is heading to Philly for NTEN?  I propose a meetup of peop=
le interested in the Calendula project to sit and discuss some details.  I =
will volunteer myself to draft up "minutes", so to speak, from that meeting=
 to communicate back to the group at large.  Eventhough this is the "less f=
un part" of open source, we need to work out the politics of how the "calen=
dula community" is going to work.  Set up a "board" ... who is "code captai=
n", who is "zealot", who will maintain a bug database, who will maintain th=
e list servs / cvs / etc., who is a "comitter" to cvs, who will set up - ma=
intain - and make look pretty/professional the calendula project web site, =
etc.  There are many issues that need to get worked out ... I am going to a=
ssume that Darryl does not want to take on all of those roles.

t.


> -----Original Message-----
> From: Darryl Caldwell [mailto:darrylc@fudosys.com]
> Sent: Friday, March 12, 2004 12:09 PM
> To: calendula-devel@fudosys.com
> Subject: RE: [Calendula-devel] data migration
>=20
>=20
> Bill, Bill, Bill, where were you when I needed your expertise=20
> last year? ;-)
>=20
> Thanks for that great code snippet. I can see putting that to use REAL
> SOON. The problem to be solved is to start planning for=20
> migration of data
> in FM and Access databases over to Calendula. Thomas and others have
> suggested that many small nonprofits use FM and Access to store their
> donor data. Some type of migration tools should be present=20
> early on and I
> want to make sure the path is mapped out.
>=20
> -D
>=20
>=20
> >
> > Hello, all:
> >
> > I haven't been following this thread, and I haven't posted=20
> to this list
> > before, which
> > explains why I'm copying to some individuals: I'm not sure=20
> I have the
> > right address
> > for the list.
> >
> > I've worked with both FM and Access. Both support ODBC, and=20
> Python offers
> > convenient access to ODBC. IIRC, FM's ODBC is wobbly, and=20
> as a consequence
> > I
> > have retrieved data from FM tables as HTML files, then parsed them.
> > Access's
> > ODBC has never given me trouble, and I've used it heavily,=20
> on and off, for
> > some
> > years.
> >
> =3D=3D Code sample snipped =3D=3D
> >
> > Would someone mind restating the problem to be solved?
> >
>=20
>=20
> --=20
> Darryl Caldwell
> darrylc@fudosys.com
> www.fudosys.com
> _______________________________________________
> Calendula-devel mailing list
> Calendula-devel@fudosys.com
> http://list.fudosys.com/mailman/listinfo/calendula-devel
>=20