Talk:CDL/Database manual

from the Macalester Public Knowledge Base

Jump to: navigation, search

Contents

[edit] Roadmap

I view CDL's DB development in three stages

  1. general buildup
  2. bugfixing and structure consolidation (we are here)
  3. user interface work

During #1, we build the DB. Once the general framework is done, big and small bugs are fixed and the internal structure of the database needs to be grounded. This is important, as step #3 cannot proceed smoothly without #2! What do I mean by structure? See this:


I think the basic buildup is done, and the DB is stuck between #2 and #3. I meant to wrap up #2 during the summerof 2004, but the work dragged on and on and there are still some structural issues (e.g. how should data be grouped together? which data entry categories should exist?) lagging behind.

While we are still in #2, development moves very slowly, because while I am working on fixing the database, you are using it real-time. I can't just keep the DB file for myself a few weeks while figuring out solutions and then send you the file, because by then my version of the file will be outdated in terms of new cases that have been enetered in the meantime.

So the way this would work would be you sending me the file over the weekend, me getting it fixed and send it back to you on monday, and you overwriting your file with my update. This restricts development time.

Once we reach #3, the split of work between DB developers (me) and users (you) can flow smoothly. In Access, there's the option of splitting off the database file with the "data" per se, as one file, and another file, the menus and data entry forms, the framework, which constitute the "user interface".

Once there are no further structural issues, then, I can keep a "user interface" file, and keep on sending you all the updated version of the user interface file, while you all can keep on working with the current data file.

The problem is that until we solve all our structural issues, DB development moves slowly - UNLESS i'm working on site. But I'm in LA. Or unless YOU could catch up and learn how to modify the DB structure. So while we have these two barriers (me not being there and you not knowinbg how to work it) we'll try to get beyond stage #2 ASAP.

[edit] What is the database structure?

So which are structural issues? For example, I had a talk with Teresa back in March of 2005 about the position of labor unions inthe DB.

I originally understood unions to be selectively "on" or "off" in specific departments within the employer. So maybe cashiers at WholeFoods are unionized with SEIU but the box handlers are to be organized through the Teamsters and are not unionized. Thus, when we keep a profile on WholeFoods we can't just check the "unionized" mark off because it depends on the department. The checkbox "labor union" needs to be located within the department table. But then, some employers are not multi-department (=small) and it doesn't make sense to mark "unionized" on a department basis. And then, sometimes we get workers who do not know how unions are hierarchized in their workplace and they know they are paying union dues etc but don't know if it belongs tothe whole employer or the dept.

So I was telling Teresa that we needed the "unionized" checkbox for all three of the categories: employee, employer, and employer dept. But Teresa said that was hard to keep track of and suggested onlyu marking unionized for employee, which was the safe way I guess.

So this is a structural issue, to give an example.

[edit] What is the user interface?

[edit] Structure

  • labor unions should go under "employment" and not under "employer"


[edit] Requested Features

  • sort cases via employer and case_date (Tim, Aug 11)
  • search for cases that have had more than one case filed against them (Greg, Aug 2)

[edit] Features List

  1. Parametered queries/reports
  2. External access (php?)
  3. Tips per case categories

[edit] Menu structure

  1. WP
    1. WPF browse cases
    2. WPF_People browse people
    3. StaffF_WP volunteer coord
  2. ESL
    1. ESLF_Classes browse classes
    2. ESLF_students browse students
    3. StaffF_ESL volunteer coord
    4. ESLR_Classes Print Classes
  3. Voces Laborales: http://CDL.adelantemac.org
  4. admin
    1. StaffF
  5. ContactosF_People Contactos
  6. Organizing
    1. MembersF editar miembros
    2. MembersR imprimir lista de miembros
    3. ContactosF_Orgs Browse by Organizations
  7. EventsF eventos/reuniones
    1. campañas,

[edit] Troubleshooting

  1. Supervisor keeps on double clicking menu items => replaced first and second links with "blank links"
  2. screen size - supervisor's is 640x480
  3. sometimes the form screen "blinks", which doesn't allow for entering data

[edit] Database knowhow

  • bypass macro security check -> tools>macro>security
  • ignore startup options -> hold down shift key while opening
Retrieved from "http://mpkb.net/en/Talk:CDL/Database_manual"
Personal tools
macalester