chasers-general Mailing List for CHASERS

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

 http://mobileprofitsfasttrack.com/wp-content/plugins/akismet/ugoogle.html

Jessi and Ken,

Your responses were enlightening and helpful.  We've managed to create
the tables and income view.  Thanks very much!

Mike

Jessi's comments were right on the mark (thanks Jessi!), but in looking 
at this I discovered some additional problems. There was a stray 
"abort" in one of the files, and several of the other files needed to 
make this work weren't called. It also looks like the file to create 
the "l_other_assistance" table never made it into the public release.

It's all a bit of a dependence tangle, but I checked an updated version 
into GIT that seems to work for me. The code for creating the income 
table is in there now, but commented out by default.

Mike--if you update your code ("git pull"), and then run the following 
commands (copied from the install.client.sql file), then this will 
hopefully work for you. 

/* Income Table & Necessary Housing stuff */
\i housing/create.l_unit_type.sql
\i housing/create.tbl_housing_unit.sql
\i housing/create.l_income_certification_type.sql
\i housing/create.l_fund_type.sql

\i create.l_income.sql
\i create.l_other_assistance.sql
\i create.tbl_income.sql
\i create.view.income.sql
\i functions/create.functions_income.sql

(you probably want to run this in a transaction, in case there are 
further errors.)

I checked a placeholder function for l_other_assistance into Git. If 
DESC can provide a dump of the codes they're using, that would be 
great. Otherwise, you'll have to make up your own. Thanks.

Ken

Jessi Berkelhammer wrote:
> Hi Mike,
> It looks like the create.tbl_income.sql file first creates tbl_income,

> then some indexes, and lastly the trigger verify_income_record, which 
> relies on the function income_verify(). Like you noted, this trigger 
> cannot be created before the function is created, but the function 
> cannot be created before the table.
>
> If you break up create.tbl_income.sql, you can first create
tbl_income, 
> then create the function, and lastly the trigger. Storing the trigger
in 
> the same file as the table's create statement seems like an error here

> (and probably in other places too.)
>
> Does that make sense?
>
> take care,
> jessi

Jessi's comments were right on the mark (thanks Jessi!), but in looking 
at this I discovered some additional problems.  There was a stray 
"abort" in one of the files, and several of the other files needed to 
make this work weren't called.  It also looks like the file to create 
the "l_other_assistance" table never made it into the public release.

It's all a bit of a dependence tangle, but I checked an updated version 
into GIT that seems to work for me.  The code for creating the income 
table is in there now, but commented out by default.

Mike--if you update your code ("git pull"), and then run the following 
commands (copied from the install.client.sql file), then this will 
hopefully work for you. 

/* Income Table & Necessary Housing stuff */
\i housing/create.l_unit_type.sql
\i housing/create.tbl_housing_unit.sql
\i housing/create.l_income_certification_type.sql
\i housing/create.l_fund_type.sql

\i create.l_income.sql
\i create.l_other_assistance.sql
\i create.tbl_income.sql
\i create.view.income.sql
\i functions/create.functions_income.sql

(you probably want to run this in a transaction, in case there are 
further errors.)

I checked a placeholder function for l_other_assistance into Git.  If 
DESC can provide a dump of the codes they're using, that would be 
great.  Otherwise, you'll have to make up your own. Thanks.

Ken

Jessi Berkelhammer wrote:
> Hi Mike,
> It looks like the create.tbl_income.sql file first creates tbl_income, 
> then some indexes, and lastly the trigger verify_income_record, which 
> relies on the function income_verify(). Like you noted, this trigger 
> cannot be created before the function is created, but the function 
> cannot be created before the table.
>
> If you break up create.tbl_income.sql, you can first create tbl_income, 
> then create the function, and lastly the trigger. Storing the trigger in 
> the same file as the table's create statement seems like an error here 
> (and probably in other places too.)
>
> Does that make sense?
>
> take care,
> jessi
>
>
> Michael James wrote:
>   
>> We’re trying to create tbl_income.  When we run create.tbl_income.sql we 
>> get this error:
>>
>>  
>>
>> ERROR:  function income_verify() does not exist
>>
>> ********** Error **********
>>
>> ERROR: function income_verify() does not exist
>> SQL state: 42883
>>
>>  
>>
>> Then we run create.functions_income.sql and get this error:
>>
>>  
>>
>> ABORT;
>>
>> ERROR:  relation "tbl_income" does not exist
>>
>> ********** Error **********
>>
>> ERROR: relation "tbl_income" does not exist
>> SQL state: 42P01
>>
>>  
>>
>> This looks circular to me.  Any ideas?
>>
>>  
>>
>> Thanks,
>>
>>  
>>
>> Mike James
>>
>> Plymouth Housing Group
>>
>> mj...@pl... <mailto:mj...@pl...>
>>
>>  
>>
>>
>> ------------------------------------------------------------------------
>>
>> ------------------------------------------------------------------------------
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Chasers-general mailing list
>> Cha...@li...
>> https://lists.sourceforge.net/lists/listinfo/chasers-general
>>     
>
>   

Hi Mike,
It looks like the create.tbl_income.sql file first creates tbl_income, 
then some indexes, and lastly the trigger verify_income_record, which 
relies on the function income_verify(). Like you noted, this trigger 
cannot be created before the function is created, but the function 
cannot be created before the table.

If you break up create.tbl_income.sql, you can first create tbl_income, 
then create the function, and lastly the trigger. Storing the trigger in 
the same file as the table's create statement seems like an error here 
(and probably in other places too.)

Does that make sense?

take care,
jessi

Michael James wrote:
> We’re trying to create tbl_income.  When we run create.tbl_income.sql we 
> get this error:
> 
>  
> 
> ERROR:  function income_verify() does not exist
> 
> ********** Error **********
> 
> ERROR: function income_verify() does not exist
> SQL state: 42883
> 
>  
> 
> Then we run create.functions_income.sql and get this error:
> 
>  
> 
> ABORT;
> 
> ERROR:  relation "tbl_income" does not exist
> 
> ********** Error **********
> 
> ERROR: relation "tbl_income" does not exist
> SQL state: 42P01
> 
>  
> 
> This looks circular to me.  Any ideas?
> 
>  
> 
> Thanks,
> 
>  
> 
> Mike James
> 
> Plymouth Housing Group
> 
> mj...@pl... <mailto:mj...@pl...>
> 
>  
> 
> 
> ------------------------------------------------------------------------
> 
> ------------------------------------------------------------------------------
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Chasers-general mailing list
> Cha...@li...
> https://lists.sourceforge.net/lists/listinfo/chasers-general

-- 
Jessi Berkelhammer
Downtown Emergency Service Center
Computer Programming Specialist

Hey mike. I see what you mean about this looking circular! I'll be back near
a computer within an hour or so, and will take a closer look.

Ken

On Jul 2, 2009 2:48 PM, "Michael James" <mj...@pl...> wrote:

 We’re trying to create tbl_income.  When we run create.tbl_income.sql we
get this error:

ERROR:  function income_verify() does not exist

********** Error **********

ERROR: function income_verify() does not exist
SQL state: 42883

Then we run create.functions_income.sql and get this error:

ABORT;

ERROR:  relation "tbl_income" does not exist

********** Error **********

ERROR: relation "tbl_income" does not exist
SQL state: 42P01

This looks circular to me.  Any ideas?

Thanks,

Mike James

Plymouth Housing Group

mj...@pl...

------------------------------------------------------------------------------

_______________________________________________
Chasers-general mailing list
Cha...@li...
https://lists.sourceforge.net/lists/listinfo/chasers-general

We're trying to create tbl_income.  When we run create.tbl_income.sql we
get this error:

ERROR:  function income_verify() does not exist

********** Error **********

ERROR: function income_verify() does not exist
SQL state: 42883

Then we run create.functions_income.sql and get this error:

ABORT;

ERROR:  relation "tbl_income" does not exist

********** Error **********

ERROR: relation "tbl_income" does not exist
SQL state: 42P01

This looks circular to me.  Any ideas?

Thanks,

Mike James

Plymouth Housing Group

mj...@pl... <mailto:mj...@pl...> 

Hi Joseph.  My apologies for not responding to you earlier.  Apparently 
(and embarrassingly!) my email address wasn't current for the 
chasers-general list, so I didn't see your message until now.

As for your question, the main thing I needed to change was the path to 
the files. In chasers_config.php, I changed $CG_HOME_BY_FILE to be the 
path to the chasers install:

$CG_HOME_BY_FILE = 'C:/Program Files/Apache Software 
Foundation/Apache2.2/htdocs/chasers';

(I believe this is correct, but verify with your installation.  Also, 
it's a different path if you use the Apache & PHP bundled with Postgres).

Since I didn't get SSL enabled, I had to change this line to 'http", 
instead of 'https':

$chasers_home_url='http://'.$_SERVER['SERVER_NAME'].dirname($_SERVER['PHP_SELF']).'/'.$off;

If you have SSL working, you can leave it unchanged. I'll fix it at some 
point, as it really shouldn't be hard-coded either way.

If you make those changes, when you go to the index page, you should get 
a link to create the engine array.  Click on it, and it should work.

Let me know how it goes, and I'll try to respond a little faster! :)

Cheers,
Ken

> Ken,
>
> Thanks for trying this on a windows machine. I understand that this is a
> primary linux running program due to dependencies, could you let me know
> what files you modded in regards to changing the locations to the 
> files and
> the https code?
>
> I have it installed without table_log but when you goto the index page to
> setup the engine that is as far as I can get, I wish I was at home 
> where my
> debian box is but it wont be for a few weeks til I get there so 
> windows has
> to make do.
>
> I am just looking to get it running to see what has to be changed to
> accommodate a shelter that I am opening next year, I am just anxious 
> to play
> with it.
>
> Thanks,
> Joseph Carr

Ken,

Thanks for trying this on a windows machine. I understand that this is a
primary linux running program due to dependencies, could you let me know
what files you modded in regards to changing the locations to the files and
the https code?

I have it installed without table_log but when you goto the index page to
setup the engine  that is as far as I can get, I wish I was at home where my
debian box is but it wont be for a few weeks til I get there so windows has
to make do.

I am just looking to get it running to see what has to be changed to
accommodate a shelter that I am opening next year, I am just anxious to play
with it.

Thanks,
Joseph Carr

On Mon, Jun 1, 2009 at 4:47 PM, Kenneth Tanzer <ken...@gm...> wrote:

> Hey folks.  I thought some of you might be interested to know that I was
> able to successfully get CHASERS running on Windows.  This may be useful
> for any potential users who are really committed to staying with the
> Windows platform.
>
> I haven't fully tested it, and expect there might be some minor things
> that would need tweaking, likely related to paths and file handling.
> But it's apparently a much smaller deal than I might have imagined.
>
> As a tech note, although it took me a while to get Apache, PHP &
> Postgres running, CHASERS itself was pretty easy, and only required
> changing the path to the files, plus fixing one line of code (there's an
> 'https' hard-coded that needs to be fixed).  I didn't get SSL (for
> Apache) or table_log (for Postgres) working, so I don't have https or
> revision history working, but I don't think these are CHASERS issues.
> It's not that the can't run, just that I didn't bother setting up SSL,
> and don't have access to a Windows development environment to compile
> table_log.
>
> At some point I'll update the documentation with this new information.
>
> Let me know if you have any questions.  Thanks.
>
> Ken
>
>
> ------------------------------------------------------------------------------
> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
> looking to deploy the next generation of Solaris that includes the latest
> innovations from Sun and the OpenSource community. Download a copy and
> enjoy capabilities such as Networking, Storage and Virtualization.
> Go to: http://p.sf.net/sfu/opensolaris-get
> _______________________________________________
> Chasers-general mailing list
> Cha...@li...
> https://lists.sourceforge.net/lists/listinfo/chasers-general
>

-- 
Joseph S. Carr

Thanks for keeping us in the loop!

MJ Kiser
Program Director
Compass Center
(206) 357-3124
mj...@co...

-----Original Message-----
From: Kenneth Tanzer [mailto:ken...@gm...] 
Sent: Monday, June 01, 2009 2:48 PM
To: cha...@li...
Cc: cha...@li...
Subject: [Chasers-general] CHASERS running on Windows!

Hey folks.  I thought some of you might be interested to know that I was

able to successfully get CHASERS running on Windows.  This may be useful

for any potential users who are really committed to staying with the 
Windows platform. 

I haven't fully tested it, and expect there might be some minor things 
that would need tweaking, likely related to paths and file handling.  
But it's apparently a much smaller deal than I might have imagined.

As a tech note, although it took me a while to get Apache, PHP & 
Postgres running, CHASERS itself was pretty easy, and only required 
changing the path to the files, plus fixing one line of code (there's an

'https' hard-coded that needs to be fixed).  I didn't get SSL (for 
Apache) or table_log (for Postgres) working, so I don't have https or 
revision history working, but I don't think these are CHASERS issues.  
It's not that the can't run, just that I didn't bother setting up SSL, 
and don't have access to a Windows development environment to compile 
table_log.

At some point I'll update the documentation with this new information.

Let me know if you have any questions.  Thanks.

Ken

------------------------------------------------------------------------
------
OpenSolaris 2009.06 is a cutting edge operating system for enterprises 
looking to deploy the next generation of Solaris that includes the
latest 
innovations from Sun and the OpenSource community. Download a copy and 
enjoy capabilities such as Networking, Storage and Virtualization. 
Go to: http://p.sf.net/sfu/opensolaris-get
_______________________________________________
Chasers-general mailing list
Cha...@li...
https://lists.sourceforge.net/lists/listinfo/chasers-general

Hey folks.  I thought some of you might be interested to know that I was 
able to successfully get CHASERS running on Windows.  This may be useful 
for any potential users who are really committed to staying with the 
Windows platform. 

I haven't fully tested it, and expect there might be some minor things 
that would need tweaking, likely related to paths and file handling.  
But it's apparently a much smaller deal than I might have imagined.

As a tech note, although it took me a while to get Apache, PHP & 
Postgres running, CHASERS itself was pretty easy, and only required 
changing the path to the files, plus fixing one line of code (there's an 
'https' hard-coded that needs to be fixed).  I didn't get SSL (for 
Apache) or table_log (for Postgres) working, so I don't have https or 
revision history working, but I don't think these are CHASERS issues.  
It's not that the can't run, just that I didn't bother setting up SSL, 
and don't have access to a Windows development environment to compile 
table_log.

At some point I'll update the documentation with this new information.

Let me know if you have any questions.  Thanks.

Ken

I am trying to set this up on a development maching.
I tested the install of the web\database server setup with 2 different CMS's
and it does work.
WinXP sp2
apache 2.2
php5
activestate tcl 8.4.19.1
postgresql 8.3.7.1
phppgadmin 4.2

Following the instructions in Install.txt and install.db.sql, I manually
setup the database name (chaser), user (postgres) and password then i ran:

psql -U postgres chasers
entered password when it prompted
\i install.db.sql

the sql script ran for a few then it error'd out, with the following:

C:\Documents and Settings\Administrator>cd
C:\Webserver\htdocs\chasers\database\
pg\client

C:\Webserver\htdocs\chasers\database\pg\client>psql -U postgres chaser
Password for user postgres:
Welcome to psql 8.3.7, the PostgreSQL interactive terminal.

Type:  \copyright for distribution terms
       \h for help with SQL commands
       \? for help with psql commands
       \g or terminate with semicolon to execute query
       \q to quit

Warning: Console code page (437) differs from Windows code page (1252)
         8-bit characters might not work correctly. See psql reference
         page "Notes for Windows users" for details.

chaser=# \i install.db.sql
  oid
-------
 16386
(1 row)

  oid
-------
 16384
 16396
(2 rows)

psql:install.db.sql:45: ERROR:  function "plpgsql_call_handler" already
exists w
ith same argument types
psql:install.db.sql:46: ERROR:  language "plpgsql" already exists
  oid
-------
 16399
(1 row)

  oid
-------
 16398
 16397
(2 rows)

psql:install.db.sql:60: ERROR:  function "pltclu_call_handler" already
exists wi
th same argument types
psql:install.db.sql:61: ERROR:  language "pltclu" already exists
psql:install.db.sql:67: ERROR:  function "pgmail" already exists with same
argum
ent types
  oid
-------
 16403
(1 row)

  oid
-------
 16402
 16401
(2 rows)

psql:install.db.sql:72: ERROR:  function "pltcl_call_handler" already exists
wit
h same argument types
psql:install.db.sql:73: ERROR:  language "pltcl" already exists
SET
psql:install.db.sql:84: ERROR:  function "levenshtein" already exists with
same
argument types
psql:install.db.sql:89: ERROR:  function "metaphone" already exists with
same ar
gument types
psql:install.db.sql:93: ERROR:  function "soundex" already exists with same
argu
ment types
psql:install.db.sql:97: ERROR:  function "text_soundex" already exists with
same
 argument types
psql:install.db.sql:111: ERROR:  could not access file "$libdir/table_log":
No s
uch file or directory
psql:install.db.sql:114: ERROR:  could not access file "$libdir/table_log":
No s
uch file or directory
psql:install.db.sql:117: ERROR:  could not access file "$libdir/table_log":
No s
uch file or directory
psql:install.db.sql:120: ERROR:  could not access file "$libdir/table_log":
No s
uch file or directory
psql:install.db.sql:123: ERROR:  could not access file "$libdir/table_log":
No s
uch file or directory
chaser=#

_______________________________________________________________
It seems that only the last 5 errors are important, with the others being
warnings
about data that already exists.

(note: i had to install activestate tcl, due to the pltcl language not being
installed)

Now this is my 5th attempt installing this, with the other attempts i did
the same
steps except used "chasers" as the DB name. On each attempt I would drop the

database and create a new one.

I would normally install this on a debian lamps at home, my database
experience is with MySQL.
So the only extra box that i have running where I am at is a WinXP SP2 unit
that
I installed this on, at my current location I only have access to the
internet via
a data card (verizon) and i can not get to debian. But this should work
regardless of the
operating system. shouldn't it?

I have a feeling that this is a user (me) error since this is my first time
using postgresql.

I am wanting to just get it up and running and play with it and see what i
need to change
to suit my needs with a shelter that I am going to open up in central europe
and louisiana, in
which DESC line of work and mine (human trafficking) are very much the same.
Thanks for any help you can give.
-- 
Joseph S. Carr

Hello folks.  To help facilitate what I hope and believe will be 
newly-increased efforts to improve and disseminate CHASERS, I've created 
two new mailing lists.  One is for technical development efforts 
(chasers-devel), and the other for documentation discussion and issues 
(cleverly named chasers-documentation).

Creating these lists will provide for more specialized discussion among 
subscribers, while allowing those with only a more general interest in 
CHASERS to be spared the gory details.

Subscription to these new lists is of course open to anyone with an 
interest, and also entirely optional.  I would certainly hope, though, 
that at the very least Jonathan, Sarah, Jessi and Nathan will all end up 
as subscribers to chasers-devel.

It will be no surprise to anyone that there is plenty of room for 
CHASERS improvement--it's a target-rich environment!  The general areas 
seem to be:

        increased ease of installation and configuration
        improved documentation
        elimination of legacy code
        enhanced documentation
        increased and more flexible functionality

I've been thinking about this recently, and am working on a list of 
near-term items that I think would be relatively manageable.  I'll try 
to post it shortly (to chasers-devel), and would love to hear other 
people's comments and ideas.

I'll mention one item now, though.  It would be nice to get some of the 
improvements that have been made more recently at DESC incorporated into 
the next release.  Ones that come quickly to mind are the calendar 
repeating events (and child-child-tables) and file attachments.  There 
are likely others that I'm either forgetting or unaware of.  If someone 
at DESC could pull those patches at some point, it would be very 
helpful.  We'll also need to figure out how to keep DESC and public 
versions of CHASERS in sync, but that's a discussion we can have on the 
devel mailing list!

That's about it for now.  After a nice long break, I'm planning to 
devote some significant time and energy towards CHASERS efforts, and am 
excited to be doing so.  I hope some of you still retain CHASERS 
enthusiasm, and want to continue on the never-ending quest for 
improvement!  Hope y'all are doing well!

Ken

I am happy to say that Downtown Emergency Service Center (DESC) 
officially released CHASERS as Free and Open Source Software yesterday.  
I've included the announcement text in this email, and it's also 
available online.  Many thanks to everyone who's helped with and 
participated in this project!

Ken

http://www.desc.org/chasers_release.html
http://prnewswire.com/cgi-bin/stories.pl?ACCT=104&STORY=/www/story/09-30-2008/0004895149&EDATE=#

September 30, 2008

*FOR MORE INFORMATION ABOUT CHASERS,
SEE http://chasers.desc.org/ <http://chasers.desc.org>

DOWNTOWN EMERGENCY SERVICE CENTER RELEASES CHASERS, FREE SOFTWARE FOR 
HOMELESS SERVICE MANAGEMENT AND BEYOND*

Downtown Emergency Service Center (DESC) is pleased to release its 
CHASERS application as open-source software. DESC uses CHASERS to store 
and manage information about clients, services and agency operations.

Created by DESC, CHASERS is both proven and a work-in-progress, and has 
been under in-house development for approximately five years. During 
this time, CHASERS has been in continuous use, and now contains 
information on over 70,000 clients served by DESC. Key features include 
web-based access, client and staff management, reporting, permission and 
access control, electronic logs, collaborative caseloads and real-time 
notifications.

"CHASERS has become an integral tool in DESC's ongoing work to serve the 
sickest and most vulnerable homeless people in our community," said 
Executive Director Bill Hobson. "We are pleased to release this software 
to the community, and hope it will become useful for other oranizations 
as well."

As used at DESC, CHASERS is built entirely on Free and Open Source 
Software. In this configuration, there are no software or licensing fees 
involved, allowing CHASERS to be used to its maximum potential. One such 
advantage is that every staff member has an account, without additional 
cost.

"DESC has benefitted greatly from the use of Free and Open Source 
Software, and from assistance from free software communities," noted Ken 
Tanzer, DESC's Director of Information Services. "I'm very happy that 
DESC is in turn contributing to the pool of free software. At the same 
time, other organizations have expressed interest in CHASERS. With this 
release, these organizations can begin determining whether CHASERS can 
provide value to their operations."

CHASERS was designed for flexibility and adaptability, and modified 
versions are used for fundraising and volunteer management, and to 
manage data for a research project conducted in cooperation with the 
University of Washington's Addictive Behaviors Research Center and 
funded by the Robert Wood Johnson Foundation. A demonstration version is 
available online.

*ABOUT DOWNTOWN EMERGENCY SERVICE CENTER*

DESC is the most comprehensive provider of services and housing for 
chronically homeless adults in Seattle and King County, and has received 
numerous national and local awards. DESC's services include shelter, 
housing, mental healthcare, addiction treatment, and employment 
services. Last year, DESC served over 6,700 individuals and moved 605 
men and women off the streets into permanent supportive housing. DESC 
currently provides 650 units of housing, with another 130 units in 
development. Increasingly, housing development is at the center of 
DESCâEUR^(TM)s mission "to end the homelessness of vulnerable adults."

*INTENDED AUDIENCE AND FUTURE GOALS*

At this stage, CHASERS will be of interest primarily to organizations 
with at least some level of technical expertise. DESC is interested in 
collaborating with other entities in the service delivery, funding and 
technical support communities to continue to expand the functionality of 
CHASERS, create documentation and increase the ease of installation, 
configuration and maintenance.

*DISCLAIMER*

CHASERS is provided entirely as-is, and DESC makes no representation 
regarding the usability or fitness of the software for any particular 
purpose. Entities that choose to use CHASERS do so entirely at their own 
risk, and DESC will under no circumstances be liable for any damages or 
consequences, direct or indirect, in connection with such use.

*FURTHER INFORMATION*

For further information about CHASERS, contact:

Kenneth Tanzer
Director of Information Services
Downtown Emergency Service Center
515 Third Avenue
Seattle, WA 98104
(206) 515-1519
kt...@de...
chasers.desc.org <http://chasers.desc.org>

For further information about DESC, contact:

Nicole Macri
Director of Administration
Downtown Emergency Service Center
515 Third Avenue
Seattle, WA 98104
(206) 515-1514
nm...@de...
www.desc.org <http://www.desc.org>

I am happy to say that Downtown Emergency Service Center (DESC) 
officially released CHASERS as Free and Open Source Software today.  
I've included the announcement text in this email, and it's also 
available online.  Many thanks to everyone who's helped with and 
participated in this project!

Ken

http://www.desc.org/chasers_release.html
http://prnewswire.com/cgi-bin/stories.pl?ACCT=104&STORY=/www/story/09-30-2008/0004895149&EDATE=#

September 30, 2008

*FOR MORE INFORMATION ABOUT CHASERS,
SEE http://chasers.desc.org/ <http://chasers.desc.org>

DOWNTOWN EMERGENCY SERVICE CENTER RELEASES CHASERS, FREE SOFTWARE FOR 
HOMELESS SERVICE MANAGEMENT AND BEYOND*

Downtown Emergency Service Center (DESC) is pleased to release its 
CHASERS application as open-source software. DESC uses CHASERS to store 
and manage information about clients, services and agency operations.

Created by DESC, CHASERS is both proven and a work-in-progress, and has 
been under in-house development for approximately five years. During 
this time, CHASERS has been in continuous use, and now contains 
information on over 70,000 clients served by DESC. Key features include 
web-based access, client and staff management, reporting, permission and 
access control, electronic logs, collaborative caseloads and real-time 
notifications.

"CHASERS has become an integral tool in DESC's ongoing work to serve the 
sickest and most vulnerable homeless people in our community," said 
Executive Director Bill Hobson. "We are pleased to release this software 
to the community, and hope it will become useful for other oranizations 
as well."

As used at DESC, CHASERS is built entirely on Free and Open Source 
Software. In this configuration, there are no software or licensing fees 
involved, allowing CHASERS to be used to its maximum potential. One such 
advantage is that every staff member has an account, without additional 
cost.

"DESC has benefitted greatly from the use of Free and Open Source 
Software, and from assistance from free software communities," noted Ken 
Tanzer, DESC's Director of Information Services. "I'm very happy that 
DESC is in turn contributing to the pool of free software. At the same 
time, other organizations have expressed interest in CHASERS. With this 
release, these organizations can begin determining whether CHASERS can 
provide value to their operations."

CHASERS was designed for flexibility and adaptability, and modified 
versions are used for fundraising and volunteer management, and to 
manage data for a research project conducted in cooperation with the 
University of Washington's Addictive Behaviors Research Center and 
funded by the Robert Wood Johnson Foundation. A demonstration version is 
available online.

*ABOUT DOWNTOWN EMERGENCY SERVICE CENTER*

DESC is the most comprehensive provider of services and housing for 
chronically homeless adults in Seattle and King County, and has received 
numerous national and local awards. DESC's services include shelter, 
housing, mental healthcare, addiction treatment, and employment 
services. Last year, DESC served over 6,700 individuals and moved 605 
men and women off the streets into permanent supportive housing. DESC 
currently provides 650 units of housing, with another 130 units in 
development. Increasingly, housing development is at the center of 
DESCâEUR^(TM)s mission "to end the homelessness of vulnerable adults."

*INTENDED AUDIENCE AND FUTURE GOALS*

At this stage, CHASERS will be of interest primarily to organizations 
with at least some level of technical expertise. DESC is interested in 
collaborating with other entities in the service delivery, funding and 
technical support communities to continue to expand the functionality of 
CHASERS, create documentation and increase the ease of installation, 
configuration and maintenance.

*DISCLAIMER*

CHASERS is provided entirely as-is, and DESC makes no representation 
regarding the usability or fitness of the software for any particular 
purpose. Entities that choose to use CHASERS do so entirely at their own 
risk, and DESC will under no circumstances be liable for any damages or 
consequences, direct or indirect, in connection with such use.

*FURTHER INFORMATION*

For further information about CHASERS, contact:

Kenneth Tanzer
Director of Information Services
Downtown Emergency Service Center
515 Third Avenue
Seattle, WA 98104
(206) 515-1519
kt...@de...
chasers.desc.org <http://chasers.desc.org>

For further information about DESC, contact:

Nicole Macri
Director of Administration
Downtown Emergency Service Center
515 Third Avenue
Seattle, WA 98104
(206) 515-1514
nm...@de...
www.desc.org <http://www.desc.org>

Joshua Aaron Ginzler, PhD wrote:
> thanks jonathan. yes, the other runs were in error, which i realized when i
> went back to the log last night. all of this is always making sense to me,
> in that yesterday i kept searching and searching for permission_date in the
> system_user file. then i went looking for create language commands, but i
> couldn't make heads or tails of it all as far as edits.
>
> so i am to put that exact text with quotes at the command line:
> su -c "psql -f [file] marsptdb" postgres
>
>   
The exact text, except you would replace [file] with the path and name
of the schema file, and you might be better off starting with a fresh,
empty database, which you can easily do with:

su postgres
dropdb [dbname]
createdb -O mars [dbname]
> also, in the configuration file, i set a password phrase as you folks
> suggest in wiki as "false" instead of "md5". does that sound right since i
> am not setting the method as md5 in the pg_hba file? 
>   
This md5 field is unrelated to the pg_hba conf file md5, and should be
left as true (it basically tells CHASERS that user passwords are stored
as md5 hashes).
> as well in the pg_hba, you told me to replace language for the ipv4 but do i
> also need to do it for the ipv6?
>   
I don't think you need to do anything with the ipv6 stuff
> one last thing, in the pg_mail file i think i am supposed to insert my own
> mail server and data server. i believe my mail server is smtp.washington.edu
> (obviously outgoing server) whereas my incoming is personalized. so i put in
> the smtp address. for the data server i just put in localhost. 
>   
That should be fine...it's relatively easy to change later on if email
isn't working from CHASERS.

-Jonathan

>> [root@d-128-95-80-203 ~]# psql -U mars -f /var/www/html/chasers/chasers-schema/add_system_users.sql marsptdb
>> INSERT 0 2
>> psql:/var/www/html/chasers/chasers-schema/add_system_users.sql:32: ERROR:  null value in column "permission_date" violates not-null constraint
>>     
This can be fixed (after resolving the error below), by replacing these
lines:

INSERT INTO tbl_permission(
permission_type_code,
staff_id,
permission_read,
permission_write,
permission_super,
added_by,
changed_by)

values ('SUPER_USER',2,true,true,true,1,1);

with this:

INSERT INTO tbl_permission(
permission_type_code,
staff_id,
permission_read,
permission_write,
permission_super,
added_by,
changed_by,
permission_date)

values ('SUPER_USER',2,true,true,true,1,1,current_date);

>> psql:/var/www/html/chasers/chasers-schema/add_system_users.sql:39: ERROR:  language "plpgsql" does not exist
>> HINT:  Use CREATE LANGUAGE to load the language into the database.
>>     
>
>   
That language should have been created with
schema.desc_abrc_locator.sql, so my guess is that you got an error on
that as well. Make sure you have postgresql-pl installed, and then
revise my previous directions and run the schema file in as the Postgres
superuser:

su -c "psql -f [file] marsptdb" postgres

This is necessary since only the Postgres user can create languages.

-Jonathan

ok, so i may be on my last thing for today. i finally got to
loadingthings and the first two worked (schema and look) but here is
what happened with add_system:

> [root@d-128-95-80-203 ~]# psql -U mars -f /var/www/html/chasers/chasers-schema/add_system_users.sql marsptdb
> INSERT 0 2
> psql:/var/www/html/chasers/chasers-schema/add_system_users.sql:32: ERROR:  null value in column "permission_date" violates not-null constraint
> psql:/var/www/html/chasers/chasers-schema/add_system_users.sql:39: ERROR:  language "plpgsql" does not exist
> HINT:  Use CREATE LANGUAGE to load the language into the database.

any quick answers here? i would love to finish this today.

thanks,
j

On Wed, 2007-01-24 at 16:30 -0800, Jonathan Hedstrom wrote:
> shua wrote:
> > when making changes to php.ini i have two questions.
> >
> > 1. i went into /etc/php.ini and edited the text. the only lines that are
> > actually necessary to edit DO NOT have ";" at the start, correct? reason
> > i ask is because the line "allow_call_time_pass_reference = On" appears
> > in 2 places but only once without a ";" in front of it. 
> >
> >   
> That's correct (everything behind a ";" is a comment). I'm not quite
> sure why the php people include each option twice...it seems confusing.
> > 2. for the changes regarding memory, do i need the text in the second
> > set of parentheses as well:
> >
> >   
> >> memory_limit = 32M      ; Maximum amount of memory a script may
> >> consume (8MB) (8MB barfs on FC3/PG8)
> >>     
> No, the line should simply read:
> 
> memory_limit = 32M
> 
> again, everything else behind the ";" is a comment, so the rest isn't necessary
> 
> 
> 
> -Jonathan

shua wrote:
> when making changes to php.ini i have two questions.
>
> 1. i went into /etc/php.ini and edited the text. the only lines that are
> actually necessary to edit DO NOT have ";" at the start, correct? reason
> i ask is because the line "allow_call_time_pass_reference = On" appears
> in 2 places but only once without a ";" in front of it. 
>
>   
That's correct (everything behind a ";" is a comment). I'm not quite
sure why the php people include each option twice...it seems confusing.
> 2. for the changes regarding memory, do i need the text in the second
> set of parentheses as well:
>
>   
>> memory_limit = 32M      ; Maximum amount of memory a script may
>> consume (8MB) (8MB barfs on FC3/PG8)
>>     
No, the line should simply read:

memory_limit = 32M

again, everything else behind the ";" is a comment, so the rest isn't necessary

-Jonathan

when making changes to php.ini i have two questions.

1. i went into /etc/php.ini and edited the text. the only lines that are
actually necessary to edit DO NOT have ";" at the start, correct? reason
i ask is because the line "allow_call_time_pass_reference = On" appears
in 2 places but only once without a ";" in front of it. 

2. for the changes regarding memory, do i need the text in the second
set of parentheses as well:

> memory_limit = 32M      ; Maximum amount of memory a script may
> consume (8MB) (8MB barfs on FC3/PG8)

so that seems to do something. now i am getting tons of errors on teh
run such as:

> psql:/var/www/html/chasers/chasers-schema/schema.desc_abrc_locator.sql:16548: ERROR:  role "desc_abrc_lo" does not exist
> psql:/var/www/html/chasers/chasers-schema/schema.desc_abrc_locator.sql:16549: ERROR:  role "desc_abrc_lo" does not exist
> psql:/var/www/html/chasers/chasers-schema/schema.desc_abrc_locator.sql:16556: ERROR:  relation "user_login" does not exist
> psql:/var/www/html/chasers/chasers-schema/schema.desc_abrc_locator.sql:16557: ERROR:  relation "user_login" does not exist
> psql:/var/www/html/chasers/chasers-schema/schema.desc_abrc_locator.sql:16558: ERROR:  relation "user_login" does not exist
> psql:/var/www/html/chasers/chasers-schema/schema.desc_abrc_locator.sql:16565: ERROR:  relation "user_login_latest" does not exist
> psql:/var/www/html/chasers/chasers-schema/schema.desc_abrc_locator.sql:16566: ERROR:  relation "user_login_latest" does not exist
> psql:/var/www/html/chasers/chasers-schema/schema.desc_abrc_locator.sql:16567: ERROR:  relation "user_login_latest" does not exist
> REVOKE

i assume that this means i have to go through and change all such
identifiers to fit my db and users, or is there a shortcut? the
install.schemas does not have any explanation of this other than "If
your names are different, you may need to tweak these scripts."

j
On Tue, 2007-01-23 at 14:27 -0800, Jonathan Hedstrom wrote:
> shua wrote:
> >> [root@d-128-95-80-227 ~]# psql -U mars -f schema.desc_abrc_locator marsptdb
> >> psql: FATAL:  Ident authentication failed for user "mars"
> >>     
> >
> > does this mean that i have yet to get something properly loaded in so
> > that my user can be recognized (authenticated?)?
> >
> >   
> 
> You'll need to edit /var/lib/pgsql/data/pg_hba.conf to allow connections
> for this user, something like this should work:
> 
> #this will allow local connections w/o a password, change trust to md5
> if you want password
> local marsptdb mars trust
> 
> #this allows connections from localhost
> host marsptdb mars 127.0.0.1/32 md5
> 
> Once you edit this file, you'll need to reload the configuration (from
> the command line) :
> 
> /sbin/service postgresql reload
> 
> -Jonathan

shua wrote:
>> [root@d-128-95-80-227 ~]# psql -U mars -f schema.desc_abrc_locator marsptdb
>> psql: FATAL:  Ident authentication failed for user "mars"
>>     
>
> does this mean that i have yet to get something properly loaded in so
> that my user can be recognized (authenticated?)?
>
>   

You'll need to edit /var/lib/pgsql/data/pg_hba.conf to allow connections
for this user, something like this should work:

#this will allow local connections w/o a password, change trust to md5
if you want password
local marsptdb mars trust

#this allows connections from localhost
host marsptdb mars 127.0.0.1/32 md5

Once you edit this file, you'll need to reload the configuration (from
the command line) :

/sbin/service postgresql reload

-Jonathan

here is what i have done as directed and the response returned:

> [root@d-128-95-80-227 ~]# psql -U mars -f schema.desc_abrc_locator marsptdb
> psql: FATAL:  Ident authentication failed for user "mars"

does this mean that i have yet to get something properly loaded in so
that my user can be recognized (authenticated?)?

if so, i may have not properly done the php.ini step. can someone help
me with this?

joshua
963-9679

Ok, good to know.=20
=20
Well, that looks like that portion of things is done. I'm wondering what =
to mess with next. I noticed that when I click on 'reports' I get Unable =
to access reports. Please contact your system administrator. This =
suggests that I haven't done much with these! Perhaps this is a good =
place to work on next.
=20
Nicholas Burmeister
IT Department
The Compass Center
206-357-3144
nbu...@co...
=20

________________________________

From: cha...@li... on behalf of =
Jonathan Hedstrom
Sent: Tue 12/12/2006 12:11 PM
To: general
Subject: Re: [Chasers-general] housing double listing bmp

Nicholas Burmeister wrote:
> Hey Jon,
>=20
> Sourceforge isn't happy with this screenshot, so I'm sending it to you
> normally. We can do follow up on sourceforge. Basically, I entered a
> unit and subsidized it, and its now being double listed. Somewhere in
> the customization I think we forgot to comment something out that's
> making a double listing, but heck if I know where.
The double listing is because this page lists "Current" units and
subsidies, and "All" units and subsidies. Anything in the current list
will always appear in the "All" list.

-Jonathan
>=20
>=20
> Nicholas Burmeister
> IT Department
> The Compass Center
> 206-357-3144
> nbu...@co... <mailto:nbu...@co...>
>=20
>
> =
------------------------------------------------------------------------
>

--
Jonathan Hedstrom
Data Systems Administrator
Downtown Emergency Service Center
(206) 464-1570 ext. 3014
jhe...@de...

-------------------------------------------------------------------------=

Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share =
your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
_______________________________________________
Chasers-general mailing list
Cha...@li...
https://lists.sourceforge.net/lists/listinfo/chasers-general

Nicholas Burmeister wrote:
> Hey Jon,
>  
> Sourceforge isn't happy with this screenshot, so I'm sending it to you
> normally. We can do follow up on sourceforge. Basically, I entered a
> unit and subsidized it, and its now being double listed. Somewhere in
> the customization I think we forgot to comment something out that's
> making a double listing, but heck if I know where.
The double listing is because this page lists "Current" units and
subsidies, and "All" units and subsidies. Anything in the current list
will always appear in the "All" list.

-Jonathan
>  
>  
> Nicholas Burmeister
> IT Department
> The Compass Center
> 206-357-3144
> nbu...@co... <mailto:nbu...@co...>
>  
>
> ------------------------------------------------------------------------
>

-- 
Jonathan Hedstrom
Data Systems Administrator
Downtown Emergency Service Center
(206) 464-1570 ext. 3014
jhe...@de...

Nicholas Burmeister wrote:
> Ok, that seems to have fixed that, but we're back with the housing unit issue, for some reason.
>  
> I can add a housing unit, such as MEN1 or MEN2 (the designation for the men's program we created) but when you go to add a Compass Center Residence to a client record, the unit drop down is still blank. 
The residence records are currently javascript-driven, so you pick the
project first, then the list is populated with units from that list.
(This is mostly an fyi, since I discovered the actual problem below.)
> Under Housing, further strangeness is occuring, since there now seems to be two places to enter housing units. Here's what the page looks like:
>  
>   
Both these links point to the same place, so I don't think it will
really cause any problems--it will look less strange once there are some
unit and subsidy records...
> Housing Unit Maintenance
>
> show empty recordshide empty records
>
>
> No Housing Units
>
> (Add a Housing Unit) 
>
> No Housing Unit Subsidies
>
> (Add a Housing Unit Subsidy) 
>
>   <javascript:showHideElement('housing_unitChildListAll')>    
>
> Browse ALL Housing Unit records
>
> Back to top 
> Add a Housing Unit
> 	
> Records 1-2 (of 2 total records)
> Sorted by Unit
> Page 1 of 1
>  	 #	 Unit	
> Date	
> Date End	
> Unit Type	
> Unit Size	
> Project	
> View
> 1	 MEN	 12/12/2006	 12/12/2008	 Other or N/A	  	 Mens Program	
> View
> 2	 MEN2	 12/12/2006	 12/12/2007	 Other or N/A	  	 Mens Program	
> Page 1 of 1
>   
The problem is that you added end dates to your units. The list for
adding a residence record only looks at current units, and current units
are defined by records without an end date.

-Jonathan

2005	Jan	Feb	Mar	Apr (2)	May (4)	Jun (8)	Jul	Aug	Sep	Oct	Nov (2)	Dec (1)
2006	Jan	Feb	Mar	Apr	May	Jun	Jul (55)	Aug (73)	Sep (25)	Oct (98)	Nov (73)	Dec (48)
2007	Jan (8)	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec
2008	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct (2)	Nov	Dec
2009	Jan	Feb	Mar	Apr (1)	May (1)	Jun (4)	Jul (5)	Aug	Sep	Oct	Nov	Dec
2012	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov (1)	Dec

chasers-general Mailing List for CHASERS

chasers-general — General CHASERS list traffic