| Overview Following are instructions on updating the Local table that is a part of the Local Contact system. | |
| 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) | |
| Special Cases Many of the exceptions listed below were made on the Web to match field operations as defined by GAE management. 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, 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. | |
| 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. | |
| 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. | |