ODDEX Landing Page

When logging into the ODDEX application,  all users will be placed into the Landing Page.  Data included on the landing page is dependent on roles granted in OEDS.

Single Entity Access

For users with access to a single entity, the initial landing page will show the applicable area headings for the user based on their OEDS roles in a minimized state.  Clicking on the Show link to the right of the summary heading will display a grid with information/counts specific to the records in that application area.  Each summary area is independent of the other allowing the user to Show/Hide just the area(s) they wish to see at the current time.  Hiding area(s) that are not of interest at the current time will aid in the performance of loading the Landing Page.    

Multiple Entity Access

For users with access to more than one entity, the initial landing page will be empty where the application area summary headings/grids normally appear.  From the Entity/District drop down, the user has the option of leaving the landing page empty, selecting All entities they have access to or a single entity.  If 'All' or a single entity is selected, applicable area headings for the user based on their OEDS roles will appear in a minimized state.  A benefit to leaving the landing page selection empty is performance on load time of the page, this is especially beneficial for users that have access to a large number of entities such as ITC personnel and EMIS Area Coordinators.  Selecting a single entity to view on the landing page will also allow for faster load times. 

Messages - Announcements/Alerts

DEW Announcements may contain information from DEW personnel as related to the application areas.  System Alerts may contain information pertaining to the applications or systems as provided by the SSDT.  Districts should watch for new information posted in the Announcement/Alerts area at each login.  More details about the Announcement/Alert may be seen by clicking on the hyperlink.   This area also provides information on the current user, on the far right side.

The message panel may be collapsed/expanded by clicking on the -/+ next to the heading. 

Hide/Show Summary Grids

Each summary grid has a Hide/Show toggle allowing the user to condense the information shown at any given time on their Landing page.  Clicking on the Hide link,, will hide the Summary grid leaving only the Summary grid header. 

Clicking on the Show link will allow the Summary grid to be displayed on the landing page for that summary area.

SCR Enrollment Comparisons

For those with access to Student Cross Reference (SCR) the grid will show a listing of records. A row of counts will show for each district you have access to.  The grid displays up to ten entities at a time.  If the user has access to more entities, they will have to use the page navigation within the Summary to go to the next/previous page of entities.

Explanation of SCR Counts

  • All - All records submitted by the district

  • Open With Issues All/Not Hidden - All count is for all records with conflicts regardless of their age.  Not hidden count is for those records with conflicts that have not been marked as hidden.  Hidden records are those the district has reviewed and does not wish to review again so they mark the conflict as hidden.  Hidden conflicts are included in the All count. 

  • Not Reported All/Not Hidden - All count is for all records with a mismatch regardless of their age.  Not hidden count is for those records with a missing or mismatch that have not been marked as hidden.   Hidden records are those the district have reviewed and does not wish to review again so they mark the conflict as hidden.  Hidden conflicts are included in the All count.

  • Resolved Issues - Records that had a conflict at one time, but no longer do

Districts can see these counts change at any time.  A record can move from one column to another if updates are made to that record which change its status.

All of the blue counts are hyperlinks.  If one clicks on those links, they will be placed in SCR application with access to the records included in that count.  See SCR section for more detail on its use as well as what constitutes a conflict.

SCM Summary

For those with access to Student Claiming Module (SCM) the grid will show a listing of records. A row of counts will show for each district you have access to.  The grid displays up to ten entities at a time.  If the user has access to more entities, they will have to use the page navigation within the Summary to go to the next/previous page of entities.

Explanation of SCM Counts

  • All - All records of students claimed by corresponding district

  • Claimed Prior - Records of students claimed in the last 30 days

    • 7 - claimed 0 to 7 days ago

    • 15 - claimed 8 to 15 days ago

    • 30 - claimed 16 to 30 days ago

  • Not Reported in SCR - Student claims that have not been reported in SCR

    • 7 - claimed 0 to 7 days ago

    • 15 - claimed 8 to 15 days ago

    • 16+ - claimed 16 or more days ago

  • Canceled Claims - Student claims that have been canceled

    • 7 - claimed 0 to 7 days ago

    • 15 - claimed 8 to 15 days ago

    • 16+ - claimed 16 or more days ago

Districts can see these counts change at any time.  A record can move from one column to another if updates are made to that record which change its status.

All of the blue counts are hyperlinks.  By clicking on the count hyperlink, the user will be placed in the SCM application area with access to the records included in that count.

SOES Summary

For those with access to SOES the grid will show a listing of records. There will be a row of counts for each district the user has access to. The grid displays up to ten entities at a time.  If the user has access to more entities, they will have to use the page navigation within the Summary to go to the next/previous page of entities.

Explanation of SOES counts

  • No Activity - Records submitted regardless of age

  • Flags/Comments - Records with flags or comments regardless of age

  • Reviewed - Records reviewed and approved by resident district

  • Escalated - Records that have been escalated to DEW for their review

  • DEW Override - Records that DEW has set an override (funded or unfunded) on

  • DEW Auto Approved - Records that have been auto approved based on no changes in residency/guardian from prior year.  This count does not include records that are approved automatically within ODDEX for any other reasons.

 

Districts can see these counts change at any time.  A record can move from one column to another if updates are made to that record which changes its status.  For example, a record that was in the No Activity column, will move to the Flags/Comments column after a flag has been set by the resident district.

All of the blue counts are hyperlinks.  If one clicks on those links, they will be placed in the SOES application with access to the records included in that count.  See SOES section for more detail on its use.

Tuition Summary

For those with access to Tuition information, there will be Tuition Summary grid(s) on the landing page.  There will be a row of counts for each district the user has access to. The grid displays up to ten entities at a time.  If the user has access to more entities, they will have to use the page navigation within the Summary to go to the next/previous page of entities.  The user may have have two Tuition Summary grids. The 'Paying Summary' grid represents students that the LEA is obligated to pay tuition for.  The Educating Summary grid represents students that the LEA is educating and is entitled to a tuition payment.

 

Explanation of Tuition Counts

  • No Activity - All student tuition records submitted that have not had any flags or comments added.  This column is further subdivided based on the records age. 
    15 - Records that were added/changed 15 or less days ago
    30 - Records that were added/changed 16-30 days ago

  • Flags/Comments - Student tuition records with flags or comments regardless of age

  • Reviewed - Student tuition records reviewed and approved by the Resident/Paying LEA

  • Escalated - Student tuition records that have been escalated to DEW for their review

  • DEW Override - Student tuition records that DEW has set an override on

 

Users may see these counts change at any time.  A record can move from one column to another if updates are made to that record which changes its status.  For example, a record that was in the No Activity column, will move to the Flags/Comments column after a flag has been set by the LEA.

All of the blue counts are hyperlinks.  By clicking on the count hyperlink, the user will be placed in the Tuition application area with access to the records included in that count.

CCP Summary

For those with access to College Credit Plus information, there will be a CCP Summary grid on the landing page.  There will be a row of counts for each district and/or higher education institution that you have access to. The grid displays up to ten entities at a time.  If the user has access to more entities, they will have to use the page navigation within the Summary to go to the next/previous page of entities.  If the user has access to both LEA and HEI entities, they will see two CCP summary grids on the landing page, one for each of the entity types (LEA and HEI).

 

 

Explanation of CCP counts

  • No Activity - All student course records submitted that have not had any flags or comments added. This column is further subdivided based on the records age. 
    15 - Records that were added/changed 15 or less days ago
    30 - Records that were added/changed 16-30 days ago
    45 - Records that were added/changed 31-45 days ago

  • Flags/Comments - Student course records with flags or comments regardless of age

  • Reviewed - Student course records reviewed and approved by LEA

  • DEW Override - Student course records that DEW has set an override on

  • Agreements - All credit hour rate agreement records that have been submitted

  • Approved Agreements - Credit hour rate agreement records that have been approved

 

Users may see these counts change at any time.  A record can move from one column to another if updates are made to that record which changes its status.  For example, a record that was in the No Activity column, will move to the Flags/Comments column after a flag has been set by the LEA.

All of the blue counts are hyperlinks.  By clicking on the count hyperlink, the user will be placed in the CCP application area with access to the records included in that count.

Course Counts

For the CCP application area, the counts shown on the landing page for course related data will not be a direct correlation to what is shown on the Summary page.  The counts on the landing page are course based counts.  One student may have many course records included in the count.  However, the CCP Student Course Summary pages are Student based.  There is only one row for the Student/HEI/LEA combination regardless of how many courses the student may be enrolled in.  The agreement counts should match up with what is shown on the Agreement Summary pages.

 

Child Nutrition Direct Certification

For those with access to CNDC information, there will be a Child Nutrition Direct Certification grid on the landing page. There will be a row of counts for each district the user has access to. The grid displays up to ten entities at a time.  If the user has access to more entities, they will have to use the page navigation within the Summary to go to the next/previous page of entities. 

 

Calendar

For those with access to a Community School or those that sponsor a community school, there will be a Calendar Summary on the landing page.  There is only one calendar per LEA, therefore, the hyperlinks will only ever reflect a count of zero or one depending upon the approval status of the calendar.  The counts may change from one column to another as the calendar is reviewed by the sponsor or the Community School submits an update to their calendar data.  An example is if the sponsor had rejected the calendar due to inaccurate information.  The rejected column would show a count of 1.  When the Community School submits updated calendar data, the calendar becomes unreviewed. The calendars to approve column will reflect 1 and the rejected column will reflect 0.