Promoting data from structured data files

Description

TECHNICAL FIELD

This invention relates to promoting data from structured data files.

BACKGROUND

Computer users, whether they be businesses or individuals, often need to share access to data files. For this reason, data files are often stored at some location accessible by many different users, such as a computer server. Users can then access the data files on the server through a communications network.

Typically, a computer server allows access to a database that stores many, many data files. This database can be arranged into a filing system, usually listing the data files by file name. Finding data files by name can be fairly easy, but finding data files having particular characteristics can be difficult, because the names of the data files may not sufficiently inform users about characteristics of the data files.

To address this need to find data files having certain characteristics, some current servers include libraries that describe the data files accessible by the server in greater detail than simply the data files' names. These servers can also include a web server to enable users to see and access the libraries. For example, some current computer servers include Microsoft SharePoint™ Products and Technologies, which provide a library and web server that describes data files accessible by the computer server.

FIG. 1 shows a simplified model of a typical server and library. FIG. 1 shows a server 102 that includes a database 104 with data files 106, a filing system 108, and a library 110, as well as a web server 112.

The library 110 typically contains basic information about the data files 106. When a computer user 114 accesses the library 110 through a communication network 116, the server 102 (through the web server 112) presents the information in the library 110 as a table. Often this information (also called “properties”) can be easily seen and/or searched by the user 114.

Referring to FIG. 2, a table 202 is shown that includes properties of the data files 106. Three data files, a first, second, and third data file 204, 206, and 208, are shown in a part 210 of the filing system 108. The table 202 shows an example of four properties of these three data files.

Each row of the table 202 is dedicated to each of the data files 204, 206, and 208. Each of these rows can contain a reference and/or be uniquely identified with the data file to which it is dedicated. Each column of the table 202 is dedicated to a property of these data files. Each row and column can intersect at a cell; this cell can provide information unique to a particular property for a particular data file. The first column shows a property for each of the data file's names, called a name property 212. The second column provides an author's name property 214 about each of the data files. The third column provides a creation-date property 216. The fourth provides a last-modified-date property 218. These properties inform the user 114 about each of the three data files' name, author, creation date, and last date it was modified.

Other information can also be added to the library 110. This information can be added, usually at the computer user's 114 request. This information is typically information entered into the library 110 by the computer user 114. Thus, the user 114 can request that the library 110 add an additional column and then manually enter information into that column.

Typical libraries are inadequate in many ways, however. The properties included in current libraries often fail to inform the user 114 about what data is actually in the data files 106. Rather, these properties typically provide the user 114 with information exterior to the data files 106, such as when they were created or who authored them.

SUMMARY

In accordance with at least one embodiment, a data promotion tool is provided and enables promotion of data from a structured data file to a library. In at least some embodiments, the described tool also enables demotion of data from a library to a structured data file.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a simplified model of a typical server having a database with data files, a filing system, and a library within the filing system, and a web server; communications network; and a computer user.

FIG. 2 illustrates applications and files of a simplified, typical server and sets forth an exemplary table of a library showing basic properties of three data files.

FIG. 3 illustrates an exemplary computer server, in accordance with one embodiment, capable of promoting and demoting data from and to structured data files, an exemplary communication network, and an exemplary computer user.

FIG. 4 illustrates exemplary applications and files of an exemplary computer server, in accordance with one embodiment, capable of promoting and demoting data, and sets forth an exemplary table showing basic properties of three data files.

FIG. 5 sets forth a flow diagram of an exemplary process, in accordance with one embodiment, for provisioning, promoting, and demoting data of structured data files.

FIG. 6 sets forth an exemplary, provisioned table, in accordance with one embodiment, for showing basic and advanced properties of three structured data files.

FIG. 7 illustrates a rendering of an exemplary structured data file, in accordance with one embodiment, having fields with data.

FIG. 8 sets forth an exemplary table, in accordance with one embodiment, having basic and advanced properties for three structured data files.

FIG. 9 sets forth an exemplary table, in accordance with one embodiment, having basic and advanced properties, one of the advanced properties for two of three structured data files containing new, demotable data.

FIG. 10 illustrates a rendering of an exemplary structured data file, in accordance with one embodiment, having fields with data, one of the fields containing new, demoted data.

FIG. 11 sets forth a flow diagram of an implementation of an exemplary process, in accordance with one embodiment, for provisioning, promoting, and demoting data of structured data files.

The same numbers are used throughout the disclosure and figures to reference like components and features.

DETAILED DESCRIPTION

Examples of Promoting Data

The following disclosure describes a system and method (a “tool”) for promoting data from structured data files. This promotion can enable a library to allow users to quickly and easily search through properties that are based on data that is within the structured data files.

If, for instance, a sales manager wants to see every sales report that lists a sale to “ACME Tire Co.”, he can do so. He can search the library with a search engine and almost immediately see every sales report that mentions a sale to ACME Tire Co.

This promotion of data from within a structured data file is very powerful. The data promoted can be easily searched or presented to users for easy viewing. The data promoted can also be a function of data copied from within the structured data file. These functions can aggregate data from within a structured data file, for instance.

If the sales manager wants to see every sales report that lists a sale to ACME Tire Co. where the sales total to ACME Tire Co. is greater than $1000, for instance, he can do so. Assume that the sales reports are structured data files and that each can have multiple entries for sales. Data from each of the entries in each of the sales reports can be copied, added together, and the total promoted to the library. Thus, the library can contain the total sales to ACME Tire Co. for each of the sales reports. The manager, then, can search the library for sales to ACME Tire Co. that total more than $1000. Quickly and easily, the manager can find every sales report that has sales to ACME Tire Co. totaling greater than $1000.

In this example, the sales manager did all of this without altering the sales reports or having people enter information into the library by hand.

Example of Demoting Data

The tool described in the following disclosure can also demote data from a file (e.g., a library) to within a structured, data file. Demotion allows a user to quickly and easily change data within structured data files.

Like the first example above, assume the sales manager found every sales report that lists a sale to ACME Tire Co., regardless of the total of the sales. In this case, assume that the sales manager wants to change all of the sales reports. He could open each of the files listed in the library and alter each, but that could be time consuming and possibly mistake prone (especially if he has to enter something many times).

Instead, the tool described here allows him to alter each of the sales reports through another file (e.g., a library). With this tool, the sales manager can replace a promoted property in a library with some other data and have a corresponding change made to the sales reports. This is a type of demotion.

Continuing the example, assume that 132 sales reports are found when the sales manager searches for sales reports with sales to ACME Tire Co. Assume also that the sales manager has learned that ACME Tire Co. just changed its name to “VICTORY Tire Co.”. To keep his new sales reports to VICTORY Tire Co. and his old sales reports to ACME Tire Co. consistent, he wants to change the name of “ACME Tire. Co.” to “VICTORY Tire Co.” in each of the sales reports. With the disclosed tool, he can do so.

The sales manager, with the 132 sales reports listed from his library search, can globally change the words “ACME Tire Co.” to “VICTORY Tire Co.” The tool can then change the part (e.g., the node) within each of the 132 sales reports that lists “ACME Tire Co.” to “VICTORY Tire Co.”. The sales manager is enabled to do all of this simply and easily, without having to change each sales report manually.

As is apparent, demotion of data from a library to within a structured data file is powerful; it can save time, money, and be more accurate than many alternatives.

Promoting Data, Generally

As mentioned in part above, the tool promotes data from within structured data files. The data can be promoted to various types of files, including those that are easy for a user to search, such as data storage that can be optimized for search functions. The file into which data is promoted can be a text file, a database, and the like. The file can be a locally accessible library, such as one stored on a computer user's computer or accessible via a local intranet. The file can also be remotely accessible, such as a library stored on a server accessible via the global internet.

In the following description a currently available library is altered and augmented for use as the file into which data from structured data files is promoted. The use of this library in the description below is not intended to limit the scope or applicability of the tool; other types of files that allow for searching and/or presentation of data can also be used. Also as part of this implementation, structured data files from which data is promoted are not altered, either in their structure or their contents. In other implementations, the structured data files can be altered as part of promotion of data, though altering the structured data files may cause undesirable complications for later use of the structured data files.

Also in the following description, the tool is described in the context of a server having the currently available library, a database with structured data files, and a web server; a communications network; and a single computer user. These devices will be described first, followed by a discussion of the techniques in which these and other devices can be used.

Exemplary Architecture

FIGS. 3 and 4 include an exemplary architecture for the promotion and demotion tool, in accordance with one embodiment. The architecture in these figures is intended to aid in the discussion of the tool, and is not intended to limit its applicability.

FIG. 3 shows a simplified model of a server 302; a database 304 having structured data files 306, a filing system 308, and a library 310 within the filing system 308; a web server 312; a computer user 314; and a communication network 316. The server 302 can be accessed by the user 314 through the communication network 316. The communication network 316 can be a local intranet or a global internet, for example.

The server 302 also includes a provisioning application 318, a rules file 320, and a promotion application 322. The promotion application 322 can include a demotion application 324, discussed in greater detail below.

In this implementation, the library 310 contains two basic properties about three of the structured data files 306, discussed below. When the computer user 314 accesses the library 310, the server 302 presents these basic properties in the library 310 as a table.

FIG. 4 sets forth a table 402 showing two basic properties of three of the structured data files 306. The data files 306 include a first sales report 404, a second sales report 406, and a third sales report 408. These reports are shown in a part 410 of the filing system 308 for the database 304. The basic properties shown are a file-name property 412 and an author-name property 414.

Techniques for Provisioning, Promoting, and Demoting Data

Preparing the Library for New Properties

Prior to promoting data from within the structured data files 306 into the library 310, the provisioning application 318 communicates with the library 310 to prepare the library 310 for new properties.

The provisioning application 318 can be part of the server 302 or otherwise. In the example shown in FIG. 3, the provisioning application 318 is part of the server 302.

FIG. 5 shows an exemplary process 500 for provisioning, promoting, and demoting data, in accordance with one embodiment. The process 500 is illustrated as a series of blocks representing individual operations or acts performed by the server 302. This and other processes described herein may be implemented in any suitable hardware, software, firmware, or combination thereof. In the case of software and firmware, these processes represent sets of operations implemented as computer-executable instructions.

At block 502, the provisioning application 318 prepares (“provisions”) for new properties to be promoted. This can include creating a new library or altering an existing one. In the ongoing implementation, the library 310 is altered to be capable of adding new properties. In doing so, the provisioning application 318 alters or requests that the library 310 alter itself. In FIG. 4, the library 310 shows properties for files as columns, with a row dedicated to each of the structured data files 306. Thus, in this example the provisioning application 318 interacts with the library 310 to add a column for each property that is to be added.

FIG. 6 sets forth an exemplary provisioned example of the table 402 showing two basic properties of three of the structured data files 306 (the structured data files 404, 406, and 408) and new columns for four advanced properties. The basic properties shown are the file-name property 412 and the author-name property 414. The advanced properties shown are a customer-name advanced property 602, a total-sale advanced property 604, a sale-date advanced property 606, and a quality-of-service advanced property 608. The columns for these advanced properties are provisioned but do not yet have data promoted into them. These particular advanced properties are examples of many different kinds of properties that can be provisioned and promoted as part of this process 500.

As part of this block 502 the provisioning application 318 can follow various instructions in the rules file 320. The rules file 320 includes instructions on what data is to be promoted, where it is to be promoted (such as in which column of the library 310), how to provision (e.g., alter) the library 310 to make room for the new properties, and the like. The rules file 320 can include functions that are to be performed on data copied (e.g., extracted) from the structured data files 306 and ways to locate the data within the structured data files 306.

In one implementation, the rules file 320 is constructed with the aid of various XML schemas (e.g., as specified by XSD) governing structured data files that include XML.

Promoting Data from Structured Data Files

The promotion application 322 promotes data within a structured data file. It can do so following blocks 504 and 508 or blocks 504, 506, and 508.

Specifically, at block 504, the promotion application 322 copies data from a structured data file. To do so, the promotion application 322 locates a particular part (e.g., node) of the structured data file and then copies the data in that part. The promotion application 322 can do so on command from a user or entity, such as from or through the server 302 or the library 310. The promotion application 322 can also do so when a structured data file is being saved into the database 304.

At this block 504 the promotion application 322 can follow various instructions in the rules file 320. The rules file 320, for instance, can instruct the promotion application 322 to locate a part of a structured data file with an XPath (XML Path language) expression, if the structured data file includes XML. With that part located, the promotion application 322 can copy whatever is in the located part, such as “ACME Tire Co.” for instance.

FIG. 7 sets forth an exemplary structured data file having fields with data. This exemplary structured data file is an example of a rendering of the first sales report 404 authored by Joe Smith (see FIG. 4). The first sales report 404 can also be represented hierarchically, thereby showing parts of the structured data file as nodes (not shown).

The first sales report 404 shown in FIG. 7 includes the following fields containing data: quality field 702; customer field 704; sale date field 706; delivery date field 708; first product field 710; first product quantity field 712; first product price field 714; first product price total field 716; second product field 718; second product quantity field 720; second product price field 722; second product price total field 724; third product field 726; third product quantity field 728; third product price field 730; and third product price total field 732.

At block 504 the promotion application 322 copies data from particular parts of the first sales report 404 (here represented as fields in the rendered first sales report 404). In this implementation, the data to be copied is shown within the following fields: the quality field 702; the customer field 704; the sale date field 706; the first product price total field 716; the second product price total field 724; and the third product price total field 732.

At block 506, the promotion application 322 performs functions, if applicable, on the copied data. The functions can include aggregating the data, summing the data (if the data is numerical), comparing data to other information available to the promotion application 322, concatenating the data, and other functions known in the art.

In the ongoing example, the data copied at block 504 from the first sales report 404 includes: “satisfied”, shown in the quality field 702; “ACME Tire Co.”, shown in the customer field 704; “Mar. 13, 2000”, shown in the sale date field 706; “580.50”, shown in the first product price total field 716; “659.04”, shown in the second product price total field 724; and “102.96”, shown in the third product price total field 732.

Based on the instructions in the rules file 320, the promotion application 322 can perform functions on the data. In the ongoing example, the rules file 320 instructs the promotion application 322 to add up the first, second, and third product price totals. Thus, the promotion application 322 adds “580.50”, “659.04”, and “102.96” for a total of “1342.50.”

At block 508, the promotion application 322 adds the copied and/or resulting data to the library 310. If a function has been performed on the data copied, the data resulting from the function on the copied data is added to an appropriate part of the library 310. If not, the copied data is added.

In the ongoing example, the rules file 320 instructs the promotion application 322 to add the data, “satisfied”, “ACME Tire Co.”, “Mar. 13, 2000”, and 1342.50 to the advanced properties shown in the table 402 shown in FIG. 6. Thus, the promotion application 322 adds this data to the columns for the customer-name advanced property 602, the total-sale advanced property 604, the sale-date advanced property 606, and the quality-of-service advanced property 608 for the first row. The first row corresponds to the first sales report 404.

The promotion application 322 also performs blocks 504, 506, and 508 for the second and third sales reports 406 and 408 and so fills the other rows of the table 402.

FIG. 8 sets forth an exemplary promoted example of the table 402 showing two basic properties of three of the structured data files 306 (the structured data files 404, 406, and 408) and columns containing four advanced properties. The basic properties shown are the file-name property 412 and the author-name property 414. The advanced and now populated properties shown are the customer-name advanced property 602, the total-sale advanced property 604, the sale-date advanced property 606, and the quality-of-service advanced property 608. These particular advanced properties are examples of many different kinds of properties that can be provisioned and promoted as part of this process 500.

As shown in FIG. 8, with the disclosed tool a user can quickly and easily see and/or search through structured data files based on what is in those files. The user can view and search certain data promoted to the library 310, allowing the user to better analyze and sort through structured data files.

Demoting Data into Structured Data Files

At block 510, in accordance with the same embodiment, the demotion application 324 can optionally demote data into a structured data file. To do so, the demotion application 324 locates a particular part (or parts) of the structured data file that are associated with data in the library 310. The demotion application 324 can determine this association based on the data's location in the library 310, such as a cell in the table 402. The demotion application 324 then replaces the data in the appropriate part of the structured data file with data from that location in the library 310. The demotion application 324 can do so on command from a user or entity, such as from or through the server 302 or the library 310. The demotion application 324 can also demote data in the library 310 into the structured data file whenever a user replaces data within the library 310 with other data.

In one implementation, a user can change data in multiple structured data files by globally changing data in an advanced property in the library 310. If, for example, the sales manager from the above examples wishes to change the customer's name in the first sales report 404 and the third sales report 408, he can do so simply by changing the customer name in the customer-name advanced property 602 (filled and shown in FIG. 8).

Assume that the sales manager uses the library 310 and the customer-name advanced property 602 of FIG. 8 to find two structured data files in which the customer is “ACME Tire Co.” In this example only two such structured data files are shown to have this customer name (the first sales report 404 and the third sales report 408) though hundreds of structured data files could also be demoted in the same way. The sales manager can find these by running a search of the library 310 to present only those structured data files in which the word “ACME” appears in the properties 602 of FIG. 8. The sales manager could also just globally replace the names without running a search.

In this example, the sales manager wants to change all of the sales reports from the name “ACME Tire Co.” to “VICTORY Tire Co.” In this implementation he can do so simply by globally replacing the text in the library 310 “ACME Tire Co.” with “VICTORY Tire Co.”

FIG. 9 sets forth an exemplary and altered, promoted table 902 showing two basic properties of the structured data files 306 (the sales reports 404, 406, and 408) and columns containing the four advanced properties, 602, 604, 606, and 608. The basic properties shown are the file-name property 412 and the author-name property 414. The advanced, populated properties shown are the customer-name advanced property 602, the total-sale advanced property 604, the sale-date advanced property 606, and the quality-of-service advanced property 608. Here the data in two of the customer-name advanced property's 602 fields have been altered to replace “ACME Tire Co.” with “VICTORY Tire Co.”

In this example, the demotion application 324 alters each of the sales reports 404 and 408. The demotion application 324 demotes the replaced data into the sales reports 404 and 408. With this tool, the sales manager can replace a promoted property in the library with some other information and have a corresponding change made to the sales reports.

FIG. 10 sets forth an example of this demotion, here to the sales report 404 rendered in FIG. 7. Here the customer name is changed from “ACME Tire Co.” with “VICTORY Tire Co.”, as shown at a demoted example of the customer field 704.

Using this tool disclosed herein, a user can alter many, many structured data files quickly and easily.

Exemplary Implementation

The following implementation describes one way in which the tool can be implemented. The server 302 and its parts, the communication network 316, and the computer user 314 will be used to aid in describing this implementation, as will the structured data files 404, 406, and 408. In this implementation, the communication network 316 includes a global interne and the server 302 is an altered version of the currently available SharePoint™ server. The library 310 is an altered version of a library used by the SharePoint™ server.

These are used as examples of this implementation, and are not intended to limit the scope or applicability of this implementation or the tool.

FIG. 11 shows an exemplary process 1100, which is an implementation of the process 500 for provisioning and promoting data from the structured data files 306.

At block 1102, the server 302 receives a remote procedure call (RPC) across the communication network 316. This RPC uses the URL (Universal Resource Locator) to identify the server 302. It also includes instructions to the library 310, which the library 310 follows. This RPC call is used by the library 310 to add basic properties fields, if desired, and to set up the library 310. The RPC is communicated through HTTP (HyperText Transfer Protocol), though it can be done in other well-known ways as well.

At block 1104, the server 302 receives the rules file 320. In one implementation, the server 302 receives the rules file 320 in another RPC sent by the computer user 314. As shown in FIG. 3, the rules file 320 is then stored by the server 302.

At block 1106, the provisioning application 318 reads the rules file 320 to instruct the library to add advanced property fields to the library 310. An example of these advanced property fields that can be opened by the library 310 in response to the provisioning application 318 following the rules file 320 are the advanced properties 602, 604, 606, and 608 shown in FIG. 6.

The server 302 can receive a second or additional rules file to augment or replace the rules file 320. Thus, if the computer user 314 wants to change the library 310 again, the user 314 can send another rules file to replace or augment the rules file 320.

At block 1108, the server 302 receives an XML file. The server 302 can receive the XML file via an RPC from the computer user 314. In this implementation, the structured data files include XML. Also in this implementation, the XML file is transported in a Simple Object Access Protocol (SOAP) wrapper. It is later loaded in Document Object Model (DOM) format for promotion and/or demotion of data.

A simplified view of DOM for the sales report 404 can be shown as:

FirstSalesReport

Quality

Customer

SaleDate

DeliveryDate

Product

ProductQuantity

ProductPrice

ProductPriceTotal

Product

ProductQuantity

ProductPrice

ProductPriceTotal

Product

ProductQuantity

ProductPrice

ProductPriceTotal

Here the root of the structured data file is “FirstSalesReport”.

At block 1110, the server 302 saves the XML file. The server 302 receives the XML file and saves it into the structured data files 306 of the database 304. The XML file is sent in SOAP because that can make it easier to transfer. It can be loaded in DOM format because that can make it easier to process and search. As part of parallel to, or after this save of the XML file, the promotion application 322 acts. The library 310 also acts to promote basic properties into the library 310.

At block 1112, the promotion application 322 follows the instructions in the rules file 320 to promote data (as advanced properties) from within the XML file into the library 310. The library 310 also promotes basic properties about the XML file (such as the properties 412 and 414 of FIG. 4). Block 1112 is an exemplary implementation of blocks 504 and 508 or 504, 506, and 508 of the process 500.

As part of block 1112, the promotion application 322 reads and follows instructions in the rules file 320. The rules file's 320 instructions include rules. The promotion application 322 reads and follows each rule of the rules file 320 in order, until all of the rules have been followed and advanced promotion is complete.

For example, assume that the XML file saved at block 1110 is the sales report 404. Assume also that the rules file 320 includes the following rules:

• • Rule 1: Select FirstSalesReport/“Customer,” copy data here, store data here into third column of row associated with XML file's row.
  • Rule 2: Select FirstSalesReport/Product/“ProductPriceTotal,” copy data here, perform function (add together) all copied data that is in any node with this name, store the result in fourth column associated with XML file's row.
  • Rule 3: Select FirstSalesReport/“SaleDate,” copy data here, store data here into fifth column of row associated with XML file's row.
  • Rule 4: Select FirstSalesReport/“Quality,” copy data here, store data here into sixth column of row associated with XML file's row.

Starting with Rule 1, the promotion application 322 finds any nodes of the XML file indicated by the FirstSalesReport/“Customer” with an XPath expression (which is included in the rules file 320). In this case there is only one node with this name, so the promotion application 322 copies data within the node, here “ACME Tire Co.” and copies it into the correct column (for the sales report 404 it is the first row of the third column of the table 402 show in FIG. 6). The promotion application 322 uses an OLEDB (Object Linking and Embedding to DataBase) mapping to store the data in the correct column and row of the table 402. The result is shown in this field of promoted table 402 of FIG. 8.

If the promotion application 322 finds multiple nodes with the XPath given and no function is to be performed on the data copied from the nodes, the promotion application 322 copies the data from the first node and adds it into the table 402.

For Rule 2, the promotion application 322 finds any nodes of the XML file indicated by the FirstSalesReport/Product/“ProductPriceTotal” with an)(Path expression. In this case there are three nodes with this name, so the promotion application 322 copies data from all three of the nodes. The data in the nodes is: 580.50; 659.04; and 102.96 (shown in FIG. 7 at references 716, 724, and 732). The promotion application 322 follows the function in the Rule 2 (here to add the data from each of the nodes). The promotion application 322 adds the data together for a total of 1,342.50. The promotion application 322 then copies the result of the function, here 1,342.50 into the correct column (for the sales report 404 it is the first row of the fourth column of the table 402 shown in FIG. 6). Again the promoting application 322 uses an OLEDB mapping. The result is shown in this field of promoted table 402 of FIG. 8.

For Rule 3, similar to Rule 1, the promotion application 322 finds any nodes of the XML file indicated by the FirstSalesReport/“SaleDate” with an) (Path expression. There is only one node with this name, so the promotion application 322 copies data within the node, here “Mar. 13, 2000”, and copies it into the correct column. Again, see the promoted table 402 of FIG. 8.

For Rule 4, similar to Rules 1 and 3, the promotion application 322 finds any nodes of the XML file indicated by the FirstSalesReportl“Quality” with an) (Path expression. There is only one node with this name, so the promotion application 322 copies data within the node, here “Satisfied”, and copies it into the correct column. Again, see the promoted table 402 of FIG. 8.

Demoting

If desired, the demoting application 324, which can be part the promoting application 322 (such as a sub-application), can demote data from the library 310 into the XML file.

In this implementation, if the user makes any change to a field in the advanced properties of the library 310, the web server 312 will prompt the user to determine if the user wants the change demoted to the XML file. If so, the demotion application 324 can make this demotion.

At block 1114, the server 302 receives a change to a field in the advanced properties. Before continuing, the server 302 receives instructions (such as from the user 314 after a prompt from the demotion application 324) to demote the new data.

At block 1116, the demotion application 324 copies the new data from the change made to the field in the advanced properties.

From one of the above examples, assume that the sales manager changes the first row of the customer-name advanced property 602 from “ACME Tire Co.” to “VICTORY Tire Co.” (shown in FIGS. 8 and 9). Then, at block 1116, the demotion application 324 copies “VICTORY Tire Co.” The demotion application 324 can then communicate with the promotion application 322 to determine which node of which file is related to the change (such as with: FirstSalesReport/“Customer”). This may be with an)(Path expression, as above, when the structured data file comprises XML.

At block 1118, the demotion application 324 finds the correct node(s) of the correct file (here relating to the customer-name field 704 of the first sales report 404 of FIG. 7) with an XPath expression. The demotion application 324 then replaces the data within that node or nodes with the new data. This is shown in the demoted example of the customer-name field 704 shown in FIG. 10.

CONCLUSION

The above-described tool enables a user to promote data from within a structured data file. It can also enable a user to demote data from a library or other file into a structured data file. Although the invention has been described in language specific to structural features and/or methodological acts, it is to be understood that the invention defined in the appended claims is not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as exemplary forms of implementing the claimed invention.