[Babase] More vocabularly: PPA, Posgres, Babase, etc.
Karl O. Pinc
kop at meme.com
Wed May 2 16:34:59 EDT 2007
On 05/02/2007 12:19:29 PM, kfenn wrote:
There's been a lot of talk in the style of what's below, and the
vocabularly just isn't right. (Tabby need not feel put-upon.)
The basic problem is that PPA is being used for the entirity of
the new system. It's like calling all the software on your
computer "Word".
I've tended to use "papio" for the entirity of the new system.
I don't think this is necessarly best. I'd like to use "Babase 2.0".
So, the pieces would be:
Babase 1.0/foxpro -- The old system: it's programs and data,
including foxpro.
Babase 2.0 -- The new system: it's programs and data, including
all the 3rd party software that makes it work.
the database/Babase/the Babase data -- The data itself.
Babase/the Babase programs -- The programs, database rules,
documentation, and all other stuff we wrote.
papio -- The computer hardware (and maybe everything on it.)
Postgres/PostgreSQL/pg -- The database software (sometimes also
"the database" when it's clear in context we're talking software.)
PPA/phpPgAdmin -- The generic front end that allows access to a
Postgres database from the web.
After that there's some minor pieces:
the browser/firefox -- the web browser
SQL -- the language. Entered and run in PPA/the browser.
The ranker -- Tyler's ranker program.
The VPN/OpenVPN -- The VPN software
the wiki/the Babase wiki -- the wiki content.
moinmoin -- the wiki software
the web site/the Babase web site -- All the Babase stuff you can get to
over the web.
The web server/Apache -- The program that serves up web pages,
including the PPA pages, the wiki pages, the upcen and psionconvert
programs, and the static documentation pages.
Maybe this vocabularly can go on the wiki?
---------------------------------------------
To re-word:
> Once the above changes/fixes occur, we have one more speedbump with
> FoxPro before we can move exclusively to PPA.
Babase 2.0
> The new files of "old"
> census data that Jen Foreman has entered is in dbf form. Karl says
> trying to do an upload of this into PPA
Postgres (via PPA and the upcen program, unless I write
some magic program)
> is not going to be
> easy....the upload is best done in FoxPro. I agree, but I can forsee
> that this update may generate a substantial number of new errors when
> we run through another conversion given that such a large bulk of
> data is replacing old data.
> If we end up with a lot of new errors, Jeanne and Susan may need to
> make a call on how to proceed with the 06B update (that is, whether
> to use FoxPro or PPA
Babase 2.0
> , and how important this additional census data
> is versus getting the 06B update done before my maternity leave
> starts). Obviously, I can do the 06B update in FoxPro at any time.
> Right now we are having problems doing uploads to the views in PPA,
Postgres
> and this is necessary for both the Duke and Princeton parts of the
> demog update. Karl is going to work on solving the problem this
> week and we are all in charge of checking in with him about
> progress... however the new census-related errors need to be fixed in
> FoxPro before we can think about doing the demog update in PPA.
(either "using PPA and the Babase programs" or "in Babase 2.0")
Karl <kop at meme.com>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
More information about the Babase
mailing list