Skip to content
Georgia Association of Educators
Georgia Association of Educators schoolhouse mark Georgia Association of Educators Support · Protect · Strengthen
Toll free in Georgia1 800 282 7142
Join GAE

Allyson's Test

Update Role Status
Overview: In order to ensure that the roles for members are accurate, this process updates the tables controlling membership roles that can change based on {DONT KNOW}.

Frequency: Weekly

Files Affected:
  • Files ROLE0619Tab.txt
  • Tables roleextract, rolesxref
  • Queries 004RoleXDelrecs, 005RoleAppend
Steps:
1. Obtain role extract file entitled ROLE0619Tab.txt from [which directory].
2. Import the role extract file.
1. Import ROLE0619Tab.txt into roleextract table.
2. Run query entitled 004RoleXDelrecs.
3. Delete all but 998 (Center staff) and 999 (Special purge records).
4. Run query entitled 005RoleAppend. Note: Ignore the violation error.
5. Append records from roleextract to rolesxref table.
6. Run query 006RolePhnRep to format phone numbers without parenthesis.
3. Reset the work table.
1. Delete all records in roleextract table.
2. Reset roleextract.ID field (autonumber) to 0.
Note: In MSACCESS, ROLEEXTRACT should be replaced with ROEX table.
Update Membership Status
Overview: In order to ensure that the membership rolls are accurate, this process updates the tables controlling membership status using information from online and manual systems to remove non active members.

Frequency: Weekly

Tables Affected: 1 Member, 2 MemWrkLoc

Steps:

  1. Prepare the Member and MemWrkLoc tables for archive by removing the members that were not changed through the online system. Seven queries should be run in the following order:
    1. Run q61NeaCostEq0
    2. Run q62NeaCostEq3ForUpd
    3. Run q63NeaCostEq1ForSta
    4. Run q64DelneaCostEq0
    5. Run q65ddelEq0MLoc
    6. Run q67ddelEqmemNeaCost
    7. Run q68delMLocddel10
  2. Make backups of tables updated online by members
    1. append the Members table to MembersBak[date]
      append memwrkloc to memwrklocbak[date]
      append purg to purgbakak
      append falmem falmembak
      append falwrk falwrkbakpurg
  3. Reset tables updated online by members
    delete all records in memwrkloc (reset memwrkloc.no;autonumber)
    append records from memwrklocmas to memwrkloc
    delete all records in purg (reset falwrk.NO;autonumber)
    delete all records in falmem
    delete all records in falwrk (reset falwrk.no;autnumber)
  4. Get import extract files into work tables
    import extract08 0619.txt into pearldb (delimiter="~"; 1st row has field names)
    Import Extract07 0619.txt into pearlprev (delimiter="~"; 1st row has field names;yr=7)
  5. Delete member cancellations from '08 & '07
    This will be a set of queries that match member records with PearlDB and PearlPrev recoreds. Matched records will be deleted from PearlDB and PearlPrevDB as
    needed.
Contents
The Local Assoc. table contains a list of all Locals and contains the following flelds:
1. Local name
2. Center
3. Uniserv Dir. (see special note)

4. PV_name (UD displayed on Purge/Verify rosters)
5. NEACode (see special note)
6. County
7. District
8. Display on Local Contact (list on Local Contact dropdown)
9. Display on My GAE (list the UD name )

Special Cases


Many of the exceptions listed below were made on the Web to match field operations as defined by GAE management.
1. UD assignments The site is 95% compatible with I&A but UD assignments are different for certain cases such as Heather & Kevin. Their Locals are worked by other UD's.

2. Center assignments of Locals The site is 95% compatible with I&A but Center assignments vary a little. UD's are assigned to one Center. When a Local is assigned to a UD, then in turn, the Local is assigned to the Center of the UD instead of the I& A assignment.For example, Warren is located in the EastCenter but is assigned to Deedee that works in the NorthCenter.

3. Locals with multiple UD's Most Locals have only one UD assigned to it, but Dekalb has multiple UD's. Because of this, there are special adjustments that we had to do.See Special Multi UD Updating note below.

4. Display flags Various parts of the site use the Local table to obtain info for display. We created 2 flags to control what is displayed:
a. Display on Local Contact Dropdown A value of "1" is used to indicate that the Local should be displayed in the Local Contact Dropdown. Any other entry such as "0" says Not to display.
b. Display on My GAE & Staff reports A value of "1" is used to indicate that the Local should be displayed in the MY GAE Panel & Staff Reports under the Service Centers menu. Any other entry such as "0" says Not to display.

5. NEACODE The Purge Verify system uses the Local table to obtain the Local Name for display on a Roster. In the case of Dekalb with multiple UD's, only the Dekalb (ODE) Local should have the NEACODE.DO NOT add NEACODE's to the other Dekalb records. Doing so will cause multiple listings of members on Dekalb Rosters.

6. Public versus Private Changes In most cases, you will need to make the same change to the both sites since they run on separate sites and databases.

Updating via the Admin Control Panel (ACP)

Except for year end and mass updating, most updating will be done via the ACP.f.

1. Log into the admin section of the site.
2. Select the "Local Association" link.

Updating a Local
Look thru the list of Locals to find the one you want to update. You may need to click thru the page#'s at the bottom of the page to see the one you want. For this example, we are displaying "Appling".

1. click on the "edit" button for your Local to display the details
2. Change the data that you want.
(Please note the Special Cases above when making changes.)
3. Click on the "update" button to save your changes.

Testing
To test the effect of your change:
1. Go to the page that displays the result of your change.
Local Contact example
Run the Local Contact page and select the Local
to see if changes are displayed.
Roster example
In this case, you will need to obtain the proper
login to get to the Purge/Verify system to see
the Roster you want.the page.

Special: Multi UD Updating (Dekalb example)
Locals with multiple UD's require a number of special steps:
1.Create a new UD code for the UD.Dekalb's entry is called "ODE".

2. Director Table
a.Create a separate entry for the Local.
b.Enter the UD code in the UD field.
. c.Add a separate entry for each UD.
d.Enter the UD code in the UD field.All other info should be as shown.
3. Local table
a. Create a separate entry for the Local.
b. Enter the UD code in the UD field.
c. Add the NEACODE and Display on Local Contact = 1.
d. Add a separate entry for each UD.
e. Enter the UD code in the UD field.
f.NEACODE = 0 and Display on Local Contact = 0.