(1) Field of the Invention
The present invention generally relates to methods and systems for data management. In particular, the present invention is directed to methods and systems for managing educational data.
(2) Background
In prior educational data systems, various schemes are used to identify student and staff data. For example, in one system, each school, district, or region is provided a pool of identification numbers (IDs) to draw from. In another system, an ID is provided that derives from a student's or staff member's data, e.g., a combination of first initial, last name, and birth date. In other systems, a student's or staff member's social security number is used as a unique identifier.
Prior embodiments of the disclosed subject matter provide a way by which an education agency can assign unique identifiers to students and staff members. In prior embodiments, the following process flow was used to assign unique identifiers to students and staff members: 1) An end user submits certain data about the individual to whom a unique identifier is to be assigned. Some of the data is mandatory for the system to work. Other data is optional. Providing the optional data can assist the system in making a correct identifier assignment; 2) The data is validated to insure that all the required fields are present and they are in the correct format; 3) Data errors are flagged; 4) An end user fixes any and all data errors; 5) A matching engine attempts to find pre-existing identifiers. Outcome could be one matching person, no matching persons, or one or more near matching person(s); 6) End users manually resolve the near match outcomes; 7) Unique identifiers are assigned to data record; and 8) End users download all assigned identifiers in order to import them into their local data system.
Unlike some prior art systems, identifiers are not generated on the fly. Instead, identifiers are selected from a pool of identifiers that are pre-generated. When the application needs an identifier, it is taken from the pool. This insures that the identifier is unique and insures that identifiers do not repeat across multiple installations of the system. This is to make sure that the installation in one state has a different pool of identifiers than an installation in a second state.
In prior art systems, the selection of an end user during correction of data errors was not flexible. For example, a user at a state or district level was unable to forward an incorrect data record to an end user at a school for correction.
One aspect of the invention is a method for assigning a unique identifier to a student or staff member data record. The method includes the following: receiving student or staff member data to develop a data record; validating the student or staff member data; flagging data errors in the student or staff member data to create a work assignment for correcting the data errors; identifying a worker or end user to complete the work assignment; routing the work assignment to the end user, wherein the end user is at one of the state, district, or school levels of an educational organization; limiting access of the end user to only those records within the educational organization that are required to complete the work assignment; completing the work assignment to correct the data errors in the student or staff member data record; and assigning a unique identifier to the student or staff member data record.
Another aspect of the invention is a system for assigning a unique identifier to a student or staff member data record. The system includes the following: a data intake module for receiving student or staff member data to develop a data record; a data validation module for validating the student or staff member data and flagging data errors to create a work assignment for correcting the data errors; a data correction module for identifying an end user to complete the work assignment, routing the work assignment to the end user, wherein the end user is at one of the state, district, or school levels of an educational organization, limiting access of the end user to only those records within the educational organization that are required to complete the work assignment, and completing the work assignment to correct the data errors in the student or staff member data record; and a data record identifier module for assigning a unique identifier to the student or staff member data record.
For the purpose of illustrating the invention, the drawing shows a form of the invention that is presently preferred. However, it should be understood that the present invention is not limited to the precise arrangements and instrumentalities shown in the drawing, wherein:
Referring now to
In a broader view of the disclosed subject matter, a method for delegating work across a hierarchical organization is disclosed. The method includes receiving a work assignment at a first level of the hierarchical organization; identifying an end user to complete the work assignment; routing the work assignment to the end user, wherein the end user is in a different level of the hierarchical organization than the first level; and limiting access of the end user to only those records within the educational organization that are required to complete the work assignment.
Still referring to
The invention provides a unique way in which to delegate the work needed to be done to get an identifier down to the parties who have the most knowledge. For example, in our system, someone at a district level can delegate work down to someone at a school level. Assume that there is a data error (an individual does not have a date of birth) that has to be fixed. Someone at a district level might not know the date of birth because they do not know the individual. However, someone at the school level does know the person and can provide that information. This process provides ways in which to delegate the responsibility of filling in that date of birth down to a school user.
The disclosed subject matter differs from prior versions in that work assignments can be delegated to any end users at any level of an organization. Previously, it was not possible to delegate work assignments downwardly from a high level to a low level within an organization, e.g., from the state or district level to the school level. One benefit of systems and methods according to the disclosed subject matter is that it will get the work into the hands of the users who have the required knowledge. As a result, it will lead to better data, which will lead to better business decision-making.
The basic user hierarchy of our system is: State User→District User→School User. The old process limited a user's ability to delegate work and handle other case management issues. As an example, let us assume that Bob works for the Allentown School District; Sally works for Lincoln High School; and Peter works for Washington High School. Both high schools are in the Allentown District. Assume that Bob submits a file to the system containing students/staff members from both high schools. At one step in the process, Bob discovers that a student/staff member from Lincoln HS is missing a Date of Birth. The old process would not allow Bob to delegate that work down to Sally. The only option Bob had was to repair the problem himself. This was not ideal since Sally and Peter would most likely have better knowledge of the students/staff members then would Bob.
The disclosed subject matter gives users a lot of flexibility as to whom they can assign work. Using the example above, assume Bob uploads a file containing students/staff members from both Lincoln HS and Washington HS. If Bob comes across the missing Date of Birth issue again, the system would automatically notify Sally of the missing value and allow her to repair the problem.
When prior systems and methods were created, it was not anticipated that a user at the district level would not have the knowledge of the students/staff members in a school in that district. The issue is especially significant in larger districts containing tens of thousands of students/staff members.
Although the invention has been described and illustrated with respect to exemplary embodiments thereof, it should be understood by those skilled in the art that the foregoing and various other changes, omissions and additions may be made therein and thereto, without parting from the spirit and scope of the present invention. Accordingly, other embodiments are within the scope of the following claims.
Number | Date | Country | |
---|---|---|---|
60955165 | Aug 2007 | US |