Universal forms engine

Abstract

A forms engine allows data sharing between customizable on-line forms, such as college admissions applications. Before applying, an applicant opens an account with a third party application servicer. After the applicant completes an application for one institution, the data is saved in a data base and automatically populates fields in subsequent application forms. The form for each institution is created from a form description file. Each form is branded for its institution and forms for different institutions differ in appearance and content so that the presence of the third party servicer is transparent to the applicant.

Description

FIELD OF THE INVENTION

This invention relates to a computer implemented method and apparatus for processing forms and, in particular, to a method and apparatus for processing customizable application forms that share information from an extensible database.

BACKGROUND OF THE INVENTION

The processing of college admission application forms described below is illustrative of the current state of forms processing. Students applying to colleges and universities typically complete a separate paper application for each institution to which they seek admission. Each application is then mailed to the corresponding institution along with an application fee.

Many institutions would like to simplify the application process by allowing students to apply over the Internet. Although an Internet application allows an institution to process the application information electronically, a student is required to re-enter the same information for each subsequent application to a different institution or to the same institution for a different academic term. Moreover, if the institution wishes to change the application form, the institution must typically revise the source code that creates the application form, thereby making changes to the application form expensive and inconvenient.

One could reduce redundancy in the application process by allowing students to complete a single, generic application provided by a third party who would then transmit the application to any designated institution. Such systems, however, would make it impossible for institutions to customize their applications form. In an environment where schools are competing for top students, the image that a school projects to potential students is important, and a customized application can help project the image that the school wishes to create. The questions that a school asks on its application reflect the values of the institution. Many schools want information different from that which would be on a generic form. Thus, it is unacceptable to many institutions to use a generic application form.

Most institutions continue, therefore, to use primarily paper applications or their own on-line applications, with the disadvantages described above. Moreover, the institution must then process the application fee for on-line applications, which may require that the institution have some expertise in electronic commerce.

SUMMARY OF THE INVENTION

Accordingly, it is an object of the present invention to provide an improved method of processing forms.

It is yet another object of the present invention to provide such a method that allows data sharing between customizable forms, the customization including branding of forms to specific institutions.

It is yet a further object of the invention to provide such a method that uses an extensible data-sharing database.

It is still another object of the present invention to provide an improved method of processing admissions applications.

The present invention comprises a universal forms engine that permits the creation and processing of customizable electronic forms and selective sharing of information between the customized forms. A user thus enters data only once, and the data is shared through an extensible database between disparate forms. The forms are completed by a user over a computer network and information from each completed form is forwarded to the appropriate entity over a computer network. The ability of the forms engine to present a form for user input, to receive data from the user, and to provide the data to the appropriate entity is independent of the computing platform of the user and the entity. Any fees associated with the forms can be processed electronically over a computer network together with the forms.

The invention thus creates forms, parses data on forms, stores data, retrieves the data, and deploys the data onto other forms. As additional forms are completed and additional information becomes part of the database, the amount of information that must be manually entered on new forms decreases because the new forms are automatically populated with the previously entered data.

A form is considered to be essentially a container for data and implies an associated process. The forms engine integrates the form, the data, and the processing regardless of the appearance of the form, the type or significance of the data, and the processing that follows collection of the data.

Metadata, that is, information that characterizes the applicant data is also stored. For example, in one embodiment, an attribute table describes characteristics, such as permissible values and accessibility to various institution personnel, of applicant attribute data. In another embodiment, such properties of the applicant attributes are stored in XML files. Storing metadata provides greater control over the data validation, sharing between forms, grouping, and access.

User information and application information are abstracted from the coding, that is, the user information and application information is stored in a way that allows the application information and the user information to be changed without reprogramming. This abstraction allows the set of user data to be extended without reprogramming, allows the user data to be displayed in different formats in different applications, allows the data to be validated to ensure that it can be used by the institutions, and eases access to the information over the Web by institutions. Abstracting the application information allows the application itself to readily changed, and allows changes, such as changes to application dates, to be made by the institutions themselves. The abstracted information is saved, for example, in a relational database or in an XML file.

The subject matter of the present invention is particularly pointed out and distinctly claimed in the concluding portion of this specification. However, both the organization and method of operation, together with further advantages and objects thereof, may best be understood by reference to the following description taken in connection with accompanying drawings wherein like reference characters refer to like elements.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a network through which applicants, a servicer, and institutions are connected in a preferred embodiment of the invention

FIG. 2 shows an entry web page presented to an applicant of FIG. 1

FIG. 3 shows a web page showing the results of an on-line college search that provided the link to the entry web page of FIG. 2.

FIG. 4 shows a web page for creating a new account with the servicer of FIG. 1

FIG. 5 is a diagram showing schematically how accounts are created in a preferred embodiment of the present invention.

FIGS. 6 a-6d show a web page used to supply directions and information to the applicant of FIG. 1.

FIG. 7 shows an applications options page that provides the applicant with links to an application instruction page,

FIGS. 8 a-8d shows an application instruction page for an on-line application.

FIGS. 9 a-9c shows the first page of an on-line admissions application

FIGS. 10 a-10c shows the second page of an on-line admissions application

FIGS. 11 a and 11b shows the third page of an on-line admissions application

FIGS. 12 a-12d shows the fourth page of an on-line admissions application

FIG. 13 is a diagram showing schematically the interactions between the applicant, the forms engine and the applicant database during initial access of an application form.

FIG. 14 is a diagram showing schematically the interactions between the applicant, the forms engine and the applicant database as data is posted from an application form.

FIG. 15 shows a flowchart of the interactions shown in FIGS. 13 and 14.

FIG. 16 shows the steps shows the steps that occur in a preferred embodiment when an applicant contacts the forms engine.

FIG. 17 shows the “back-end” states available during application processing.

FIG. 18 is a simplified example of classes used in an object-oriented programming implementation of the invention.

DETAILED DESCRIPTION

The system according to a preferred embodiment of the present invention comprises a forms engine that processes applications for admission to institutions. The preferred embodiment, which is operated by a third party application servicer, uses relational databases for storing information and communicates with applicants and institutions over the World Wide Web. The invention is not limited, however, to the processing of any particular type of form or to the use of any particular network or database.

Overview of a Preferred Embodiment

FIG. 1 shows multiple applicant computers 14 that communicate with a server 16 through the portion of the Internet 18 known as the World Wide Web (the Web). A typical applicant computer 14 comprises a personal computer, such as a Pentium-based personal computer using a Windows-based operating system and running a commercially available Web Browser, such as Netscape Navigator or Internet Explorer. In a preferred embodiment, applicant computers 14 can use an older, text-based browser, because processing, such as error checking, is performed at server 16, rather than at the client browser.

Server 16 is a computer, such as a Sun Solaris UltraSparc Server, that is executing a forms engine of the present invention, as well as Web server software that coordinates communications with visitors to the form engine Web site. Information and forms transferred from server 16 are typically formatted in a hypertext mark-up language (HTML) and can include text, programs, graphics, video, and audio portions. Server 16 is preferably operated by a third party application servicer 24 and is connected to secure data storage 26. Multiple institution computer 28, operated by institutions, such as colleges or universities that require admissions applications, also communicates with server 16 over the Internet 18.

Although the preferred embodiment of the invention is implemented using an Internet Web site, the invention is not limited to any particular type of computer or computer network. By making the applications available over the Web, any applicant with a Web browser can apply electronically. On-line application also allows the application fee to be processed on-line, so that credit card settlements, electronic bank withdrawals, and other payment methods can be performed more efficiently, and the settlement can be easily facilitated by the third party that operates the application forms engine to which multiple institutions subscribe.

FIG. 2 shows an entry page 36 that is presented to an applicant who has accessed server 16 of FIG. 1. In a preferred embodiment, entry page 36, as well as all other pages presented to the applicant, is presented as an HTML page. Pages on which the applicant enters information use the HTML <FORM> tag. The HTML form posts information to server 16, which executes a common gateway interface (CGI) program specified by the form to process the received information.

The CGI program is preferably written in Perl, C, C++, Java, or another language that supports CGI. The CGI program accesses a database that includes information about the customized application form and about the applicant. The database is preferably a relational database that is accessed using a structured query language through a database management system, such as Informix®, by Informix Software, Inc., based in Menlo Park, Calif. The invention is not limited to a particular implementation technology. The implementation details of the invention are expected to change as computer technology evolves.

Entry page 36 can be accessed from, and can be in the same style as, an institution's own world wide web site. Entry page 36 can also be accessed from other links, for example, by a link 38 (FIG. 3) on a results web page 40 from an on-line college search, such as the CollegeNET™ System, operated by the assignee of the present invention. Entry page 36 is branded with a logotype 42 branding the application as belonging to the institution to which it is directed, although the application is preferably hosted by a third party to ease data sharing across institutions and electronic processing of application fees.

Before accessing an application from entry page 36, each applicant is required to have an account with the third party servicer 24. Entry page 36 includes a link 52 for creating a new account. FIG. 4 shows a web page form 54 that is presented to the applicant to create a new account. Although the account is with third party servicer 24 and can be used to apply to many institutions, web page form 54 is branded with the logotype 42 of the institution to which the applicant is applying. Thus, it is transparent to the applicant that the application is being processed by third party servicer 24.

FIG. 5 shows schematically the actions that comprise the account creation process 56 required to create an account. The applicant uses a web client 58, such as Netscape Navigator, to enter personal information, such as name, address, e-mail address, and a user name and password for accessing the system. The password is encrypted and saved, along with the user name, in a password database 60 connected with server 16 (FIG. 1) and user information is saved in an applicant database 62, which databases comprise database 26.

Entry page 36 (FIG. 2) also provides an information link 68 to provide the application with directions and information. FIGS. 6a-6d show a preferred information web page 70 that is returned to the user in response to a request for information. Web page 70 is also branded with logotype 42 indicating the institution to which the application is directed. Web page 70 includes an application option page link 72 (FIG. 6d) to the actual application, as does entry page 36. Entry page also includes a link 74 to the user's personal log page. The personal log describes the status of all applications the user has worked on, including applications that have been submitted and applications that are in various stages of completion. Entry page 36 also includes a link 76 for changing a user's password.

FIG. 7 shows an applications options page 82 that provides an application instruction page link 84, an application link 86, and links 92 to supplemental forms, such as a counselor's report or teacher recommendation forms, that accompany an application. FIGS. 8a-8d shows application instructions 94 reached from application link 86.

FIGS. 9 a-9c show the first page of an electronic, on-line admissions application 96 that is customized in content and appearance for a particular institution. As shown in FIG. 9a, each application is individually “branded,” that is, it carries the name and logotype 42 of the institution and appears in a style that is representative of the institution. Thus, it is transparent to the applicant that a third party is servicing the application, that is, the applicant may not even be aware that the application is processed by a third party servicer. In accordance with the invention, the third party servicer provides customized forms for each participating institution, and data is shared between the customized applications. Information that had previously been entered in connection with prior applications to any institution is automatically inserted into the customized form. Information entered by the applicant onto the application form is stored in an applicant database for automatic insertion into subsequent applications by that applicant. The HTML source code for page 1 is attached in Appendix 1. FIGS. 10a-10c, FIGS. 11a-11b, and FIGS. 12a-12d show additional pages of application 96.

FIG. 13 shows schematically the interrelationship when supplying a form pages to an applicant between a forms engine 104 of the present invention, applicant database 62, password database 60, and web browser client 58 running on applicant computer 14. FIG. 13 shows that forms engine 104, preferably implemented as a CGI program, performs four primary functions. When the applicant requests an application form for a particular institution and the request is authenticated by comparing the password with the password in the password database 60, forms engine 104 retrieves user information regarding the status of applications that are pending or completed.

Forms engine 104 then generates a customized application form based upon an application description in an application data file 108. Forms engine 104 then retrieves user data that was entered in previous applications and stored in the applicant database 62, and merges the user data into the current application, which is then returned to the applicant as an HTML form. The applicant then enters any requested information that was not automatically inserted from the database.

Application 96 includes fields for the applicant to enter the specific information the institution requests of its applicants. The information is requested in a format chosen by the institution. The style and content of the customized application expresses the values held by the institution. The customized content of each application allows the school to obtain specific information that it chooses to characterize its applicant pool, including factors that it believes may correlate with student success at the particular institution.

FIG. 14 shows schematically the interactions between forms engine 104, applicant database 62, and web client 58 with respect to forms engine 104 receiving data posted from the applicant. Forms engine 104 performs a “front-end” validation on the posted data 118. Data validation is explained in detail below. If the data fail validation, a data correction page is sent to the applicant. If the data pass first stage validation, the next application page is prepared by merging applicant information from the applicant database 62 with form information in application data file 108 and sending the resulting HTML application page to the applicant.

After all the pages have passed first stage validation and the applicant attempts to submit the completed application to the institution, a second stage validation is performed. If the second stage validation is successful, user data 120 is written to the applicant database 62 and payment scripts 122 are executed in which the user is given an option to select any one of several of on-line payment methods. Credit card information is verified from a credit card database 124. After the information on the application is validated, it is transferred to the institution in a data format specified by the institution. The information is also stored for use in subsequent applications in an applicant database 62, which is independent of the institution.

FIG. 15 is a flowchart showing the products at each step of processing by forms engine 104 described in FIGS. 13 and 14. Optional steps are shown in dashed lines. FIG. 15 shows that an applicant 126 contacts forms engine 104 by a browser request for an application. Before presenting an application page to an applicant, forms engine 104 determines the state of the application process, and only presents appropriate pages to the applicant. For example, most institutions have application date windows during which applications, whether electronic or paper, for a particular term are accepted. The forms engine verifies that the application is being submitted within the allowed window. Unlike pre-printed paper applications, however, the invention provides the schools the flexibility of easily changing the application date window, so that the time to apply can be extended if the institution wants to receive additional applications.

Forms engine 104 uses data from the appropriate application data file 108 (FIG. 14) and previously entered user data to generate a page of a form 128. Data 130 is entered on the form page, by the applicant or from the database, and the page undergoes a first stage data validation 136 upon being posted by the applicant. A correction page form is submitted to the applicant each time a data validation fails, and the data is saved to the database upon successful validation. The process is repeated for additional pages until the form is completed and the applicant submits the form.

When the applicant indicates that the application is ready to be submitted to the institution, a final, more thorough validation 136, known as second stage validation, is performed on the data. Second stage validation ensures that information required by the specific institution to which the application is directed is present and that the information meets certain content criteria specified by the institution. The data validation is customized for each institution. If the application fails second stage validation, a data correction page is returned to the applicant. The validated, submittable data 140 is stored in applicant database 62 in connection with the application. The data is then processed and transformed 142 as described below in connection with aliases, and saved for use in other forms that the applicant may complete in the future. A payment 148 is then processed and application transaction processing 150 is completed. The forms engine then converts the application information into a form compatible with the institution's internal databases and delivers the information 152 to the institution's database 154.

When the applicant subsequently applies to a different institution or to a different program within the same institution, a new application, customized for the different institution, is presented to the applicant. Information that was entered onto previously submitted applications is retrieved from the database and presented to the applicant as populated fields of the new application, so that the applicant is not required to enter information more than once. The applicant can change the values in a pre-populated field if desired and the new values are saved for use in subsequent applications.

As described in more detail below, information about the applicants is maintained as a set of attributes, each attribute corresponding to database fields. If an institution chooses to include in its application a request for an applicant attribute that does not correspond to one included in the database, the database is easily extended to include the new applicant attributes without reprogramming the forms engine. Once the new attribute is added to the database, it is available for automatic inclusion in all subsequent applications.

In the preferred embodiment, each attribute used to characterize applicants has a unique identifier or alias. The unique identifier allows the engine to recognize when the same information is being described by different labels or entered in a different format on different application forms. The information can then be saved properly and inserted into subsequent applications, regardless of differences in the entry format and labels in the first and subsequent applications. Thus, the variables can be universal and unique data elements having different names can be shared among applications.

For example, one institution on its application may refer an applicants last name as a “family name” while another institution may refer to the last name as “surname” or a “last name,” yet the forms engine would share the data properly between such application forms. As another example, if a first application form requests multiple choice-type information in the form of radio buttons and the second form requests the same information in the form of a pull-down menu, information entered on the first form in the radio buttons would appear in a pull-down menu box on the second form.

While providing the institution flexibility to designate and request the information any way it chooses on its customized application, the information is retrievable onto subsequent applications regardless of how the subsequent applications label or display the information. The forms engine of the present invention can thus share information across applications, regardless of how the information is expressed in a particular application, unless the data has been designated as described below as private to a particular application and not shareable.

Each applicant attribute is characterized by one or more properties. The properties that characterize an applicants' attributes can specify, for example, whether and under what conditions the attribute data can be shared between forms, whether the attribute is a universally required field, or whether the attribute is specific to a particular geographic region. For example, an attribute named “California Driver License Number” is applicable only to institutions in California. Other information may be applicable to all institutions within a region but not to other institutions. Some applicant attributes are applicable only to institutions in a particular school system. Individual pieces of information can also be grouped and properties can be specified for the groups. The application can also include information that designates the routing of the information to groups, such as financial aid officers, within the institution.

The invention not only allows an application to be customized for each institution, it allows the information submitted by the applicant to be transmitted to each institution in any data format that the institution requests so the institution is not required to convert the data to a useable format. For example, multiple fields, such as first name and last name, may be combined into a single field, and the data fields may be delimited by a delimiter specified by the institution. Data may also be transmitted to the institution, for example, as name-value pairs, as fixed records, in EDI, or printable PDF format. Thus, the applicant information is entered in a customizable form on a browser running on any type of computer platform and stored at third party servicer 24 in a database. The information in the database is then reloadable into another customizable application form for a different institution. The information is also transmittable to an institution in its preferred format regardless of the platform used by the institution to process the information.

After an application is sent to an institution, the information remains available in the database of the third party servicer for further analysis by the institution. The institution can, for example, sort or view applicants based upon attributes such as test scores, grade point average, participation in sports, or musical talent. Moreover, each applicant attribute has a property that can be used to specify who in the institution has access to the attribute for the purpose of uploading the information or of processing the information to characterize the applicant pool. For example, parts of an application dealing with academic background may be viewable by academic departments, whereas more personal information may be viewable only by school administrators.

A preferred implementation of the invention comprises a single forms engine program, a single applicant database, including information on all applicants, and one application data file for each different application of each the participating institutions. The application data file describes the format of each application, and the forms engine displays information from the database in the format prescribed by the application data file.

The applicant database can be extended to include new attributes without making any changes to the forms engine program or to the application files of institutions that chose not to include the new data. The forms engine automatically uses the application data file to produce the requested application in HTML format for display on the applicant's browser. The application description file can be easily modified, for example, to change labels or to add additional fields. The appearance of the application for each institution can be changed by changing its application description file, without reprogramming the forms engine. The completed application is transmitted to the institution with the data in any format that the institution prefers. The institution can therefore upload the data directly into its applicant or student information system database, merging the information seamlessly into their existing work flow, thereby avoiding the additional expense and errors of re-keyboarding the information. The forms engine thus has the capability of outputting application information universally across platforms.

A transactions database table and a transactions operations table track completed transactions and operations to assist the engine in maintaining information about the state of each application, so that only appropriate pages are presented to the applicant. These tables also allow the applicant to track the progress of his or her applications and online payment.

Database Structure

The tables described below are used in a preferred college admission forms processing system. The invention can be used for processing many different types of forms without departing from the scope of the invention, and skilled persons will recognize that different database structures will be required in different applications.

Attribute Table

A first database table, the Attribute Table, includes a list of all attributes that can be used to describe an applicant. The Attribute Table thus defines the variable space for the entire system. Each attribute, such as Name, Social Security Number, and SAT score, is represented by one row of the Attribute Table and is identified by a unique Attribute Identification Number. The Attribute Table includes properties of each attribute, such as whether the attribute is a required field for first stage validation (explained below) and whether the attribute is part of a data group, such as a geographical region or an institutional group. The Attribute Table also includes references to first stage validation rules, if any, for each attributes. The Attribute Table does not include values of the attribute for any particular applicant.

User Attribute Table

The values assigned to attributes for individual applicants are stored in a User Attributes Table. Each row of the table includes a User Identification, an Attribute Identification Number, a sequence for the Attribute Identification Number, and a data value. When an applicant enters information on an application page on the Web and posts the form to the server, the information entered by the applicant is stored in the User Attribute Table after first stage validation. The form is posted when the applicant switches to another page or when the applicant indicates that the information is to be saved. An applicant may change the values of an attribute from one application to another. For example, an applicant may change his or her SAT scores to reflect new test results.

The User Attribute Table always includes the latest information that an applicant had entered and is used to supply information for new applications. When the user calls up an application to complete, data is read from the User Attribute Table. When a new application includes attributes that were not requested by any application that the user previously completed, a new row corresponding to the new attribute is inserted into the User Attribute Table. Preferably a single User Attribute Table includes the attribute information on all applicants in the systems.

User Attribute Sent Table

After an application is completed and it passes second stage validation, the information contained in the application is stored in a User Attributes Sent Table, which represents a snapshot of the submitted application. The structure of the User Attribute Sent Table is very similar to that of the User Attribute Table. The primary key of the User Attribute Table is a user identifier (the users log-on name), whereas the primary key of the User Attribute Sent Table is a Transaction Identifier, which identifies a unique combination of user, application, and application term. Thus, there can be multiple records for a single user in the User Attribute Sent Table if the user has submitted multiple applications or the same application for different application terms.

The Transaction Identifier is the same identifier used in the Transactions Table, described below. Thus, one can scan the Transactions Table for Transaction Identifiers that correspond to applications that are shown as having been submitted, and then use those identifiers to look up data related to those applications in the User Attribute Sent table.

Second stage validation is performed before writing a record into the User Attribute Sent Table and may, for example, combine fields such as last name and first name into a single field. Thus, the User Attribute Sent table shows exactly what was sent to the institution, and therefore includes a record for each application that was completed by a user. To review what data was sent, the institution reviews information derived from the records in the User Attribute Sent Table, which are then put into a format requested by the institution.

Applications Table

Each customized application is represented within an Applications Table, which defines the data set for each application. Each row in the Applications Table pertains to one attribute in a specific application and includes information such as an Application Identification Number, Attribute Identification Number, Attribute Sequence Number within the application, any second stage validation rules (described below), the Identification Number of the institution to which the application belongs, etc.

Application Data File

The Application Data File is a specially formatted text file that acts as an application description. It is a series of “directives” and optional arguments which the forms engine parses to build the HTML form and to merge in user data. The directives are interpreted by means of a look-up in a data structure that stores the directive interpretations. For example, a line in the Application Data File may be “SS_NUM.” Upon encountering the line, the forms engine will look into a data structure to interpret SS_NUM. SS_NUM may mean, for example, to display a text box with a label that reads “Enter Your Social Security Number” and to put the previously supplied value for social security number (stored in the User Attribute Table) into the text box. SS_NUM may also prescribe a minimum length, maximum length, and call a function that creates the text input box. The directive could also set flags that indicate a particular state for the application. The Application Data File can optionally supply arguments to directives. Arguments may, for example, instruct the forms engine to apply specific labels or to override default values, so that the label or format for entering the data can be customized. The information in the Application Data File could alternatively be included in the Applications Table.

In an alternative embodiment, rather than having the application information stored as directives and building the application whenever a student invokes it on-line, the application is built by a pre-processor utility that is run once to produce an “application template” with a regularized syntax. In other words, an Application Data File entry such as “SS_NUM” is replaced by a template line such as “SS_NUM|TEXT|Social Security Number: |11|11”.

In the previously described embodiment, the Application Data File lines represent function calls with optional arguments. The forms engine executes these function calls, which in turn execute a form-element-producing function like “ITEXT” which produces a text box. Thus, the forms engine not only needs to have available hundreds of functions, it also has to do two (or more) layers of function execution for each line in the Application Data File.

In the alternative embodiment, most of this processing is performed off-line during the application development phase, and the results of the processing is saved in the template file. The on-line forms engine then pulls in this “pre-digested” template file. Each line of the template file is a pipe (“|”) separated list of: (1) variable name; (2) form element [for example, form element ITEXT is textbox, IRADIO is radio button(s), etc.]; (3) question label; and (4) arguments needed by the form element function.

Whereas the forms engine in the first embodiment is analogous to an interpreter, executing a shell script, the template in the second embodiment is analogous to compiled code. The pre-processing is analogous to a compilation phase, and the output template file is analogous to a binary object. It is composed of instructions to the engine, like compiled code is composed of instructions to the CPU, whereas the bulk of the forms engine in the first embodiment comprises code to do the interpretation, the forms engine in the second embodiment has a very small instruction set: basically one instruction per form element, plus a handful of special instructions.

The template file gives the application developer absolute freedom to quickly update the application with no need to rewrite or add program code to the forms engine. Use of templates also dramatically reduces the number of functions needed by the engine, as well as the execution overhead.

The template file can be in the form of specially tagged HTML; that is, instead of a line-by-line set of directives, the template can look like HTML with embedded special tags representing the form element/variable/value to interpolate.

Below is an example, simplified for clarity, of a part of a template represented in a specially tagged HTML:

<H1>Biographical Information</H1>
<OL>
<LI>
<QUESTION ATTR_ID=”53” ARGS=”SS_NUM|ITEXT|11|11”
VALRULE=”Req( );Int(- ,);Len(9)”>Please
enter your Social Security Number:
</QUESTION>
</LI>
<LI>
<QUESTION ATTR_ID=”106” ARGS=”BIRTH—
DATE|DATEMDY”
VALRULE=”Req( )”>Please enter your birth
date (MMDDYY):
</QUESTION>
</LI>
</OL>

To process the template, the forms engine need only look for <QUESTION> . . . </QUESTION> sections and parse them. Many other pieces of logic could also be embedded into the templates. The output of the processed template is an HTML form that is viewable by the student completing the application. The output from the above template snippet could look like this, with the special QUESTION tags converted into HTML form elements and user data incorporated:

<H1>Biographical Information</H1>
<OL>
<LI>
Please enter your Social Security Number:
<INPUT TYPE=”TEXT” NAME=”SS_NUM”
VALUE=”200-00-0000” SIZE=11 MAXLENGTH=11>
</INPUT>
</LI>
<LI>
Please enter your birth date (MMDDYY):
<NOBR><INPUT TYPE=”TEXT” NAME=”mdy1_BIRTH—
DATE”
VALUE=”09” SIZE=2 MAXLENGTH=2></INPUT>
<INPUT TYPE=”TEXT” NAME=”mdy2_BIRTH_DATE”
VALUE=”17” SIZE=2 MAXLENGTH=2></INPUT>
<INPUT TYPE=”TEXT” NAME=”mdy3_BIRTH_DATE”
VALUE=”1966” SIZE=4 MAXLENGTH=4></INPUT>
</NOBR>
</LI>
</OL>

The above page is then transferred to the user.

Institutions Table

The Institutions Table includes a row for each institution. Each row includes an Institution Identifier, an Institution Name, an identifier for a parent institution if any, and other information about the institution.

Institutions can also be arranged in a hierarchy, with one institution belonging to another institution. The Institutions Table allows the construction of an arbitrary hierarchy of institutions, which can be used to control data access. Information in the Contact Table (described below) and Attribute Table is combined with information in the Institutions Table to determine access to particular attributes in applications. For example, a financial aid officer in the medical school of a university may have access only to financial information on the medical school application, whereas a financial aid officer of the university or of the university system may have access to financial information on all applications. Thus, the invention permits flexible control of data down to the attribute level.

Institutions can be grouped geographically or by other characteristics. The Institutions Table can have fields indicating to which groups the institution belongs. Thus, the forms engine can control attributes that are relevant only to institutions in a particular group.

Contact Table

The Contact Table specifies the database access privileges of people within an institution. For example, an administrator at a state university system may have access rights to data from applications to all universities within the system, whereas an administrator at a particular school may have access only to applications to that school.

Each row in the Contact Table includes a unique Contact Identifier, an Institutional Identifier, which defines the institution or group of institutions to which access is granted, and the operations which the contact is permitted. For example, a contact may be granted rights to acknowledge receipt of an application, to transfer application data using a file transfer protocol (FTP), or to receive a printable, non-editable version of completed application.

The Contact Table can also contain additional useful information, such as the e-mail address or last log-in time for the contact.

Terms Table

The Terms Table indicates the application terms that are currently available. Each row of the Terms Table includes a unique Term Identifier, a Term Key, the start and expiration dates for applications to the institution for the term, a text description of the term, and an institution-defined Term Code. The institution-defined Term Code is used when data is uploaded to the institution so that the data is seamlessly loadable into the institution's information system. The Institution-Application Table described below defines the applications available for each institution and includes a term key field that identifies the terms for which the application can be used.

Institution-Application Table

One institution, represented by a row in the Institutions Table, can own several applications, each of which is represented by a row in the Institution-Application Table. For example, an institution may have one application for freshman undergraduate students, another for transfer undergraduate students, yet another for international students, etc.

The Institution-Application Table includes one row for each application owned by an institution and relates the information in the Applications Tables to the Institution described in the Institutions Table. Each row in the Institution-Application Table includes an Application Identifier, an Institution Identifier, status of the application, type of the application, and information pertinent to the particular application (i.e., name campus, etc.). Each row also includes a Term Key, which is used with the Term Table to determine which terms are currently available for applying using the application. The Institution-Application Table can also include information about the application processing fee and how the fee is allocated between the institution and the processor.

Transaction Operations Table

Each time an applicant performs an operation, such as saving a page of information, the operation is assigned a unique Operation Identification Number and a new row is added to the Transaction Operations Table. Each row of the Transaction Operations Table includes the unique Operation Identifier, a Transaction Identifier (described below with the Transaction Table), a code indicating which operation the row represents, a contact identifier, and a time stamp indicating the date and time of the operation. Operations include, for example, save, save and send, acknowledge, secure credit card, no fee, void, and view printable application.

The Transaction Operations Table and the Transaction Table described below are used to maintain state information.

Transaction Table

A Transactions Table includes information about each user transaction, that is, each application that a user has accessed and saved. Each entry in the Transaction Table includes a unique Transaction Identifier, a User Identifier, an Application Identifier, a Term Identifier, and a code indicating the state of the application. The Transaction Identifier represents a unique combination of User Identifier, Application Identifier, and Application Term. There is exactly one row in the Transaction Table for each Transaction Identifier. The application state can be, for example, ‘in progress’, ‘submitted’, ‘payment received’, and ‘acknowledged by the institution,’ etc. Each entry also includes an order identifier, a text string that includes the User Identifier, the Application Identifier and a time stamp. The Order Identifier is used for credit card settlement and in correspondence with the institution.

When a user accesses an application, the universal forms engine looks for an existing transaction involving the user and the requested application and term. If such a transaction exists, the response of the forms engine to the user depends upon the state of the transaction. If no such transaction exist, (i.e., this is the first access to this application by the user) a new transaction is begun. An new entry is inserted in the Transaction Table. A Transaction Identifier is assigned when the user requests an explicit save operation or a “save and send” operation for the new application. A Transaction Identifier is not assigned merely on the basis of a page flip on a multipage form.

Once the user selects the “Save, Pay and Send” button, the Term, Term Identifier and Order Identifier fields are populated, and the state is set to indicated the application has been submitted. Upon payment, a Payment Operation field is populated with the Operation Identifier for the payment operation, and the state is set to indicate that payment has been received. This continues as the transaction travels through settlement, acknowledgment, etc.

Applicant Pages

Applicant pages are those presented to the applicant. These include actual application pages generated by the forms engine and displayed with labels identifying the requested information and suitable form data entry elements for applicants to input the requested information. Applications are typically composed of multiple pages.

Another applicant page shows the applicant the status of all applications the applicant has worked on. This page is produced by a CGI utility that examines the tables described above and produces an HTML page showing whether each application has been completed, saved, submitted, or paid and whether it has been acknowledged by the school.

Correction pages are presented to the applicant when first or second stage validation described below detects missing or incorrect data.

Other pages include those that inform the user when no terms are available for accepting applications (that is, the current date is outside the submission windows) or when a requested application has already been submitted for the requested term.

Data Validation

The presence and content of the information is preferably checked at the server, rather than by the browser on the applicant's computer. This reduces the requirements for the browser, so that the applicant is not restricted to using the latest version of a browser and, as less computation is performed by the browser itself, compatibility problems are reduced. An applicant can use a character based browser, such as Lynx, if he chooses. When information is recalled from the database for insertion into a new application, it is checked against the content requirements of the institution. If the recalled data does not meet the criteria, the information is requested again from the applicant.

Data validation is performed in two stages. Data is saved both before and after each stage of validation. The first stage consists of checks that are universal to all applications. These checks are done every time a page is submitted, such as when a subsequent page is requested or when a page is saved. For example, first stage validation may check that the applicant's name is present, that SAT scores are between be 200-800, and that once the non-digit characters are stripped out of social security numbers, a sequence of nine digits not beginning with “9” or “000” remains.

To avoid presenting the applicant with an overwhelming number of fields that fail validation rules at the end of the entire application, it is preferable to validate as many fields as possible in the first stage validation. On the other hand, the number of required fields is preferably minimized in the first stage, because an applicant may want to partially complete an application during one session and complete the remaining fields at another time.

Second stage validation is performed when an application is being submitted to an institution and the entire form must be complete. The second stage typically includes more required fields and more specific validation rules for submitted data fields. Second stage validation is performed on the entire data set for the application and validates the information in accordance with rules specified by the institution for the particular application. First, institution specific required fields are verified. For example, because some institutions may be willing to process an application with the field Hobbies left blank, this field is not required in first stage validation. If an institution does require this field to be complete, an incomplete field will be flagged during second stage validation. After second stage validation is successfully completed, the data is ready to be uploaded to the institution.

The Application Table indicates which fields are required for the particular application. The Application Table also indicates certain data validation rules, such as permissible values or formats for data. The second stage validation can reformat the data into a format requested by the institution. For example, some institutions want the name of the applicant in the form of a single field, with the last name first, followed by a comma and then the first name and middle initial. To avoid having applicants enter data more than once to accommodate changes in format, the information is preferably stored in simpler data elements, and then combined during second stage validation into the format requested by the institution.

Dependency rules are checked during second stage validation. For example, whether a particular field, such as Alien Registration Number, is required may depend upon the value supplied by the applicant for another field, such as Citizenship.

A user who is earnestly filling out the application with the intent to submit it, could, upon submission, be confronted with many institution-required fields on a large second stage data correction page. To minimize the size of that page, the user is given the option of having first stage validation additionally scan the current page's fields for attributes which will be required by the second stage validation process.

Initially this option is active. If the user is presented a data correction page, the top of the page has radio buttons and instructions for enabling/disabling this feature. The user's choice is maintained between pages via a hidden field in the form(s).

In this manner, as the user progresses through the application, he can enter values for second stage-required fields in a gradual manner via the first stage validation process, rather than being confronted with many fields to populate upon submission.

If the user is unable to supply a value at the time, he can disable this feature and postpone entering data into the field until he is ready to submit the application to the institution.

Attribute Aliasing

Aliasing of attributes refers to a secondary naming scheme developed to create a flexible data dictionary. By using Aliasing, an application developer can rapidly locate attributes that are defined by system, and avoid creating duplicate attributes that store the same data.

Each attribute alias is a series of descriptors delimited by colons. For example, anything relating to address information uses a descriptor of “ADDRESS”; questions relating to the applicant's birth use a descriptor of “BIRTH”.

Thus, the country of birth attribute is named “BIRTH_COUNTRY” but its alias is “BIRTH:ADDRESS:COUNTRY”. Similarly, the date of birth attribute is named “BIRTH_DATE”, and is aliased as “BIRTH:DATE”.

Permanent address attributes are named “STREET”,“STREET2”,“CITY”, “ZIP”, etc. but the aliases are “ADDRESS:PERMANENT:CITY”, “ADDRESS:PERMANENT:ZIP”, etc.

Mailing address attributes are named “MAIL_STREET”,“MAIL_STREET2”, “MAIL_CITY”, “MAIL_ZIP”, etc. but the aliases are “ADDRESS:MAIL:CITY”, “ADDRESS:MAIL:ZIP”, etc.

The use of Aliasing provides the ability to search for content by a keyword or set of keywords. For example, to find “father's home address”, one could search for all attributes whose aliases contain the descriptors “FATHER”, “ADDRESS”, and “HOME”.

This search would locate the aliases “FATHER:ADDRESS: HOME.1:STREET”, “FATHER:ADDRESS:HOME.1:CITY”, “FATHER:ADDRESS:HOME.1:COUNTRY”, “FATHER:ADDRESS:HOME.1:TELEPHONE”, which correspond to the variable names “PERSON_AT_ADDRESS_SINCE.1”, “PERSON_CITY.1”, “PERSON_COUNTRY.1”, “PERSON_PHONE.1”, respectively.

One can look at the intersection or union of keyword search results to quickly access desired attributes. Thus, the aliasing system is used primarily for developing new applications: not only as a lookup tool, but also to avoid adding as new variables attributes that already exist. Finally, aliasing ensures maximum data-sharing by weeding out duplicates that would split the data between two name spaces. It is preferable to use this system as the primary internal naming scheme.

Procedure

FIG. 16 shows the steps that occur in a preferred embodiment when an applicant contacts the forms engine. Step 156 shows that when an application contacts the URL of the forms engine, the forms engine is invoked and initializes itself by reading in libraries and initializing variables, such as global constants and data structures. For example, in the first embodiment of the Application Data File described above, an associative array of associative arrays that defines the form elements used by the engine to construct the application form is initialized.

In step 157, the forms engine looks for data posted from the Web page form. There may be no data at first, but after some information is entered and a page is saved or changed, data will post to the forms engine, which will perform first stage validation on the data. The forms engine then processes input arguments and posted data to determine the application state as described below.

Step 158 shows that the forms engine then makes database calls to initialize variables pertaining to the current admissions application (ID #, fee information, institution, etc.).

Step 159 shows that the forms engines determines which application terms (e.g. “Fall 1999”, etc.) are available for this user/application combination. For example, the user may have already submitted and paid for a “Fall 1999” application and is now requesting the same application. This request may be to 1) review the submitted application or 2) apply for a new term. The engine needs to guarantee that the user does not submit the same application more than once per term. The search engine calculates submission state information to prevent a user from changing data in an already submitted application, and then resubmitting it in the mistaken belief that the data would be updated at the institution.

There are three outcomes of the calculation of submission state:

• • a. No currently available terms. Each term has a Begin-Date and an Expiration-Date. If the current time is before the Begin-Date or after the Expiration-Date, that term is unavailable. No terms would be available if all application windows for an institution are either expired or have not yet begun, or if the user has applied to all currently available terms.
  • b. User has applied for a term, and has not yet initiated a new transaction for this application.
  • c. User has an available “Active,” that is, not submitted or paid, transaction for this application.

In step 160, the engine determines, based upon the availability of a term and the state of any pending or submitted applications, which application form is required by the user and generates the appropriate application form. If the user has an available active transaction, the engine will return the appropriate page of the application in an HTML form with any previously supplied data already filled in. If the user has already submitted the application and has no active transactions, an “Already Submitted” page is returned, with hypertext link(s) to “Printable” (uneditable) versions of the submitted application(s), and the option to fill out the application for a term other than the term(s) already applied for. If there are no available terms, a “No Available Terms” page is returned, which gives the user the option to fill out and save the application, but not submit it until a term is available. In the case that the user has previously submitted an application for the specified term and no other terms are available, a hybrid of the above two pages is returned, with links to printable version(s) of submitted application(s) and the option to fill in and save data but not submit the application until a new term is available.

In step 161, the forms engine reads and parses the “Application Data File” corresponding to the application to find the appropriate page of the application.

In step 162, the engine initializes a user data structure, preferably an associative array of key/value pairs or a data object in an Object-Oriented implementation Programming using data from the User Attribute Table.

If data has been posted, the forms engine performs first stage data validation in step 163.

If one or more data fail validation, the engine creates a “data correction page” and returns it to the user. This page repeats the text of the failed question, displays a message explaining why the data failed, and repeats the form element pertinent to that datum. When the user posts this page, first stage validation is applied to the incoming data, and if one or more are still in error, a new data correction page is returned. This process continues until all the data for that page have passed validation.

As described above, the first stage validation optionally checks for second stage required fields, thereby reducing the number of fields that will require data entry during the second stage validation. On each data correction page, the user has the option to enable/disable this feature.

In step 164, the forms engine outputs an appropriate page to the user depending upon the engine's state.

The front end, that is, the portion of the forms engine that processes incoming data from the user, is essentially one CGI program that determines the proper action by parsing information coming in from the Web form in combination with state information from the Transactions Table. For example, the user could be returning from a data correction page, the user may have hit the “save and send” button, or the user may have switched pages. The engine may look for posted data and process it, etc.

State

The forms engine can be in one of several possible states after analyzing incoming data. For example, the data may have failed validation and the forms engine, therefore, needs to output data correction page, or a user may have requested to go to page “x”, so the forms engine needs to create and output page “x”; etc. (see discussion of state, below).

Most interactions between the user and the inventive system are through “front-end processing,” which was described above with respect to FIG. 14. The response of the engine is dependent upon the current state. The Web, which is the communications conduit the system uses, is by definition stateless: When a browser (Web client) submits a request to a Web server, a connection is made between the two only long enough for the server to transmit the desired information. The server then drops the connection, and any information created by the client/server interaction is discarded by the server. The next time the client connects to the server, the slate is blank and they start that interaction from scratch.

The system needs a way to maintain state information between contacts. The system utilizes two state models to describe the states of two different aspects of the system: a “session state” applies to the front-end process of creating and returning Web forms, and a “transaction state” pertains to the state of the transaction, that is, the state for a particular user's application to an institution for a specific term. Transaction states include for example, active or submitted or paid or void.

Every page has hidden fields that provide state information. The session state can be determined by parsing the hidden fields returned with data. State information can include, for example, the version number of the application and the page that the user previously requested. For example, the hidden fields would indicate to the server whether a page is being returned because the applicant selected “Save, Pay, and Send” or whether the applicant merely requested a page flip. As another example, when first stage validation finds an error and returns a data correction page to the user, the data correction page includes hidden fields that indicate the page that the user was attempting to go to. When the data correction page is submitted, the engine parses the hidden fields to determine the state and returns the previously requested page to the user.

The current transaction state for a specific application/user combination is determined by looking up the application in the data base tables described above. For example, if the applicant requests an application for a term for which the applicant has already submitted an application, the engine determines that such is the case, and rather than returning the application, returns a page stating that the application was already submitted. The student is given the option of viewing the application in a printable, non-editable form, or of opening an application form for another term. The engine screens out the term already applied for when it returns the application. If no terms are currently available, a page is returned that states no terms are currently available, but the applicant is permitted to begin completing an application that can be saved until a term is available. In such a case, the “save and send” button is not available until a term is available. Thus, applicants can begin completing forms even before a term is available.

With regard to the front-end state model, the following is a list of the states the engine defined by the action that caused the engine to be in that state:

• 1. “Initial Contact”—The user is requesting the application form from outside of the engine. The engine will create the first page of the application, merge any matching user data, and return the form.
• 2. “Page Flip”—For multi-page applications, the user has come from page “x” and wants to go to page “y”. The engine first applies front-end validation to the incoming data posted from page “x” (which may result in returning a data correction page), saves the validated data, generates page “x”, merges any matching user data and returns the form.
• 3. “Explicit Save”—At the bottom of each page is a button that allows them to save the current page of data. Essentially, the action of the engine in this state is identical to the “page flip”, but “x” equals “y” (i.e., the returned page is the same page number as the page posted from).
• 4. “Save and Send”—The user has elected to submit the completed application to the institution. The engine does front-end validation on the current page posted, saves data, does back-end validation on all data pertaining to the application, saves data to the User Attribute Sent Table, and passes control to the payment server.
• 5. “Data CRX (Correction) Page”—When either front-end or back-end validation has failed, the engine switches to this state, which causes the form generator to create a data correction page and hide in that page state information including the state the engine was in prior to switching to this state. (For example, if the user is on page 3 and chose to go to page 5, but errant data on page 3 lead to an intervening data correction page, the data correction page includes hidden data indicating the page flip to page 5). Once the data are successfully amended and the user posts the data correction page, the engine detects that the prior state was a “page flip” to page 5, and returns page 5 to the user. Similarly, if the user had selected “save and send” and got an intervening front-end or back-end validation data correction page, once corrected the post from that data correction page will then switch the engine into “save and send” mode, and the user will receive the payment page from the payment server.
• 6. “App Terms Page”—This state is entered when the applicant requests an application that was already submitted or for which no terms are available: (a) an “already submitted” page; or (b) a “no available terms” page. The engine will return either with hidden state information. When one of these pages is posted, the engine will then continually insert additional hidden state information into subsequent forms to ensure future behavior is in accordance with selection(s) the user made on those pages.
• 7. “Print Engine”—The engine is being called in print mode to deliver a “printable” (i.e., non-form) version of the application/user data.
• 8. “Exit”—The user has chosen the ‘Finish Session’ button on the application page, and the engine passes control to the user activity CGI, which displays a page of information about the applications the user has worked on and their status.
• 9. “Search”—The user has selected a search button to aid in the selection of a value for example, a country. The engine saves any validated data and displays a search page, which contains links back to the page of the application the user left. These links also cause the selected value to be passed into the engine, which then displays it appropriately in the form.

FIG. 17 shows the back-end state model for an application, and the corresponding transaction operations that cause changes between states. Null state 172 is the state after an application has been created but before the application has been posted by the applicant. The application switches into the active state 178 when the applicant saves a page of the application or when the applicant attempts to save a page and an error prevents the page from being saved. When the application is submitted, it enters a submitted state 180. The applicant is preferably given a warning that no changes can be made to the application after payment is made and is given the option to amend the application. If the applicant indicates a desire to amend the application, or if the application fee is not paid, the application returns to active state 178. If the applicant request a fee waiver or the applicant indicates that he desires to pay by check, the application enters a hold state 182 until the check clears or the fee waiver is approved by the institution. Fee waivers are used by institutions to encourage applications from qualified individuals who may not be able to afford the application fee.

After the application is submitted, the applicant pays for the application, which enters a paid state 184 until the payment is acknowledged by the institution or settled. In the paid state 184 and subsequent states, the application can be viewed for printing by the applicant or downloaded by a batch transfer or file transfer protocol by the institution. The application is then acknowledged by the institution and the payment is settled. Depending upon whether the acknowledgment or settlement occurs first, the application enters an acknowledged state 186 or a settled-preacknowledgment state 192. After both settlement and acknowledgment occur, the application enters a completed state 190. The application can enter a void state 194 if it becomes unuseable, for example, because an applicant cancels the application or withdraws permission to provide the application information to the institution. Voided application are maintained in a separate database table.

Data Formatting

When application information is uploaded and acknowledged by the institution, the original application information remains archived in the applicant database in the User Attributes Sent table. The application can be printed, re-uploaded, etc. Institutions can request information related to all or a subset of their applications to see, for example, what new applications have been sent and the status of various applications. The data is available for data manipulation, such as for sorting on fields or presenting application information in various database views. For example, a school can look at applications sorted by test scores. The school could also look at all applications of students from a particular geographical area, or students who play a particular sport or instrument. The institution can perform statistical correlations between information on the application and grades achieved at the institution after matriculation to determine what characteristics of applicants correlate with success at the institution.

Not only are the individual data elements tailored to the specifications of a particular institution, the entire data set is formatted to conform to that institutions needs. The data formats may include 1) comma separated values, 2) tab delimited values, 3) fixed length formats, 4) name/value pairs, and 5) EDI 189. For all of these methods, of course, the data is ordered as required (e.g., Social Security number first, last name second, high school name 33rd, etc.).

The format of the entire data set is done via back-end utilities that run on the server and that utilize specially formatted text files containing data formatting descriptions and additional data-manipulation rules. These utilities are triggered when the institution's contact person accesses the administrative utility on the forms engine server and chooses to upload data sets.

Another implementation of the invention uses object-oriented programming and the Extensible Markup Language (XML), which is used to create a customized mark-up language related to applications processing. In this embodiment, most of the information about each applicant is stored in an XML file corresponding to that applicant, although some basic account information about each applicant is still maintained in a data table. Information about each application is stored in an XML application description file. This implementation requires fewer files, thereby simplifying maintenance and reducing the run time overhead associated with reading and reconstructing applications from multiple files. First and second stage validation rules are maintained in the XML application description file. Unlike the previously described embodiment, initialization is only required when the web server is started, because the application persists, along with its database connections, as long as the server is operating.

An XML parser, typically written in Perl, parses the XML application description source file and invokes programs that implement by creating and saving binary objects the features specified by the XML tags. For example, the text between a <begin page> tag and an<end page> tag is used to create a page object having attributes defined by the text between the tags. Similarly, an object corresponding to an element of a page is created based upon the text between a <begin element> tag and an<end element> tag. The created objects define the application that is presented to the applicant.

FIG. 18 shows examples of binary objects created by the XML parser and the relationships between some of the objects. For example, FIG. 18 shows, that a page object 204 can include one or more element object 206, groups objects 208, and table objects 210. An element object 206, which can be instantiated for example as a question on the application, includes a pre-text element 212 and a post-text element 214 corresponding to text associated with the question, an input field element 216, and any validation rule elements 218. Groups objects 208 may also include a pre-text element 212 and a post-text element 214, as well as element objects 206, other group objects 208, and table objects 210. Table objects 210 can include table header objects 220 and row element objects 222. Skilled programmers can write many classes to customize an application and will understand that FIG. 18 is a greatly simplified example used to demonstration the principles of the embodiment.

The group object allows multiple elements to be associated with a group and eases the implementation of an adaptive application, in which the content of application pages sent to an applicant may depend upon the applicant's answers in previous pages. Whether an element or group is displayed depends upon the value of a display attribute, which can be used to specify the conditions under which the object is displayed on the screen or in printed reports. For example, a group of questions may belong to a “non-U.S. citizen” group object. Questions belonging to the non-U.S. citizen group object may request information such as visa type, alien registration number, and country of origin. If the applicant answers that the is a U.S. citizen, elements in the “non-U.S. citizen” group are not displayed. An adaptive application would also be useful for a higher education system that includes multiple schools or campuses. A single application file could be used, with the questions presented to the applicant depending upon the particular school the applicant chooses. Using a single application greatly simplifies maintenance of the application form.

Applicant information is similarly saved in an applicant XML file. Unlike the application description XML file, the applicant file is changed as information is posted by the applicant. Thus, the applicant XML file is re-saved each time that data is posted by the applicant.

Although the present invention has been described using an embodiment that processes college admission application forms, it is not limited to that application, but is applicable to processing any form, such as employment forms and student loan forms, such as for the PLUS student loan program.

While a preferred embodiment of the present invention has been shown and described, it will be apparent to those skilled in the art that many changes and modifications may be made without departing from the invention in its broader aspects. Because the computer and computer network fields are changing rapidly, it is expected that implementation of the invention will change significantly as technology evolves. The particular programming language and the type of database can be varied depending on the preferences of the programmer. Such changes in implementation, however, do not depart from the spirit and scope of the invention. The appended claims are therefore intended to cover all such changes and modifications as fall within the true spirit and scope of the invention.

APPENDIX
<HTML>
<HEAD>
<META NAME=“GENERATOR” CONTENT=”Mozilla/4.04 [en] (Win95;
I) [Netscape] ”>
<TITLE>Lewis and Clark College for Admission for mossch,
page 1</TITLE>
</HEAD>
<BODY BGCOLOR=“#FFFFFF”>
<CENTER>
<H1>
<IMG SRC=“/logos/lewisc.gif” ></H1></CENTER>
<CENTER>
<H2>
Lewis and Clark College<BR>
Application for Admission, page 1&nbsp;<BR>
Fee: $45.00</H2></CENTER>
<FORM METHOD=“POST” ACTION=“https://www.applyweb.com/cgi-
bin/app?lewisc” ENCTYPE=“application/x-www-form-urlencoded”>
<HR>
<TABLE BORDER=0 WIDTH=“695” >
<TR>
<TD><B>Office of Admissions</B>
<BR>0615 S.W. Palatine Hill Road
<BR>Portland, Oregon 97219-7899
<BR>Phone: 503-768-7040</TD>
<TD VALIGN=TOP>Toll-Free: 800-444-4111
<BR>Fax: 503-768-7055
<BR>Internet: admissions@lclark.edu
<BR>World Wide Web: http://www.lclark.edu</TD>
</TR>
</TABLE>
<HR>
<TABLE BORDER=0 WIDTH=“610” >
<TR>
<TD><B>Admissions plan:</B>&nbsp;
<BR><INPUT TYPE=RADIO NAME=“LEWISC-ADMISSION” VALUE=“Early
Decision (binding)” ><NOBR>Early
Decision (binding)</NOBR>&nbsp;
<BR><INPUT TYPE=RADIO NAME=“LEWISC-ADMISSION” VALUE=“Early
Action (nonbinding)” ><NOBR>Early
Action (nonbinding)</NOBR>&nbsp;
<BR><INPUT TYPE=RADIO NAME=“LEWISC-ADMISSION” VALUE=“Regular
Decision” ><NOBR>Regular
Decision</NOBR>&nbsp;</TD>
<TD VALIGN=TOP><B>Applicant status:</B>&nbsp;
<BR><INPUT TYPE=RADIO NAME=“LEWISC-APPLICANT_STAT”
VALUE=“First-year student” ><NOBR>First-year
student</NOBR>&nbsp;
<BR><INPUT TYPE=RADIO NAME=“LEWISC-APPLICANT_STAT”
VALUE=“Transfer student” ><NOBR>Transfer-
student</NOBR>&nbsp;
<BR>Portfolio Path?&nbsp;<INPUT TYPE=RADIO NAME=“LEWISC-
PORTFOLIO” VALUE=“Y” ><NOBR>Yes</NOBR>&nbsp;<INPUT
TYPE=RADIO NAME=“LEWISC-PORTFOLIO” VALUE=“N”
><NOBR>No</NOBR>&nbsp;</TD>
</TR>
</TABLE>
&nbsp;
<TABLE BORDER=0 WIDTH=“500” >
<TR>
<TD><B>Entry date:</B>&nbsp;<SELECT NAME=“LEWISC-APP_TERM”
SIZE=1 ><OPTION VALUE=“” >&nbsp;<OPTION VALUE=Fall 1998”
SELECTED >Fall
1998&nbsp;<OPTION VALUE=“Spring 1998” >Spring
1998&nbsp;</SELECT></TD>
<TD VALIGN=TOP><B>Residence plans:</B>&nbsp;
<BR><INPUT TYPE=RADIO NAME=“LEWISC-RESIDENCE”
VALUE=“Residence hall” ><NOBR>Residence
hall</NOBR>&nbsp;
<BR><INPUT TYPE=RADIO NAME=“LEWISC-RESIDENCE”
VALUE=“Commuting student” ><NOBR>Commuting
student</NOBR>&nbsp;</TD>
</TR>
</TABLE>
<HR><B><FONT SIZE=+2>Personal</FONT></B>
<BR><I>Last/Family Name:</I> <B><FONT
SIZE=+2>Scheinberg</FONT></B>&nbsp;<INPUT TYPE=HIDDEN
NAME=“NAME_LAST” VALUE=“Scheinberg”><IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” >&nbsp;<IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” >
<I>First:</I> <B><FONT
SIZE=+2>Michael</FONT></B>&nbsp;<INPUT TYPE=HIDDEN
NAME=“NAME_FIRST” VALUE=“Michael”>
<BR>Middle:&nbsp;<INPUT TYPE=“text” NAME=“NAME_MIDDLE”
VALUE=“” SIZE=12 MAXLENGTH=25><IMG SRC=“/images/spacer.gif”
ALT=“” ><IMG SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” >&nbsp;<IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” >&nbsp;<SELECT
NAME=“NAME_SUFFIX” SIZE=1
><OPTION><OPTION>Jr.&nbsp;<OPTION>Sr.&nbsp;<OPTION>II&nbsp;
OPTION>III&nbsp;<OPTION>IV&nbsp;</SELECT><IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” >&nbsp;<IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” >&nbsp;<IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” >&nbsp;<IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” >&nbsp;<IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” >&nbsp;<IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” >&nbsp;<IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” >&nbsp;<IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” >&nbsp;<IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” >&nbsp;<IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” >&nbsp;<IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” >&nbsp;<IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” >&nbsp;<IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” >&nbsp;<IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” >&nbsp;<IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” >&nbsp;<IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” >&nbsp;<IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” >&nbsp;<IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” >&nbsp;<IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” >&nbsp;<IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” >&nbsp;<IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” >&nbsp;<IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” >&nbsp;<IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” >&nbsp;<IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” >&nbsp;<IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” >&nbsp;<IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” >
Gender:&nbsp;<INPUT TYPE=RADIO NAME=“GENDER” VALUE=“M”
><NOBR>Male</NOBR>&nbsp;<INPUT TYPE=RADIO NAME=“GENDER”
VALUE=“F” ><NOBR>Female</NOBR>
<BR>Preferred name or nickname:&nbsp;<INPUT TYPE=“text”
NAME=“NAME_PREFER” VALUE=“” SIZE=12 MAXLENGTH=45><IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” >&nbsp;<IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” >
Former last name(s), if any&nbsp;<INPUT TYPE=“text”
NAME=“NAME_OTHER_LAST” VALUE=“” SIZE=12 MAXLENGTH=40>
<P>Permanent address:
<BR>Street:&nbsp;<INPUT TYPE=“text” NAME=“STREET” VALUE=“”
SIZE=20 MAXLENGTH=40>Box/Apt:&nbsp;<INPUT TYPE=“text”
NAME=“STREET2” VALUE=“” SIZE=10 MAXLENGTH=25>
<BR>City:&nbsp;<INPUT TYPE=“text” NAME=“CITY” VALUE=“”
SIZE=20 MAXLENGTH=35><IMG SRC=“/images/spacer.gif” ALT=“”
><IMG SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” >&nbsp;<IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” >
State/Province:&nbsp;<SELECT NAME=“STATE” SIZE=1 ><OPTION
VALUE=“” >&nbsp;<OPTION VALUE=“AL” >Alabama&nbsp;<OPTION
VALUE=“AK” >Alaska&nbsp;<OPTION VALUE=“AZ”
>Arizona&nbsp;<OPTION VALUE=“AR” >Arkansas&nbsp;<OPTION
VALUE=“CA” >California&nbsp;<OPTION VALUE=“CO”
>Colorado&nbsp;<OPTION VALUE=“CT” >Connecticut&nbsp;<OPTION
VALUE=“DE” >Delaware&nbsp;<OPTION VALUE=“DC” >District
of Columbia&nbsp;<OPTION VALUE=“FL” >Florida&nbsp;<OPTION
VALUE=“GA” >Georgia&nbsp;<OPTION VALUE=“HI”
>Hawaii&nbsp;<OPTION VALUE=“ID” >Idaho&nbsp;<OPTION
VALUE=“IL” >Illinois&nbsp;<OPTION VALUE=“IN”
>Indiana&nbsp;<OPTION VALUE=“IA” >Iowa&nbsp;<OPTION
VALUE=“KS” >Kansas&nbsp;<OPTION VALUE=“KY”
>Kentucky&nbsp;<OPTION VALUE=“LA” >Louisiana&nbsp;<OPTION
VALUE=“ME” >Maine&nbsp;<OPTION VALUE=“MD”
>Maryland&nbsp;<OPTION VALUE=“MA”
>Massachusetts&nbsp;<OPTION VALUE=“MI”
>Michigan&nbsp;<OPTION VALUE=“MN” >Minnesota&nbsp;<OPTION
VALUE=“MS” >Mississippi&nbsp;<OPTION VALUE=“MO”
>Missouri&nbsp;<OPTION VALUE=“MT” >Montana&nbsp;<OPTION
VALUE=“NE” >Nebraska&nbsp;<OPTION VALUE=“NV”
>Nevada&nbsp;<OPTION VALUE=“NH” >New
Hampshire&nbsp;<OPTION VALUE=“NJ” >New Jersey&nbsp;<OPTION
VALUE=“NM” >New
Mexico&nbsp;<OPTION VALUE=“NY” >New York&nbsp;<OPTION
VALUE=“NC” >North
Carolina&nbsp;<OPTION VALUE=“ND” >North Dakota&nbsp;<OPTION
VALUE=“OH” >Ohio&nbsp;<OPTION VALUE=“OK”
>Oklahoma&nbsp;<OPTION VALUE=“OR” >Oregon&nbsp;<OPTION
VALUE=“PA” >Pennsylvania&nbsp;<OPTION VALUE=“RI” >Rhode
Island&nbsp;<OPTION VALUE=“SC” >South Carolina&nbsp;<OPTION
VALUE=“SD” >South
Dakota&nbsp;<OPTION VALUE=“TN” >Tennessee&nbsp;<OPTION
VALUE=“TX” >Texas&nbsp;<OPTION VALUE=“UT”
>Utah&nbsp;<OPTION VALUE=“VT” >Vermont&nbsp;<OPTION
VALUE=“VA” >Virginia&nbsp;<OPTION VALUE=“WA”
>Washington&nbsp;<OPTION VALUE=“WV” >West
Virginia&nbsp;<OPTION VALUE=“WI” >Wisconsin&nbsp;<OPTION
VALUE=“WY” >Wyoming&nbsp;<OPTION VALUE=“AB”
>Alberta&nbsp;<OPTION VALUE=“BC” >British
Columbia&nbsp;<OPTION VALUE=“MB” >Manitoba&nbsp;<OPTION
VALUE=“NB” New
Brunswick&nbsp;<OPTION VALUE=“NF”
>Newfoundland&nbsp;<OPTION VALUE=“NS” >Nova
Scotia&nbsp;<OPTION VALUE=“NT” >Northwest
Territories&nbsp;<OPTION VALUE=“ON” >Ontario&nbsp;<OPTION
VALUE=“PE” >Prince
Edward Island&nbsp;<OPTION VALUE=“QB” >Quebec&nbsp;<OPTION
VALUE=“SK” >Saskatchewan&nbsp;<OPTION VALUE=“YT” >Yukon
Territories&nbsp;</SELECT>
<BR>Zip/Postal Code:&nbsp;<INPUT TYPE=“text” NAME=“ZIP”
VALUE=“” SIZE=10 MAXLENGTH=10><IMG SRC=“/images/spacer.gif”
ALT=“” ><IMG SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” >&nbsp;<IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” >
Current telephone <FONT SIZE=−1>(area
code) +number</FONT>&nbsp;<INPUT TYPE=“text” NAME=“PHONE”
VALUE=“503-224-0115” SIZE=12 MAXLENGTH=17>
<BR>E-mail address:&nbsp;<INPUT TYPE=“text” NAME=“EMAIL”
VALUE=“mos@hevanet.com” SIZE=20 MAXLENGTH=40><IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” >&nbsp;<IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” >
Fax #:&nbsp;<INPUT TYPE=“text” NAME=“FAX” VALUE=“” SIZE=12
MAXLENGTH=17>
<P>If different from above, please give your mailing address
for all admissions
correspondence:
<BR>Street:&nbsp;<INPUT TYPE=“text” NAME=“MAIL_STREET”
VALUE=“” SIZE=20 MAXLENGTH=35>BOX/Apt:&nbsp;<INPUT
TYPE=“text” NAME=“MAIL_STREET2” VALUE=“” SIZE=10
MAXLENGTH=45>
<BR>City:&nbsp;<INPUT TYPE=“text” NAME=“MAIL_CITY” VALUE=“”
SIZE=20 MAXLENGTH=35><IMG SRC=“/images/spacer.gif” ALT=“”
><IMG SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” >&nbsp;<IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” >
State/Province:&nbsp;<SELECT NAME=“MAIL_STATE” SIZE=1
><OPTION VALUE=“” >&nbsp;<OPTION VALUE=“AL”
>Alabama&nbsp;<OPTION VALUE“=AK” >Alaska&nbsp;<OPTION
VALUE=“AZ” >Arizona&nbsp;<OPTION VALUE=“AR”
>Arkansas&nbsp;<OPTION VALUE=“CA” >California&nbsp;<OPTION
VALUE=“CO” >Colorado&nbsp;<OPTION VALUE=“CT”
>Connecticut&nbsp;<OPTION VALUE=“DE” >Delaware&nbsp;<OPTION
VALUE=“DC” >District
of Columbia&nbsp;<OPTION VALUE=“FL” >Florida&nbsp;<OPTION
VALUE=“GA” >Georgia&nbsp;<OPTION VALUE=“HI”
>Hawaii&nbsp;<OPTION VALUE=“ID” >Idaho&nbsp;<OPTION
VALUE=“IL” >Illinois&nbsp;<OPTION VALUE=“IN”
>Indiana&nbsp;<OPTION VALUE=“IA” >Iowa&nbsp;<OPTION
VALUE=“KS” >Kansas&nbsp;<OPTION VALUE=“KY”
>Kentucky&nbsp;<OPTION VALUE=“LA” >Louisiana&nbsp;<OPTION
VALUE=“ME” >Maine&nbsp;<OPTION VALUE=“MD”
>Maryland&nbsp;<OPTION VALUE=“MA”
>Massachusetts&nbsp;<OPTION VALUE=“MI”
>Michigan&nbsp;<OPTION VALUE=“MN” >Minnesota&nbsp;<OPTION
VALUE=“MS” >Mississippi&nbsp;<OPTION VALUE=“MO”
>Missouri&nbsp;<OPTION VALUE=“MT” >Montana&nbsp;<OPTION
VALUE=“NE” >Nebraska&nbsp;<OPTION VALUE=“NV”
>Nevada&nbsp;<OPTION VALUE=“NH” >New
Hampshire&nbsp;<OPTION VALUE=“NJ” >New Jersey&nbsp;<OPTION
VALUE=“NM” >New
Mexico&nbsp;<OPTION VALUE=“NY” >New York&nbsp;<OPTION
VALUE=“NC” >North
Carolina&nbsp;<OPTION VALUE=“ND” >North Dakota&nbsp;<OPTION
VALUE=“OH” >Ohio&nbsp;<OPTION VALUE=“OK”
>Oklahoma&nbsp;<OPTION VALUE=“OR” >Oregon&nbsp;<OPTION
VALUE=“PA” >Pennsylvania&nbsp;<OPTION VALUE=“RI” >Rhode
Island&nbsp;<OPTION VALUE=“SC” >South Carolina&nbsp;<OPTION
VALUE=“SD” >South
Dakota&nbsp;<OPTION VALUE=“TN” >Tennessee&nbsp;<OPTION
VALUE=“TX” >Texas&nbsp;<OPTION VALUE=“UT”
>Utah&nbsp;<OPTION VALUE=“VT” >Vermont&nbsp;<OPTION
VALUE=“VA” >Virginia&nbsp;<OPTION VALUE=“WA”
>Washington&nbsp;<OPTION VALUE=“WV” >West
Virginia&nbsp;<OPTION VALUE=“WI” >Wisconsin&nbsp;<OPTION
VALUE=“WY” >Wyoming&nbsp;<OPTION VALUE=“AB”
>Alberta&nbsp;<OPTION VALUE=“BC” >British
Columbia&nbsp;<OPTION VALUE=“MB” >Manitoba&nbsp;<OPTION
VALUE=“NB” >New
Brunswick&nbsp;<OPTION VALUE=“NF”
>Newfoundland&nbsp;<OPTION VALUE=“NS” >Nova
Scotia&nbsp;<OPTION VALUE=“NT” >Northwest
Territories&nbsp;<OPTION VALUE=“ON” >Ontario&nbsp;<OPTION
VALUE=“PE” >Prince
Edward Island&nbsp;<OPTION VALUE=“QB” >Quebec&nbsp;<OPTION
VALUE=“SK” >Saskatchewan&nbsp;<OPTION VALUE=“YT” >Yukon
Territories&nbsp;</SELECT>
<BR>Zip/Postal code:&nbsp;<INPUT TYPE=“text” NAME=“MAIL_ZIP”
VALUE=“” SIZE=10 MAXLENGTH=12><IMG SRC=“/images/spacer.gif”
ALT=“” ><IMG SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” >&nbsp;<IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” >
Phone at mailing address:&nbsp;<INPUT TYPE=“text”
NAME=“MAIL_PHONE” VALUE=“” SIZE=12 MAXLENGTH=17>
<BR>Social Security #:&nbsp;<INPUT TYPE=“text” NAME=“SS_NUM”
VALUE=“” SIZE=11 MAXLENGTH=11><IMG SRC=“/images/spacer.gif”
ALT=“” ><IMG SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” >&nbsp;<IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” >
Date of birth (MMDDYY) :&nbsp;<INPUT TYPE=“text”
NAME=“mdy1_BIRTH_DATE” VALUE=“” SIZE=2 MAXLENGTH=2><INPUT
TYPE=“text” NAME=“mdy2_BIRTH_DATE” VALUE“” SIZE=2
MAXLENGTH=2><INPUT TYPE=“text” NAME=“mdy3_BIRTH_DATE”
VALUE=“” SIZE=4 MAXLENGTH=4>
<P>What country are you a citizen of? (<A
HREF=“/country.html” TARGET=“ResourceWindow”>view
codes</A>) &nbsp;<INPUT TYPE=“text” NAME=“CITIZEN_COUNTRY”
VALUE=“” SIZE=2 MAXLENGTH=2>
<BR>Religious affiliation (optional)&nbsp;<INPUT TYPE=“text”
NAME=“RELIGION” VALUE=“” SIZE=30 MAXLENGTH=40>
<BR>If not a U.S. citizen, are you a Permanent
Resident?&nbsp;<INPUT TYPE=RADIO NAME=“RESIDENT_ALIEN_YN”
VALUE=“Y” >Yes&nbsp;<INPUT TYPE=radio
NAME=“RESIDENT_ALIEN_YN” VALUE=“N” >No&nbsp;<IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” >&nbsp;<IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” >&nbsp;<IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” >&nbsp;<IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” >
Visa type&nbsp;<INPUT TYPE=“text” NAME=“VISA_TYPE” VALUE=“”
SIZE=12 MAXLENGTH=40>
<BR>Have you previously applied to Lewis &amp;
Clark?&nbsp;<INPUT TYPE=RADIO NAME=“LEWISC-APP_BEFORE”
VALUE=“Y” ><NOBR>Yes</NOBR>&nbsp;<INPUT TYPE=RADIO
NAME=“LEWISC-APP_BEFORE” VALUE=“N” ><NOBR>No</NOBR>
<BR>If yes, for which term/year?&nbsp;<INPUT TYPE=“text”
NAME=“LEWISC-APPLY_YN” VALUE=“” SIZE=5 MAXLENGTH=10>
<BR>Will you be a candidate for need-based financial
aid?&nbsp;<INPUT TYPE=RADIO NAME=“LEWISC-FIN_AID” VALUE=“Y”
><NOBR>Yes</NOBR>&nbsp;<INPUT TYPE=RADIO NAME=“LEWISC-
FIN_AID” VALUE=“N” ><NOBR>No</NOBR>
<BR>(Financial aid is not a factor in the admission decision
process. Indicating
“yes” will allow us to send the required IDF packet.)
<P>If yes, FASFA and IDF forms were/will be filed
on:&nbsp;<INPUT TYPE=“text” NAME=“mdy1_LEWISC-FASFA_FORM”
VALUE=“” SIZE=2 MAXLENGTH=2><INPUT TYPE=“text”
NAME=“mdy2_LEWISC-FASFA_FORM” VALUE=“” SIZE=2
MAXLENGTH=2><INPUT TYPE=“text” NAME=“mdy3_LEWISC-
FASFA_FORM” VALUE=“” SIZE=4 MAXLENGTH=4>
<BR>(See application instructions for important deadline
information.)
<BR>Name of your current school:&nbsp;<INPUT TYPE=“text”
NAME=“CURRENT_SCHOOL_NAME” VALUE=“” SIZE=30 MAXLENGTH=50>
<BR>Type of school:&nbsp;<SELECT NAME=“HS_TYPE.1” SIZE=1
><OPTION><OPTION>Public&nbsp;<OPTION>Private&nbsp;<OPTION>Pa
rochial&nbsp;</SELECT>
<P><B>For first-year students only:</B>
<BR>Name of high school counselor:&nbsp;<INPUT TYPE=“text”
NAME=“HS_COUNSELOR” VALUE=“” SIZE=40 MAXLENGTH=80>
<BR>Office telephone:&nbsp;<INPUT TYPE=“text”
NAME=“PERSON_PHONE.45” VALUE=“” SIZE=12 MAXLENGTH=17><IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” >&nbsp;<IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” >
School Fax #:&nbsp;<INPUT TYPE=“text” NAME=“HS_FAX.1”
VALUE=“” SIZE=12 MAXLENGTH=12>
<BR>High School CEEB code number:&nbsp;<INPUT TYPE=“text”
NAME=“HS_CEEB.1” VALUE=“” SIZE=6 MAXLENGTH=6>
<P><B>If you're not currently attending school</B>, please
tell us what
you're doing.
<CENTER><TEXTAREA NAME=“ESSAY_NO_SCHOOL” ROWS=40 COLS=60
WRAP=virtual></TEXTAREA></CENTER>
&nbsp;
<P>Please list any relatives who may have attended Lewis
&amp; Clark, give
their name, relationship, class (if known).
<CENTER><TEXTAREA NAME=“LEWISC-STATEMENT_FAMILY_ATTEND2”
ROWS=2 COLS=60 WRAP=virtual></TEXTAREA></CENTER>
&nbsp;
<P>What influenced you to apply to Lewis &amp; Clark?
<CENTER><TEXTAREA NAME=“LEWISC-STATEMENT_INFLUENCE” ROWS=5
COLS=60 WRAP=virtual></TEXTAREA></CENTER>
<P>Have you ever visited the Lewis &amp; Clark
campus?&nbsp;<INPUT TYPE=RADIO NAME=“LEWISC-VISIT” VALUE=“Y”
><NOBR>Yes</NOBR>&nbsp;<INPUT TYPE=RADIO NAME=“LEWISC-VISIT”
VALUE=“N” ><NOBR>No</NOBR>&nbsp;<IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” >&nbsp;<IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” ><IMG
SRC=“/images/spacer.gif” ALT=“” >
If yes, when? (MMDDYY) &nbsp;<INPUT TYPE=“text”
NAME=“mdy1_LEWISC-VISIT_WHEN” VALUE=“” SIZE=2
MAXLENGTH=2><INPUT TYPE=“text” NAME=“mdy2_LEWISC-
VISIT_WHEN” VALUE=“” SIZE=2 MAXLENGTH=2><INPUT TYPE=“text”
NAME=“mdy3_LEWISC-VISIT_WHEN” VALUE=“” SIZE=4
MAXLENGTH=4><INPUT TYPE=“HIDDEN” NAME=“POSTING_PAGE”
VALUE=“1”><INPUT TYPE=“HIDDEN” NAME=“SCHOOL_CAMPUS”
VALUE=“Portland,OR”><INPUT TYPE=“HIDDEN” NAME=“LEWISC-FEE”
VALUE=“38.25”><INPUT TYPE=“HIDDEN” NAME=“LEWISC-CHG”
VALUE=“6.75”><INPUT TYPE=“HIDDEN” NAME=“SCHOOL” VALUE=“Lewis
and Clark College”><INPUT TYPE=“HIDDEN” NAME=“DOCTYPE”
VALUE=“Lewis and Clark College for Admission”><INPUT
TYPE=“HIDDEN” NAME=“SCHOOL_ABBREV” VALUE=“LEWISC”><INPUT
TYPE=“HIDDEN” NAME=“LEWISC-VERSION” VALUE=“” ><INPUT
TYPE=“HIDDEN” NAME=“IGNORE_REQ” VALUE=“1”><INPUT
TYPE=“HIDDEN” NAME=“AWVERSION” VALUE=“1.37”>
<TABLE BORDER=2 WIDTH=“100%” >
<TR>
<TD>
<CENTER>Save and go to page:&nbsp;<INPUT TYPE=“SUBMIT”
NAME=“GOTOPG” VALUE=“2”><INPUT TYPE=“SUBMIT” NAME=“GOTOPG”
VALUE=“3” ><INPUT TYPE=“SUBMIT” NAME=“GOTOPG”
VALUE=“4”></CENTER>
</TD>
<TD>
<CENTER><B>Page 1</B>&nbsp;</CENTER>
</TD>
<TD>
<CENTER><INPUT TYPE=“SUBMIT” NAME=“PGSAVE” VALUE=“Save This
Page”></CENTER>
</TD>
</TR>
</TABLE>
</FORM>
</BODY>
</HTML>

Claims

1. A method of further processing over a computer network forms directed by multiple public forms users to multiple institutions of higher education, the forms being processed by a third party forms servicer that is neither one of the institutions of higher education nor one of the public forms users, the method comprising: presenting to a form user over a computer network by a third party forms servicer in response to a request from the form user, a form directed to one of the multiple institutions of higher education, the form being generated by a forms generator that generates multiple forms corresponding to multiple institutions of higher education, the forms including fields for the forms users to enter user information;receiving by the third party forms servicer over the computer network user information and electronic payment information entered by the user;processing by the third party forms servicer an electronic payment associated with the form, the processed payment being from the user to the one of the multiple institutions to which the form is directed;storing by the third party forms servicer at least some of the user information entered on the form; andmaintaining by the third party forms servicer a transaction state for the form so as to prevent duplicate submission or payment,causing the form to enter a first state after the form user submits payment information and before the payment is settled; andtransmitting the completed form to the form user to view after causing the form to enter the first state.

2. A method of processing over a computer network forms directed by multiple public forms users to multiple institutions of higher education, the forms being processed by a third party forms servicer that is neither one of the institutions of higher education nor one of the public forms users, the method comprising, presenting to a form user over a computer network by a third party forms servicer in response to a request from the form user, a form directed to one of the multiple institutions of higher education, the form being generated by a forms generator that generates multiple forms corresponding to multiple institutions of higher education, the forms including fields for the forms users to enter user information;receiving by the third party forms servicer over the computer network user information and electronic payment information entered by the user;processing by the third party forms servicer an electronic payment associated with the form, the processed payment being from the user to the one of the multiple institutions to which the form is directed;storing by the third party forms servicer at least some of the user information entered on the form;maintaining by the third party forms servicer a transaction state for the form so as to prevent duplicate submission or payment; andif the form indicates that the form user is paying by check or is requesting a fee waver, causing the form to enter a hold state until the check is received or the fee waiver is approved.

3. The method of claim 2 further comprising causing the form to enter a first state after the form user submits payment information and before the payment is settle.

4. The method of claim 3 or 1 further comprising causing the form to enter a second state after the payment is settled.

5. The method of claim 3 or 1 in which causing the form to enter the first state prevents the form user from making further changes to the form.

6. The method of claim 3 or 1 in which the form enters a paid state after payment is submitted and before the payment is acknowledge by the institution or settled, and the form then enters a completed state when the form is acknowledged by the institution and the payment is settled.

7. The method of claim 3 or 1 in which if the form is not settled, the form returns to an active state.

8. The method of claim 2 or 1 further comprising: presenting over a computer network by the third party forms servicer in response to a request from the form user, a second form directed to one of the multiple institutions of higher education; andautomatically inserting into the second form user information previously entered onto a form by the form user.

9. The method of claim 2 or 1 in which presenting to a form user over a computer network by a third party forms servicer in response to a request from the form user a form directed to one of the multiple institutions of higher education includes presenting a form including multiple pages.

10. The method of claim 9 further comprising verifying in accordance with validation criteria user information on each of the multiple pages as they are posted by the form user.

11. The method of claim 10 in which verifying in accordance with validation criteria user information on each of the multiple pages as they are posted includes verifying the user information at a client computer or at a server computer.

12. The method of claim 10 in which the validation criteria are specified by the institution to which the form is directed.

13. The method of claim 10 further comprising verifying in accordance with first validation criteria user information on each of the multiple pages as they are posted and verifying in accordance with second validation criteria user information when a completed form is submitted.

14. The method of claim 13 in which verifying user information in accordance with first validation criteria includes verifying user information at a client computer and in which verifying user information in accordance with second validation criteria includes verifying user information at a server computer.

15. The method of claim 2 or 1 in which receiving electronic payment information includes receiving electronic payment information entered onto the form.

16. The method of claim 2 or 1 in which maintaining a transaction state includes maintaining a transaction state using at least one hidden field in a page of the form.

17. The method of claim 16 further comprising determining whether a payment has been submitted by parsing a hidden field on the page of the form.

18. The method of claim 2 or 1 in which the maintaining a transaction state includes maintaining the form within one state selected from a set of states, the set of states including an active state, a submitted state, and a paid state.

19. The method of claim 2 or 1 in which presenting a form to a form user over a computer network includes presenting a form using a stateless communications conduit.

20. The method of claim 19 in which the stateless communication conduit includes the World Wide Web.

21. The method of claim 2 or 1 in which the state of the form is maintained in a database table.

22. A computer system, comprising: a processor for carrying out computer instructions;a computer readable m emory storing instructions for performing the steps of claim 2 or 1.