C3HITS+Status+2Q2009

toc

Overall Goals

 * Align with TJD and UUA wide efforts to align congregation information reporting:
 * ? What are the standards amongst UUA congregations for reporting congregation/district statistics and other information?
 * Create a document of understanding/confidentiality agreement for certain volunteer roles including IT Services roles:
 * ?What do the Treasurer, Canvassing (Stewardship) Committee, Board Chair (or Board members) agree to now that insures church confidential information is treated appropriately?
 * modified proposed C3HUU Confidentiality and Acceptable Use form posted, based on several, including [|one found from a Canadian UUA church]
 * ? Is there a C3HUU document similar to this one? Anyone who is an ITS person working on the C3HUU PCs needs to sign this! [|Here is the current draft of the C3HUU IT Acceptable Use Policy].

Church Management System (ChMS) software:
see: []
 * SK has all the nice user friendly touches, BUT they finally admitted in early April that much of our current Logos data would have to be re-entered BY HAND, so SK trial is over
 * now pursuing next on the list, PowerChurch Plus (PC+), if you want to get a peek at what this software offers,
 * feature: Palm/Windows Mobile support so you can have information on your congregation in your purse/pocket if you wish!
 * same functions as SK, just not as nice a user front-end or integration with word processor
 * data migration support, PC+ team will do it for an extra $250 (worth it!)
 * IT Services is leading in order to provide oversight for a well integrated ChMS, volunteer assistants?

Podcasts:

 * we're close now, let's review what we need to do to get this done well and reliably
 * due to recent increase in workload, Mark is catching up on creating and uploading MP3s to the web site, could train someone to do this, volunteers?
 * to do the whole service, would need to cover copyrights, best case is to tie in with campus ministry and use UNC umbrella agreement as Duke Chapel does
 * edit out some anyway: Joys and Concerns, perhaps some "Within these walls", etc
 * to do well, would require separate mics for audio INPUT to be recorded from the sound system which AMPLIFIES the microphone input for the audience
 * really requires a separate process (sometimes separate volunteer) to oversee recording alongside person who is tending the service audio amplification
 * EZ Listening (for hearing impaired) needs to be part of Sound crew concerns for maintenance and appropriate setup

Staff PCs and maintenance:

 * anyone who does IT work and has administrative access to PCs, CAN access ANY file on the PC IF they know what they are doing. Some possible ways to keep private information private such as:
 * setting more restrictive permissions and using a Windows Domain setup with the QNAS device (for laptops that are brought into C3HUU, too)
 * password protecting all files that are sensitive (the ChMS will do that for all information posted to it)
 * attempted to have work done by local Intrex service, was absurdly expensive. Reloading XP on a PC cost as much as BUYING a new PC with Windows XP! Then all the other software we use still had to be loaded.
 * Completed documentation of processes, still looking for a volunteer(s) to do this work when a PC goes belly up. Interesting story of last volunteer! (which is why new PC for Marion has been delayed)
 * most major software on C3HUU PCs is self-updating or prompts when updates are available