US20140164163A1

US20140164163A1 - Importable template

Info

Publication number: US20140164163A1
Application number: US14/020,437
Authority: US
Inventors: Anthony F. Bernard; Timothy P. Choate; Godwin Gonsalvez; Dejan Sundeic
Original assignee: Ariba Inc
Current assignee: Ariba Inc
Priority date: 2002-07-31
Filing date: 2013-09-06
Publication date: 2014-06-12
Also published as: AU2003257076A8; WO2004012081A2; WO2004012081A3; US8554650B1; AU2003257076A1; WO2004012081A9

Abstract

An importable electronic template and methods of creating and utilizing the importable template. The template includes an alphanumeric field created by a template creation entity and a response field created by the template creation entity. Data is electronically entered into the response field by a responding entity. The importable electronic template is incorporated into a general purpose electronic template.

Description

FIELD OF THE INVENTION

The present invention is directed to a template and, in particular, a template that may be locked so that it cannot be altered and imported into a template having elements in addition to the imported template.

BACKGROUND OF THE INVENTION

In using a computer system, data may be entered into spreadsheets, or templates, using a variety of different computer programs. These templates may have two different types of data. First, the templates may receive data that is entered by a party and becomes integrated with that template so that whenever a user accesses the template, the data will be provided. This data may also be locked, or remain permanent, such that a user may not be able to change any of the data.
Second, the template may receive data that is entered by a user, but does not remain with the template. Rather, the user must re-enter or enter new data each time the user accesses the template.
It is believed that, presently, template building software is object based, which implies that the user would create many small templates and piece them together to create an overall template. This software is database centric, where all properties of the templates are stored in a database. It is believed that the algorithms and reliance on computer hardware make its solution unable to scale. Thus, there is a need to develop a system that has less reliance on computer hardware and different algorithms.

SUMMARY OF THE INVENTION

The invention is directed to an importable electronic template executable by a processor. The template includes an alphanumeric field created by a template creation entity and a response field created by the template creation entity. Data is electronically entered into the response field by a responding entity. The importable electronic template is incorporated into a general purpose electronic template by including a reference to the general purpose electronic template in the general purpose electronic template.
The invention also provides a method of creating a general purpose electronic template that includes an importable electronic template, wherein the importable electronic template has a text field and a response field. The method includes inserting a reference to the importable electronic template into a code that creates the general purpose template when executed by a processor, retrieving the locked importable template, and displaying the locked importable template as a portion of the general purpose template.
Accordingly, the invention provides solutions to the shortcomings of prior templates. The templates of the present invention beneficially minimize the time required to create templates because many locked templates can be used to create a general purpose template. The templates of the present invention also beneficially enable searching data across multiple templates related to a standardized portion of a template.
Those of ordinary skill in the art will readily appreciate, therefore, that those and other details, features, and advantages will become further apparent in the following detailed description of the preferred embodiments.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, wherein like reference numerals are employed to designate like parts or steps, are included to provide a further understanding of the invention, are incorporated in and constitute a part of this specification, and illustrate embodiments of the invention that together with the description serve to explain the principles of the invention.

In the drawings:

FIG. 1 is a schematic illustration of entities involved in an embodiment of an auction;

FIG. 2 is a schematic illustration of an embodiment of an auction network;

FIG. 3 is one embodiment of a sample general purpose template with an incorporated importable template;

FIG. 4 is one embodiment of a sample importable template.

FIG. 5 is a flow diagram of creation, use and modification of a locked importable template;

FIG. 6 is a sample template creation screen display used to practice an embodiment of the invention;

FIG. 7 is a sample template editing screen display that may be used to practice the embodiment of the invention of FIG. 6; and

FIG. 8 is another sample template editing screen display.

DETAILED DESCRIPTION

Reference will now be made in detail to the preferred embodiments of the present invention, examples of which are illustrated in the accompanying drawings. It is to be understood that the Figures and descriptions of the present invention included herein illustrate and describe elements that are of particular relevance to the present invention, while eliminating, for purposes of clarity, other elements found in typical computer networks.
Any reference in the specification to “one embodiment” or “an embodiment” means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment of the invention. The appearances of phrases such as “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment.
Templates, in the present invention, refer to electronic forms having elements, such as comments and questions, which may be in fields, as well as blank response fields, and are created by a template creator. The electronic templates are saved in a memory device and may be accessed by responding entities. The responding entities reference the instructions, comments, and questions and provide appropriate responses in the response fields.
Such templates are useful in many applications including, for example, purchaser sponsored or reverse electronic auctions. For example, electronic auctions, as developed by the Assignee of the present invention, are described in U.S. Pat. No. 6,230,146, issued on May 8, 2001, which is hereby expressly incorporated in its entirety by reference. As shown in FIG. 1, in a purchaser sponsored auction, a purchaser, or sponsor, 10 desires to purchase goods and/or services from one or more suppliers 12, 14 and 16 who bid seeking a contract award to provide those goods and/or services. Typically, the purchaser will award a contract to the lowest bidding qualified suppliers 12, 14 and 16. Templates are useful in qualifying suppliers to participate in the auction.
The purchaser sponsor 10 in such a purchaser sponsored auction often compiles a list of qualification requirements prior to the auction. Those qualifications may include specifications for the type and quality of goods to be provided, logistical requirements, and delivery schedule requirements. These requirements may be placed in a template with fields included where responses from potential bidders are to be provided. Information to be inputted into the fields might include, for example, binary confirmation that the potential bidders 12, 14 and 16 are capable of meeting a requirement, numeric information, such as a delivery date, and textual information, such as a location of a factory where the potential bidder will manufacture the desired goods.
The template may then be stored at a location in a memory device that is accessible to potential bidders 12, 14 and 16. For example, in an auction network 70, which contains a client access network 71, communication network 73, and data processing network 76, as shown in FIG. 2, the template may be created by a sponsor 10 at the production server 77 or training and reporting server 80 and stored in the production database 84 or the reporting and training database 86. That memory location may, furthermore, be protected by, for example, a password so that only selected potential bidders 12, 14 and 16 are permitted to access the template. The directory, login and reporting servers 90 may act as a portal for access to the auction network 70 and any templates.
Potential bidders 12, 14 and 16 are then invited to access and respond to the templates. Those potential bidders 12, 14 and 16 may, for example, utilize a client machine 72 to access the template through the primary communications servers 74 or secondary communications servers 75. While there are many other uses for the templates of the present invention, the supplier/bidder scenario is utilized as the scenario in which the template of the present invention is utilized in the examples provided herein.
Qualified bidders 12-16 are notified (i.e., via an e-mail) of the start and finish times for the auction. However, the auction may terminate earlier than its intended finish time if, for example, the sponsor 10 so instructs or if the auction coordinator 20 notices illegal actions or irregularities from one or more bidders during the auction. A bidder may be disqualified for any irregularities and blocked from participating in the current as well as future auctions. In that case, the auction may continue, but without the disqualified bidder. On the other hand, an auction may be extended beyond its scheduled finish time if, for example, a bidder has requested such an extension or to accommodate bids received after the official finish time for the auction.
Once the auction commences, each bidder 12-16 may place as many bids as the bidder desires for the price and non-price bid parameters. A client module of communication software on a bidder's computer terminal may provide the necessary communication tool for the bidder to transmit its bids to the bid servers 77, 80. In one embodiment, the bidder may be required to access a pre-designated web site where an auction data entry form or web page may be presented to the bidder to enter that bidder's bid data therein. Alternatively, the data entry form or page may be included as part of the client module of the communication software and may be locally displayed on the bidder's computer terminal without requiring the bidder to access a remote web site. The data entry form displays fields for price and non-price bid parameters where the bidder can enter the bidder's bid using a data entry device such as, for example, a computer keyboard. The production servers 77 receive the bids placed by the bidders 12-16 and forward the received bid data to the bidding software running on the production servers 77.
The embodiments described herein utilize an online reverse auction, wherein the present invention is performed by a computer processor, as an example. In the online reverse auction, suppliers 12-16 bid to supply goods or services to a purchaser 10 and the purchaser 10 typically purchases the goods or services from the lowest priced qualified bidder 12-16. It is to be understood, however, that the present invention may be used in other applications, such as, most generally, preparing databases, collecting information, requesting data, and any other applications involving entry or display of data. The auction would not necessarily occur online and the present invention may be performed by other than a computer processor.
The present invention may also be utilized in connection with auctions other than reverse auctions. For example, the present invention may be advantageously utilized with forward auctions, wherein the party offering the highest priced qualified bid, rather than the lowest priced qualified bid, is awarded the goods or services being sold. In the case of a forward auction, the leading bid is the highest amount offered and the leading bidder 12-16 is the purchaser party 10 making that highest offer, while in a reverse auction, the leading bid is the lowest amount offered and the leading bidder 12-16 is the supplier party 12-16 making that lowest bid. Similarly, placing a “better bid” in a reverse auction indicates placing a lower bid, while placing a “better bid” in a forward auction indicates placing a higher bid.
The template of the present invention may be imported into a template having elements in addition to the imported template and may also be locked so that it cannot be altered or modified.
An importable template is designed for the purpose of being merged into a general purpose template. A general purpose template is a template into which an importable template may be imported. A general purpose template, therefore, typically contains elements such as text or data entry fields in addition to the elements contained in any particular importable template. A general purpose template may contain multiple importable templates and/or multiple occurrences of a single importable template.
Both general purpose templates and importable templates contain two types of data; (i) template creation data that defines such things as elements in the template and is input by the template designer, and (ii) response data that is entered into one or more response fields by a responding entity party to whom the template is provided.
The present invention contemplates two types of importable templates: locked and unlocked. Locked importable templates have template creation data that cannot be changed by the user. Unlocked importable templates have template creation data that can be changed by the user. Importing an unlocked template into a general purpose template may be likened to taking a copy of the unlocked importable template and placing that copy in the general purpose template. The template creation data copied into the general purpose template from the unlocked importable template may be modified by the general purpose template user or creator after importation. Unlocked importable templates provide the benefit of permitting the template creator to copy sections of template creation data into the general purpose template and make modifications rather than recreate all the data contained in the unlocked importable template. Conversely, locked importable templates maintain standards within general purpose templates because they cannot be changed by the creator of the general purpose template.
A locked template offers the advantage of keeping aspects of a general template into which the locked template is imported standard. The aspects of the general template that are maintained as standards are those portions contained in the locked template. An importable template offers the advantage of not having to reenter data contained in a portion of a template that is contained in the importable template repeatedly. Once the data has been entered once into the importable template, it may thereafter be simply entered in a general template by importing the importable template.
Locked importable templates also offer the benefit that response data entered into such a template meet certain standards. Such standard response data may be entered into a database. Because all responses to a locked importable template are provided in response to an unmodifiable and, therefore, identical inquiry, the database containing responses to a particular locked importable template may be searched for one or more characteristics or a range of characteristics. That database may also be searched in conjunction with other responses stored in a database or elsewhere. Such response data may also be formatted in the same way to facilitate searching. For example, the template may ask, among other things, for a company to input the number of years the responding entity has been in business and permit a two digit integer representing years to be entered in a response field of the template. If it is later desired to allow only entities that have been in business to participate as, for example, bidding suppliers 12-16, the template creator can search for all responding entities that have been in business for at least five years in that field and quickly eliminate the remaining suppliers from contention.
In one embodiment, a creator of a locked importable template may be permitted to alter the template creation data in the locked importable template, thereby changing the locked importable template in all general purpose templates in which it exists. In that embodiment, the template, once created, is stored electronically, and completed by a responding entity electronically in a single computer network. The network may, for example, be a local area network, a wide area network, or the Internet and may be a network depicted in FIG. 2. When the locked importable template is inserted into a general purpose template, a link to a single storage area containing the locked importable template is placed in the general purpose template so that every use of the locked importable template in a general purpose template causes those general purpose templates to pull the template creation data associated with the locked importable template from that single storage location. That link may, for example, be a template identification number that is saved in a directory and associated with the memory location in which that locked importable template is stored. Thus, any change made to the template saved at the single storage location is propagated through every general purpose template that draws upon that locked importable template.
In another embodiment, where the locked importable template is copied into general purpose templates, an identifier of each use of a locked importable template may be saved as a use attribute or metadata along with the locked importable template. In an embodiment where such use metadata is utilized, a change in the locked importable template may be propagated to all general purpose templates in which the locked importable template is used. Propagation may be accomplished by accessing each template listed in the modified template use metadata and updating the locked importable template at each of those locations.
In one embodiment, the template creation data is defined in Extensible Markup Language (“XML”) and stored in a memory device as XML code. Response data is stored separately in the same or a different database. When a responding entity accesses a general purpose template containing a locked importable template in order to input response data, (i) the general purpose template contains a link to the appropriate XML code for the locked importable template, (ii) the locked importable template XML code is retrieved from the memory device, (iii) the locked importable template is displayed to the responding entity as a portion of the general purpose template, (iv) the responding entity inputs requested response data into predefined fields of the template, and (v) the response data is saved to the database.
Schema 1, as shown below, is a listing of an XML code for a general purpose template that, when executed by a processor, creates a general purpose template that utilizes an importable template. The general purpose template of schema 1 incorporates the importable template of schema 2. A user creates a general purpose template by importing a locked template. As shown in FIG. 3, the imported locked section indicates that it is not able to be edited within this general purpose template by being in a different color, different font, or any other chosen indication. XML Schema 1 depicts the XML of FIG. 3, which represents a general purpose template 100 that references a locked importable template. Details of the locked importable template are later explained in reference to FIGS. 6-8.


XML Schema 1

<templateName>General Purpose Template</templateName>

<modifiedBy>{E2206A1D-00E0-1000-006B-

0A0840328C00}</modifiedBy>

<description>This will contain a Locked importable

template.</description>

</templateInformation>

<questionLabel language=“EN”>General Section</

question Label>

</questionText>

</templateElement>

<questionLabel language=“EN”>Choose at least one

option</questionLabel>

</questionText>

</detailInfo>

<optionLabel language=“EN”>Option 1</

optionLabel>

</optionText>

</option>

</detailInfo>

<optionLabel language=“EN”>Option 2</

optionLabel>

</optionText>

</option>

<optionLabel language=“EN”>Option 3</

optionLabel>

</optionText>

</detailInfo>

</option>

</optionList>

<hintLabel languag=“EN”>You should choose at least

one.</hintLabel>

</hintText>

</templateElement>

</templateElement>

</TEMPLATE>

Schema 2, as shown below, is a listing of an XML code for an importable template that, when executed by a processor, creates an importable template. The importable template may be incorporated into a general purpose template as shown in connection with Schema 1. The importable template may be either a locked or unlocked importable template. The template 102 created by the code in Schema 2, which is shown in FIG. 4, is a locked template.


XML Schema 2

<templateName>Patent Example</templateName>

<modifiedBy>{E2206A1D-00E0-1000-006B-

0A0840328C00}</modifiedBy>

</referenceBy>

<description>Locked Importable Template.</description>

</templateInformation>

<questionLabel language=“EN”>Top Level

Heading</questionLabel>

</questionText>

</templateElement>

<questionLabel language=“EN”>Answer this textbox

question</questionLabel>

</questionText>

<validationType>String</validationType>

<hintLabel language= “EN”>Please enter some string in

this text box.</hintLabel>

</hintText>

<range>

</range>

</detailInfo>

</templateElement>

<questionLabel language=“EN”>Length</questionLabel>

</questionText>

<questionLabel language=“EN”>Width</questionLabel>

</questionText>

<questionLabel language=“EN”>Height</questionLabel>

</questionText>

<hintLabel language=“EN”>You must enter the deminsion

of this object.</hintLabel>

</hintText>

</templateElement>

</TEMPLATE>

The XML structure of Schema 1 and Schema 2 is an example of how a locked template is referenced from another template. The locked importable template appears as a templateElement node in the XML structure of Schema 1, which is the XML Schema for the general purpose template. Since this is only a reference, the actual XML of the locked template is seen in Schema 2. A templateElement is a node in the XML schema that represents any question or imported locked template. Each question style (i.e., checkbox, text box, radio button, geography, min/max, and select list) has its own question type code. This code can be seen in the schemas questionType node. A reference to a locked importable template has a special question type of ‘IM’, as may be seen toward the end of Schema 1. The “IM” question type designates that the general purpose template is referencing an importable template. A series of template Elements are included in Schema 1 and labeled as such. Within the templateElement block in Schema 1, there is a node named templateReference that designates which template is being imported into the general purpose template. The reference number associated with the templateReference 74 identifies the template of Schema 2. As may be seen by reference to Schema 2, the templateID is identified as 74.
Schema 2 is the XML for an importable template that is to be imported into the general purpose template of Schema 1. The XML of Schema 2 is in a format similar to a general purpose template, however, when a template that imports the template of Schema 1 is rendered, the imported template is accessed and the templateElements of the imported template are rendered as if they were part of the general purpose template. This gives the impression that the imported template is part of the importing general purpose template because there are no visual differences between template creation data on the importing general purpose template and the template creation data imported from the importable template.
In another embodiment, the template creation data is stored in a relational database, such as a Microsoft® SQL Server. This solution eliminates the use of XML. The embodiment has similar functionality to the solution using XML, except that the data contained in the XML is stored in a relational database. The rendering of the templates is also treated differently. Implementations utilizing XML also utilize a XSL transformation, while implementations using the relational database require a rendering object to interrupt the data returned from the database. The details of the rendering object are dependent on the code base of the application. For instance, if the code base was Microsoft® C#, the rendering object may be a class or set of classes that interrupt the data and render the correct controls onto the page.
A relational database implementation would also further facilitate flexibility of the templates created. A database facilitates customizing because columns in a database table may be ignored if they are null (empty). This is not possible with an XML structure because the outer node of the XML must be present. This implementation facilitates more scalable internationalization due to the nature of a relational database. Relational databases allow for tables to have multiple language representations of the same data based on the same Ids. Therefore, with the addition of a language identifier the database may return data in any language that is supported by the application.
The XML implementation templates may be imported as locked or unlocked, while the relational database implementation templates are imported (attached) in only one manner. However, attached templates may still be automatically updated as in the XML implementation. This is accomplished through a versioning style, which is synonymous with locked and unlocked. The versioning styles include smart versioning and simple versioning. If a template is ‘smart’ versioned then it will behave identical to a locked template. If the attached template is ‘simple’ versioned than it will act according to the rules defined by an unlocked template. Smart versioning is only applicable to implementations that utilize a relational database. A smart-versioned template may be automatically updated when a new version is published (made available for general use). A simple versioned template will not be updated. Simple-versioned instances will always reflect the version of the template at the time it was created no matter how many versions of the template are created. Smart version templates may be used to standardize sections or template types, while simple-versioned templates may maintain a snapshot, which may be used in such instances as legal agreements.
FIG. 5 illustrates a template creation, use, and modification flow chart 200. At 202, an importable template creator creates Template 1 and indicates that it is importable and locked. Two classes of template creators exist in the present embodiment: a general purpose template creator that has authority to create general purpose templates that may include both locked and unlocked importable templates and a locked importable template creator that has authority to create and modify locked importable templates. A third class of template creator may also be established to approve modifications to locked importable templates. It should be noted that one person may have authority in more than one class.
At 204, a general purpose template creator incorporates locked importable Template 1 into general purpose Template 2. At 206, a responding entity views general purpose Template 2. At 208, an importable template creator edits Template 1. At 210, approval is provided to propagate the proposed change made at 208 through all general purpose templates incorporating locked importable Template 1. At 212, approved edited Template 1 is propagated to all general purpose templates incorporating Template 1. Accordingly, general purpose Template 2 is modified and any responding entity that views Template 2 thereafter will see Template 2 with the modifications made to Template 1 at 208.
When a template is edited, the new version may replace the previous version, or the new version may be saved in a memory device as a separate version to facilitate reversion to a previous version. The latest version may always be the version provided to general purpose templates incorporating the locked importable template.
As discussed above, FIG. 3 illustrates a general purpose template containing a locked importable template. This general purpose template is created for use in a request for information related to the purchase of goods or services in an auction. The template, furthermore, includes an importable template and that importable template is locked in this embodiment. The locked importable template is a block that has been inserted into the general purpose template. The locked importable template block contains elements. These elements include a section header, a textbox question and minimum and maximum questions. Other elements that may be present in a template include, for example, radio button questions that would be posed to responding entities and response fields in which responses may be entered by responding entities.
Templates may be provided with unique identifiers by way of which, for example, an importable template may be referenced in a general purpose template and by way of which an importable template may be imported into a general purpose template. Elements within the template may be provided with unique identifiers as well. Thus, for example, a response field in a locked importable template may have a unique identifier that is associated with that field every time response data for that field is received. A separate owner identifier may also be associated with each field. That owner identifier will be the same for every response entered into any field in a particular template by that responding entity and may be the same for every response entered into any field in any template by that responding entity. Therefore, a particular field of a template may be searched across all of responding entities by searching respondent entries having the element identifier associated with that field. Moreover, a particular field of a locked importable template may be searched across a range of responding entities by searching respondent entries with the element identifier associated with that field and a range of owner identifiers.
A template may be stored in a database to improve retrieval speed over storage in a file system. A template may also be stored in a database to provide additional flexibility over file systems in the backup process. Storing the XML in a database also allows for easy collection of additional data regarding the template. This data may be used for searching or reporting. In addition, there may be other uses for additional data.
In one embodiment, the template is stored in XML format, however, the template may alternately be stored in another source code or an object code format. The template may be stored in the database as a text field of unspecified size so that the template code can be modified and can grow as needed. For example, the template may be stored as a database context, for example, as a text blob in Microsoft® SQL Server 2000™. A “text blob” is a common name for the SQL Server ‘text’ data type, which may be used to store XML for large amounts of text.
Tables may be required to support the database structure for the template and the tool to search responses given by a responding entity. For example, the template detail table, as shown in Table 1, is a table in which the XML Schema are stored. Each change to a general purpose template or an importable template would be written to this table. Responses provided by a responding entity are stored in the AttrValue table, as shown in Table 2. Metadata that is collected about the template is stored in a Template table, as shown in Table 3. This data includes whether it is an importable, locked, unlocked or general purpose template. Whenever there is a list of templates, it is retrieved from this table. Other tables, including Tables 3, 4, and 5, are used for reference or desired functions.

TABLE 1

Template

	PK	Template Id
	PK	Version
		Template Xml

TABLE 2

AttrValue

	PK	Template Id
	PK	Attr Id
	PK	Owner ID
		Attr_Value
		Instance_Id

TABLE 3

Template

	PK	Template Id
		name
		description
		last_modified
		modified_by
		template_type

TABLE 4

Attr

	PK	AttrId
		AttrName
		Instance_Id

TABLE 5

AttrValueDeleted

	PK	Template Id
	PK	Attr Id
	PK	Owner Id
		Attr_Value
		Instance_Id

TABLE 6

AttrValueSearch

	PK	Template Id
	PK	Attr Id
	PK	Owner Id
		Attr_Value
		Instance_Id

TABLE 7

AttrValueDeleted

	PK	Owner Id
		Template_Id
		Template_Status

FIG. 6 is a sample template creation screen display 500 for an embodiment of the present invention. This screen 500 may be used to create a general purpose template or an importable template and an importable template created through this screen may be either locked or unlocked. At 502, a title is entered for the template. When the template is stored, the title is stored in a directory so that users may identify templates by title. As indicated at 502 by the asterisk, a title is a field that is required to be entered by the template creator. At 504, a description of the template being created is entered. That description may briefly indicate, for example, the purpose of the template or the type of use for which the template is intended. The template description may also be viewed by potential users when the template title is selected. As indicated at 504 by the asterisk, a template description is also a field that is required to be entered by the template creator.
Import functionality of the sample template creation screen display 500 is defined at 508, 510, and 512. At 508, a binary selectable area or “check box” appears next to the word “Importable.” If the template being created is intended to be an importable template, the box in this embodiment is selected and a check appears to indicate that it is importable. If the template being created is not intended to be an importable template, the box in this embodiment is either not selected or is deselected and a blank box appears to indicate that the template is not importable. If a non-importable file is indicated at 506, the “Locked” and “Unlocked” selection areas at 508 and 510 are not selectable because locking and unlocking is only applicable to importable templates. If, however, an importable template is indicated at 506, then either the locked selection area of 508 or the unlocked selection area at 510 must be selected. In this embodiment, when “Locked” is selected at 508, “Unlocked” is deselected at 510 and when “Unlocked” is selected at 510, “Locked” is deselected at 508.
The “Detail Page” selection box at 512 may be selected to indicate that the template will be used as a detail page or deselected to indicate that the template will not be used as a detail page. A detail page can only be displayed as a secondary page, which means a general purpose template creator must specify that a question links to a given detail page. A non-detail page represents a general purpose template.
FIG. 7 is a sample template editing screen display 530 that may be used in conjunction with the embodiment of the present invention illustrated in FIG. 6. This screen 530 may be used to create template segments such as text and fields in a general purpose template or an importable template. The template editing screen 530 illustrated in FIG. 7 is based on the template created in the template creation screen display 500 of FIG. 6. In the template editing screen 530, information is displayed in the template block 540 and that information is drawn from the template creation screen 500: the template title is displayed at 532, the template description is displayed at 534, the import status is displayed at 536, and the detail information is displayed at 538. Fields are created in the “Build Fields” block 550. The type of field desired is selected from the “Field Type” pull down menu 552. In this embodiment, it is required that the person creating the template select a field type. Field types include checkbox, radio button, text box, geography, select list and min/max. A “Hints” area is provided to provide information to assist in selecting a field type.
For example, when creating a field for a template, a text field may be formed by selecting “text box” from the field types menu and then completing any additional fields that may appear. A select list, in which a responding entity would choose response data, may be formed by selecting “select list” from the field type menu.
A “Template Preview” box 560 is provided and depicts fields created for the template thus far. As may be seen at 562, the text field “Example Question *” has been created in the template and a response data field has been created at 564. At 566, an edit selection object is provided for the “Example Question *” field 562 and response data 564 field on the same line. The edit selection object 566 may be selected by a user and permits the user to edit the fields on the same line and to the right of that object 566, or in this example, the fields shown at 562 and 564. At 568, a delete selection function 568 is provided and may be selected by a user to delete the fields to the right of that function 568, or in this example, fields 562 and 564. At 570, a comment or hint may be provided by the template creator for display to the responding entity. In this example, the hint indicates that the associated fields 562 and 564 are part of an importable template. At 572, a scroll control function is included to permit the user to scroll up or down to view other fields. The language in which the template is to be displayed may be modified at a language drop down box 574 of the “Template Preview” box 560.
FIG. 8 is a sample template editing screen display 600 that may be used to create fields in a general purpose template. This screen 600 may, moreover, be used to insert an importable template into a general purpose template. The template editing screen 600, displays a template title at 632, a template description at 634, an import status at 636, and detail information at 638 in a template description box 630. Fields are created in the “Build Fields” block 650 as they are in the “Build Fields” block 550 of screen 530.
A “Template Preview” box 660 is provided and depicts fields created for the general purpose template thus far. The “Template Preview” box 660 is divided into two sections, an imported element section 662 and a non-imported element section 664. One imported element 666, which is the same element created in the create new template screen 500 and the edit template screen 540, is illustrated. It should be noted that the imported element 666 provides only an option for removal of that element and does not permit editing of that element. This is because the imported element 666 is locked and, therefore, not editable. A non-imported element 668 is also depicted and may be either edited or deleted. Each of the elements, both imported and non-imported, may include “Hint” areas 670 and scroll areas 672. The language in which the template is to be displayed may also be modified at a language drop down box 674 of the “Template Preview” box 660.
When the template is created, a Search view is automatically generated for the template. Once a template is published (available for general use), the user may go to a search page and choose a template. A view of the template that will allow the user to search for data entered against the chosen template is provided. An example of a search algorithm is shown in Schemas 3-6 below. This algorithm uses Tables 1-7 above and stored procedures that exist in the database. Stored procedures are files that contain code that retrieves and manipulates data from a relational database.
Searches comprise multiple micro-queries, where each query is a combination of Template Id and Attribute ID and perhaps also Attribute Value. After each micro-query is processed, the server will return a list of owners. The server will then perform set operation and return a caller with either a union or intersection of those results. Schema 3 illustrates a stored procedure that implements micro-query.


Schema 3

ALTER procedure ap_AttrValueSearhByTemplIdAttrId_List_Intermed

Results

-- Returns intersection of set of OwnerIds that are already in #Owner

-- and OwnerIds which satisfy the new @Where clause.

-- counts on the existence of #Owner table that is created by caller

@TemplateId int,

@AttrId int,

@RowCount int output

as

set nocount on

declare @temp table (ownerid int)

declare @intersection table (ownerid int)

declare @spid int

set @spid = @@spid

if not exists(select spid from tempdb.dbo.IntermedResults where spid =

@spid)

begin

insert into tempdb.dbo.IntermedResuts (spid, OwnerId)

select distinct @spid, OwnerId

from AttrValueSearch (nolock)

where TemplateId = @TemplateId

and AttrId = @AttrId

set @RowCoount = @@Rowcount

return

end

insert into @tmp

select OwnerId

from AttrValueSearch (nolock)

where TemplateId = @TemplateId

and AttrId = @AttrId

insert into @intersection(OwnerId)

select distint tempdb.dbo.IntermedResults.ownerID

from tempdb.dbo.IntermedResults (nolock) inner join (select * from @tmp)

tmp

on tempdb.dbo.IntermedResults.OwnerId = tmp.OwnerId

and tempdb.dbo.IntermedResults.spid = @spid

--truncate table #Owner

delete tempdb.dbo.IntermedResults

where spid = @spid

insert into tempdb.dbo.IntermedResults (spid, OwnerId)

select * from (select distinct @spid spid, OwnerId from @intersection ) a

set @RowCount = @@Rowcount

return

The stored procedure of Schema 3 relies on a presence of InterMedResults static table created in TempDB, as shown in Schema 4.


Schema 4

CREATE TABLE [InterMedResults] (

[spid] [int] NOT NULL ,

[OwnerId] [int] NOT NULL ,

CONSTRAINT [PK_InterMedResults] PRIMARY KEY CLUSTERED

(

[spid],

[OwnderId]

) ON [PRIMARY]

GO

In one embodiment, the procedure of Schema 4 will be executed from a new batch, as shown in Schema 5.


Schema 5

set nocount on

declare @rc int

exec ap_AttrValueSearhByTemplIdAttrId_List_IntermedResults 99, 333,

@rc output if @rc = 0 goto BATCH_END

exec ap_AttrValueSearhByTemplIdAttrId_List_IntermedResults 99, 334,

@rc output if @rc = 0 goto BATCH_END

exec ap_AttrValueSearhByTemplIdAttrId_List_IntermedResults 99, 335,

@rc output if @rc = 0 goto BATCH_END

select ownerId from tempdb.dbo.IntermedResults where spid = @@spid

BATCH_END:

delete tempdb.dbo.IntermedResults where spid = @@spid

Other Modification:

ALTER Proc _New_AttrSearch @TemplateId int, @Where varcher(1000),

@NumMatching int as

set nocount on

Declare @SQL varchar(2000)

select @SQL = ’

select OwnerId,count(*) as NumMatching

From AttrValues_Comma

where TemplateId = ’+ convert(varchar(15),@TemplateId) +’

and (‘+ @Where +’)

Group by OwnerId

Having count(distint AttrId) >= ‘+ convert(varchar(15),@NumMatching)

exec (@SQL)

Finally, multiple micro-criteria may be called with a single stored procedure call, as shown in Schema 6.


Schema 6

Exec _New_AttrSearch 200

, ‘(AttrID = 3422 and AttrValue > 35) or (AttrID = 2349 and AttrValue =

333)’

, 2

While the invention has been described in detail and with reference to specific embodiments thereof, it will be apparent to one skilled in the art that various changes and modifications can be made therein without departing from the spirit and scope thereof. In particular, it should be noted that while the templates described above have been described in the context of auctions, the templates may be used in any non-auction situations. Thus, it is intended that the present invention cover the modifications and variations of this invention provided they come within the scope of the appended claims and their equivalents.

Claims

1. A system, comprising:

an interface configured to:

receive a request for a general purpose electronic template including a first set of elements, wherein the general purpose electronic template includes a reference to an importable electronic template to be imported into the general purpose electronic template; and

in response to receiving the request, obtain the importable electronic template based at least in part on the reference included in the general purpose electronic template, wherein the importable electronic template includes a second set of elements including:

a text field; and

a response field:

a processor configured to:

render the obtained importable electronic template as a portion of the general purpose electronic template at least in part by importing the obtained importable electronic template into the general purpose electronic template such that the general purpose electronic template includes at least a portion of the second set of elements included in the importable electronic template in addition to the first set of elements; and

a memory coupled to the processor and configured to provide the processor with instructions.

2. The system recited in claim 1, wherein the importable electronic template is locked such that a user of the general purpose electronic template is prohibited from modifying the importable electronic template.

3. The system recited in claim 2, wherein the interface is further configured to receive an indication of a change to the importable electronic template, wherein the change is caused at least in part by a second user that is permitted to modify the importable electronic template.

4. The system recited in claim 1, wherein the reference to the importable electronic template includes a reference to a location in a data storage in which the importable electronic template is stored.

5. The system recited in claim 1, wherein at least one of the text field and the response field are referenced by the general purpose electronic template.

6. The system recited in claim 1, wherein the text field of the importable electronic template is modified after the importable electronic template is imported into the general purpose electronic template.

7. The system recited in claim 6, wherein the modification to the text field is rendered in the general purpose electronic template.

8. The system recited in claim 6, wherein the modification to the text field is propagated to a second general purpose electronic template that includes a reference to the importable electronic template.

9. The system recited in claim 1, wherein the response field is modified after the importable electronic template is incorporated into the general purpose electronic template.

10. The system recited in claim 9, wherein the modification to the response field is rendered in the general purpose electronic template.

11. They system recited in claim 9, wherein the modification to the response field is propagated to a second general purpose electronic template that includes a reference to the importable electronic template.

12. The system recited in claim 1, wherein the text field is configured to receive template creation data stored in at least one of a relational database and a memory device of XML code.

13. The system recited in claim 1, wherein the processor is further configured to render a search view that permits a user to search for the importable electronic template and data entered against the importable electronic template.

14. A method, comprising:

receiving a request for a general purpose electronic template including a first set of elements, wherein the general purpose electronic template includes a reference to an importable electronic template to be imported into the general purpose electronic template; and

in response to receiving the request, obtaining the importable electronic template based at least in part on the reference included in the general purpose electronic template, wherein the importable electronic template includes a second set of elements including:

a text field; and

a response field; and

rendering the obtained importable electronic template as a portion of the general purpose electronic template at least in part by importing the obtained importable electronic template into the general purpose electronic template such that the general purpose electronic template includes at least a portion of the second set of elements included in the importable electronic template in addition to the first set of elements.

15. The method of claim 14, wherein the importable electronic template is locked such that a user of the general purpose electronic template is prohibited from modifying the importable electronic template.

16. The method of claim 14, wherein the reference to the importable electronic template includes a reference to a location in a data storage in which the importable electronic template is stored.

17. The method of claim 14, wherein at least one of the text field and the response field of the importable electronic template is modified after the importable electronic template is imported into the general purpose electronic template.

18. A computer program product, the computer program product being embodied in a tangible computer readable storage medium and comprising computer instructions for:

a text field; and

a response field; and

19. The computer program product of claim 18, wherein the importable electronic template is locked such that a user of the general purpose electronic template is prohibited from modifying the importable electronic template.

20. The computer program product of claim 18, wherein at least one of the text field and the response field of the importable electronic template is modified after the importable electronic template is imported into the general purpose electronic template.