WO2005033980A1 - Systeme, procede et appareil d'importation de donnees texte dans une base de donnees - Google Patents

Systeme, procede et appareil d'importation de donnees texte dans une base de donnees Download PDF

Info

Publication number
WO2005033980A1
WO2005033980A1 PCT/US2004/032188 US2004032188W WO2005033980A1 WO 2005033980 A1 WO2005033980 A1 WO 2005033980A1 US 2004032188 W US2004032188 W US 2004032188W WO 2005033980 A1 WO2005033980 A1 WO 2005033980A1
Authority
WO
WIPO (PCT)
Prior art keywords
attributes
spreadsheet
control file
data
rule
Prior art date
Application number
PCT/US2004/032188
Other languages
English (en)
Inventor
Atul Gupta
Amar Singh
Original Assignee
Schlumberger Holdings Limited
Schlumberger Canada Limited
Services Petroliers Schlumberger
Schlumberger Technology Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Schlumberger Holdings Limited, Schlumberger Canada Limited, Services Petroliers Schlumberger, Schlumberger Technology Corporation filed Critical Schlumberger Holdings Limited
Priority to MXPA06003684A priority Critical patent/MXPA06003684A/es
Priority to CA2540812A priority patent/CA2540812C/fr
Priority to EP04793918A priority patent/EP1671248A1/fr
Priority to GB0608392A priority patent/GB2423391A/en
Priority to EA200600651A priority patent/EA010400B1/ru
Publication of WO2005033980A1 publication Critical patent/WO2005033980A1/fr
Priority to NO20061923A priority patent/NO339507B1/no

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/21—Design, administration or maintenance of databases

Definitions

  • This invention relates to methods and systems for use in computer software having databases.
  • the invention provides methods, apparatuses and systems for more effectively and efficiently loading text data into a database.
  • a database as a repository for storing data.
  • databases include Oracle, SQL Server, Sybase, to name a few.
  • the data is stored in relational database tables in a pre-defined schema.
  • the data can be created in the database using GUIs, such as for example Oracle Forms, by manual entry or, most often, by the user loading the data in the database using a software program, such as Loader.
  • An external storage unit such as a disk file or a tape that contains the data to be loaded (“dataset”) is usually encoded in binary or text (ASCII) format. If a software loading program is being used to load the dataset, the loading program reads the dataset, decodes the encoding and loads it in the database tables. This is a very common scenario for software used, for , example, in the oil and gas industry where the need is for data to be loaded in various industry standard formats, such as DLIS, Geoshare, ITSML, to name a few: These standard formats are in bin.ary, XML or ASCII. Therefore, for such industry data in standard formats, "custom" loaders are written to load the data.
  • ASCII binary or text
  • the custom loaders read a specific format and load (create/update) data in a specific repository.
  • GeoFrame DLIS Loader reads DLIS data and loads data in GeoFrame repository only.
  • an object of the present invention is to provide improved methods, apparatuses and systems for loading data, especially in non-standard text files, into a database while eliminating or minimizing the impact of the problems and limitations described.
  • the data in the spreadsheet dataset may be row-based data or column-based data
  • a preferred embodiment of the present invention includes a control file containing a set of rules, each rule having a condition, and a spreadsheet loader having as inputs the spreadsheet dataset and the control file. Each rule in the control file is evaluated for each record to determine if the condition is true for the record, and the records are parsed if the condition is true.
  • the spreadsheet loader sends the parsed data to the database.
  • the set of rules within the control file may include a variable rule, an entity rule or both (including but not limited to a plurality of both).
  • the variable rule comprises a condition, a parsedescriptor, .and a values clause and may include an endcondition and/or an attributelist.
  • the entity rule is comprised of a condition and an attributelist and may include an endcondition clause and/or a referenceentity clause.
  • the invention may also include a user interface used to create the control file.
  • the user interface may include a control file information section, having .an object tree, attributes tab, and control file preview area, and a data file information section, having a spreadsheet data area reflecting the spreadsheet dataset, Using the user interface, selecting a business object in the object tree opens a list of one or more attributes for the business object in the attributes tab. Attributes from the open list of attributes may be dragged and dropped into columns in the spreadsheet data area; and the spreadsheet dataloader uses the attributes dropped into the spreadsheet data area to map the columns to the business objects and to create the control file from the mapping.
  • the control file may be previewed in a control file preview area in the user interface.
  • Attributes in the attribute tab that are mandatory for the selected business object may distinguished from attributes that are not mandatory, such as with a color, shading, or use of a special font.
  • the spreadsheet data area of the user interface may include editing functions.
  • the object tree may display the business objects using a two-tier hierarchy, with a list of sub models (being groups of business objects), and with business objects under each sub model.
  • the invention may also include a data access layer in the database which allows entity definitions and persistence maps to be used to create new business objects in the object tree.
  • Attributes of the business objects are defined on the database.
  • the attributes may be evaluated using a valueexpr clause and may be parsed using a pasedescritpor command and the value of the parsed attribute is referenced using a value clause.
  • a preferred embodiment of the invention includes a method for loading data from a spreadsheet dataset, having data in the form of one or more records, into a database including the steps of creating a control file having rules, each rule including a condition; inputting the spreadsheet dataset and the control file into a spreadsheet loader; evaluating each rule with respect to each record to determine if the condition for the rule is true for that record .and if the condition is true, then posing the record into one or more tokens .and referencing the value of the parsed record using a value clause of the rule and sending the parsed, valued data to the database.
  • Creating a control file may include the steps of: by using a user interface for a spreadsheet loader, selecting a business object in an object tree section of the user interface, so the selection of the business object opens a list of attributes for the selected business object in an attributes tab section of the user interface, dragging and dropping the attributes for the selected business object into columns of a spreadsheet data area of the user interface, the spreadsheet data area reflecting a spreadsheet dataset that is to be loaded by the spreadsheet loader, using trie drop and dragged attributes to map the columns into which the attributes were dragged to the business objects of the dragged attributes, and generating a control file reflecting the mapping step. Further, one may preview the generated control file in a control file preview area of the user interface.
  • Attributes in the attribute tab that are mandatory for the selected business object may distinguished from attributes that are not mandatory, such as with a color, shading, or use of a special font.
  • the spreadsheet data area of the user interface may include editing functions.
  • the object tree may display the business objects using a two-tier hierarchy, with a list of sub models (being groups of business objects), and with business objects under each sub model.
  • the rules of the control file may include a variable rule, an entity rule or both.
  • the variable rule includes a condition, a parsedescriptor, and a values clause and may include an endcondition and/or an attributelist.
  • the entity rule includes a condition and an attributelist and may include an endcondition clause and/or a referenceentity clause.
  • the invention may include a data access layer in the database allowing entity definitions and persistence maps to be used to create new business objects in the object tree.
  • the attributes are defined on the database, and may be evaluated using a valueexpr clause, may be parsed using a pasedescritpor command and the value of the parsed attribute may be referenced using a value clause.
  • a prefened embodiment of the invention includes a system for loading data from a spreadsheet dataset (having data in the form of one or more records) into a database.
  • the system includes a control file having rules, each rule including a condition, a spreadsheet loader having inputs of the spreadsheet dataset and the control file.
  • the spreadsheet loader has a program storage device readable by a machine, tangibly embodying a program of instructions executable by the machine to perform the following method steps: evaluating each rule with respect to each record to determine if the condition for the rule is true for that record and if the condition is true, then parsing the record into one or more tokens and referencing the value of the parsed record using a value clause of the rule, and sending the parsed, valued data to the database.
  • the control file of the system of this embodiment of the invention may be created by the following steps: Using a user interface for a spreadsheet loader to select a business object in an object tree section of the user interface, where the selection of the business object opens a list of attributes for the selected business object in an attributes tab section of the user interface, dragging and dropping the attributes for the selected business object into columns of a spreadsheet data area of the user interface, the spreadsheet data area reflecting a spreadsheet dataset that is to be loaded by the spreadsheet loader, mapping the columns into which the attributes were dragged to the business objects of the dragged attributes by using the drop and dragged attributes, and generating a control file reflecting the mapping step.
  • the generated control file may be previewed in a control file preview area of the user interface.
  • the set of rules within the control file may include a variable rule having a condition, a parsedescriptor, and a values clause and may include an entity rule, having a condition and an attributelist.
  • Attributes in the attribute tab that are mandatory for the selected business object may distinguished from attributes that are not mandatory, such as by color, by shading, or by a special font. They could also be distinguished by sound for visually impaired users. Editing functions may be performed using the spreadsheet data area of the user interface.
  • the object tree may display the business objects using a two-tier hierarchy, with a list of sub models, being groups of business objects, followed by business objects under each sub model.
  • the invention may include a data access layer in the database. The data access layer may allow entity definitions and persistence maps to be used to create new business objects in the object tree. Attributes are defined on the database. Attributes may be evaluated using a valueexpr clause. Attributes may be parsed using a pasedescritpor command and the value of the parsed attribute referenced using a value clause
  • An advantage of the present invention is that it provides a simple interface for loading all spreadsheet text data into a database.
  • Another advantage of the present invention is that it loads any text data whose layout is in spreadsheet format.
  • FIG. 1 illustrates inputs coming into a spreadsheet loader of a preferred embodiment of the present invention.
  • FIG. 2 is a block diagram illustrating the schema for entity rules and variable rales of a preferred embodiment of the present invention.
  • FIG. 3 is a block diagram that depicts further detail for the variable rule in a preferred embodiment of the present invention.
  • FIG. 4 is a block diagram that depicts further detail for the entity rule in a preferred embodiment of the present invention.
  • FlG. 5 is a block diagram that depicts further detail for attributes in a preferred embodiment of the present invention. .
  • FlG. 6 is a block diagram of a spreadsheet loader user interface for a preferred embodiment of the present invention.
  • FlG. 7 is a block diagram of a preferred embodiment of the present invention.
  • FlG. 8 is a block diagram of a spreadsheet dataset of a preferred embodiment of the present invention.
  • FlG. 9 is a block diagram of control file of a preferred embodiment of the present invention.
  • FIG. 10 is a flow chart of a preferred embodiment of the present invention.
  • FlG. 11 is a flow chart of how to create a control file in a prefened embodiment of the present invention.
  • FIG. 1 illustrates inputs coming into a spreadsheet loader 10 of a preferred embodiment of the present invention.
  • the spreadsheet loader 10 of this prefened embodiment has two inputs: a spreadsheet dataset 20, containing a dataset of data, and a control file 30 and the spreadsheet loader 10 outputs data into a database 35.
  • a spreadsheet dataset 20 may be read by this preferred embodiment of the invention in two ways: as a sequence of rows ("row-based data") or as a sequence of columns ("column- based data"). Refening to FlG.8, each entry in the spreadsheet dataset is called a record 21. There is a difference in the way the data is processed by the spreadsheet loader 10 for each of the two ways of reading a spreadsheet, as described below.
  • Row-based data Data in each row represents one or more business objects.
  • a business object is an entity, such as a well in the exploration and production ("E&P") domain.
  • Each column represents an attribute of the business object.
  • the attributes are used to describe some aspect of the business object.
  • attributes are usually separated by a special character, e.g. comma (,), pipe (
  • the above row describes a well object with the following attributes: the name of the well, uwi (unique well identifier), "drill_total_depth” (total measured depth), true vertical depth (tvd), and spud_date (the date that drilling of the well began). So in the row above, the well object and its attributes are:
  • the business objects are Log Channels and one such business object is RHOB.
  • DEPT stands for depth and the other column n.ames for different logging measurements: RHOB stands for Bulk Density, SP for Spontaneous Potential, GR for Gamma Ray, POR for Porosity, DEN for Density and PER for Photoelectric Factor, Right.
  • RHOB stands for Bulk Density
  • SP for Spontaneous Potential
  • GR Gamma Ray
  • POR Porosity
  • DEN Density
  • PER Photoelectric Factor
  • the control file 30 contains a set of rules 100.
  • the rales 100 may be defined in any language that the spreadsheet loader 10 understands.
  • the control file rales are described in XML.
  • Each control file rale 100 describes how to p.arse and map the data in the spreadsheet dataset.
  • Each rule 100 has a condition that has to be true for the rale to be evaluated. Conditions are discussed further below, with reference to FlG. 3 and FlG. 4.
  • FlG. 2 is a block diagram illustrating the schema for rales in a prefened embodiment of the present invention. As illustrated in FlG.
  • variable rales 110 there are two main types of rules 100 in this prefened embodiment of the present invention: variable rales 110 and entity rales 120.
  • Variable Rule 110 The variable rale is used to read a token.
  • a token is a string or a number read from the data record as described by a parse string.
  • the variable rale reads the token from data in the form of an input text file and stores it as a variable to be used later, in either an entity rule 120 or in a condition of another rule. More information on variable rules is illustrated in FlG. 3 (and discussed below).
  • Entity Rule 120 describes an entity, an object that is to be created.
  • the entity rale 120 lists attributes of the object and describes how the attributes are set, using a variable rule 110 or the token, which is read from the input text file. More details on entity rules are illustrated in FlG. 4 (and discussed below). [00033]
  • the symbol depicted in FlG. 2 to the right of the rules 100 (and to the left of branches leading to the variable rale 110 and entity rule 120) is an aggregate 122 and means one or many entity or variable rales comprise a set of rules.
  • control file 30 that reads the row-based data as shown in EXAMPLE 1 above.
  • FIG. 3 is a block diagram that depicts further detail for the variable rule 110 in a prefened embodiment of the present invention.
  • Variable rules 110 are evaluated based upon conditions processed from each record in the spreadsheet dataset.
  • the symbol to trie right of the variable rule 110 in FlG. 3 is a sequence 124 and means the variable rule is constructed as a sequence of a condition 125, a parsedescriptor 130, a values clause 135 and may (optionally) include an endcondition 140 and an attributelist 145.
  • a condition 125 is a logical state that must evaluate to true if a variable rule (or entity rale as discussed below) is to be processed.
  • the variable rale 110 may include expressions in the condition. .
  • An expression describes data, variables or entities.
  • the parsedescriptor 130 is used to parse the record by breaking it into either a single token or an anay of tokens.
  • the value of the parsed dataset is referenced using a value clause 135.
  • the value clause 135 is an expression that references which of the tokens parsed using the parsedescriptor 130 is assigned a value for a variable or an attribute and is referenced in- other expressions by name.
  • The- optional endcondition 140 is an expression that allows specifying whether a variable or entity is to be continually evaluated for subsequent data records - in the case of continual evaluation, the endcondition 140 in the prefened embodiment of the invention will evaluate to trae.
  • the optional attribute list 145 is a list of attributes that may be assigned values 135 for a given entity.
  • FIG. 4 is a block diagram that depicts further detail for the entity rule 120 in a prefened embodiment of the present invention.
  • the symbol to the right of the entity rale 120 in FlG. 4 is a sequence 124 and means that an entity rule 120 is comprised of condition 125 and attributelist 145 and optional endcondition 140 and referenceentity 155 clauses.
  • the optional referenceentity 155 is a list of one or more entities that are referenced by the current entity.
  • the referenceentity 155 is used to establish the relational reference between the current entity and other entities being processed by the spreadsheet loader.
  • FIG. 5 is a block diagram that depicts further detail for attributes 2O0 in a prefened embodiment of the present invention.
  • Attributes 200 refer to aspects of a business object and are defined on the database into which the spreadsheet loader will load the data.
  • the attributes 200 are evaluated as a valueexpr 210 or a parsedescriptor 220 and a value clause 230.
  • the valueexpr 210 is a simple expression or a constant value that is assigned to the attribute.
  • an attribute 200 is an expression
  • the value for the attribute 200 is evaluated by the valueexpr 210.
  • the parsedescriptor command 220 is used to parse the data record by breaking it into either a single token or an array of tokens.
  • the value of the parsed data record is referenced using the value clause 230.
  • Some attributes 200 are mandatory for business objects because the attributes 200 are required to be present to create the business object in the relational database (non-null columns). Other attributes are not mandatory.
  • FIG. 6 is a block diagram of a user interface 300 of the spreadsheet loader in a prefened embodiment of the present invention, which is used to build the control file. (The operation of the user interface 300 is also further illustrated in FlG. 7 and discussed below.) Refening to FlG. 6, the user interface 300 has two main panels, the Control File Information panel 305 and the Data File Information panel 310.
  • the Control File Information panel 305 has three areas: an object tree area 315, an attributes tab area 320 and a control file preview area 325.
  • the object tree area 315 displays the business objects (not depicted) as supported by the database (not depicted in FlG. 6).
  • the definition of the business objects is preferably described in XML.
  • the object tree area 315 is preferably displayed in a two-tier hierarchy, with a list of Sub Models (not depicted) and then the business objects (not depicted) under each Sub
  • the Sub Models are a grouping of business objects. For example, in E&P domain, there could a Well Sub Model that consists of all Well-related entities/objects.
  • the attributes tab area 320 displays the attributes (not depicted) of the selected business objects.
  • the data file information panel 310 has a spreadsheet data area 340.
  • the spreadsheet data area 340 displays the data from the spreadsheet dataset 20.
  • the spreadsheet data .area 340 includes basic edit operations.
  • control file preview area 325 of the control file information panel 305 displays a control file as it is built when the user maps the attributes to columns in the spreadsheet dataset, as reflected in the spreadsheet data area 340.
  • FlG. 7 is a block diagram of a prefened embodiment of the present invention. It can be difficult to create a control file and the user interface 300 can be used to facilitate this. Refening to FlG. 7, in order to create the control file 30, the user uses the user interface 300 to map the columns in the spreadsheet dataset 20, as reflected in the spreadsheet data area 340 of the user interface 300, to the attributes of one or more business objects in the object tree 315 by using a drag and drop feature of the user interface 300.
  • the user may select a business object in the object tree 315, a list of the attributes of the selected business object will open in the attribute tab 320 and the user may drop and drag the attribute name into a column in the spreadsheet data area 340, which reflects the spreadsheet dataset 20.
  • the spreadsheet loader 10 maps the attribute name to the spreadsheet data area 340 and generates a control file rule (which can be previewed in the control file preview area 325). Once the mapping is completed, the user may load the data into the database 35 using the spreadsheet loader 10.
  • the user may also define new business objects in the object tree 315, by adding entity definitions and persistence maps (for example, in XML) to be used by a generic data access layer (not depicted in FlG. 7) for the database 35.
  • Entity definitions (not to be confused with entity rules) are descriptions of database objects.
  • Persistence maps are rules that describe, for the data access layer, how the data is written to the database 35 or to some other repository, such as a flat file
  • the spreadsheet loader 10 may pick the entity definitions in the object tree area 315 and the user can use a high level view for mappings.
  • FlG. 10 depicts a flowchart for a prefened embodiment of the present invention.
  • a control file having rules, each rule including a condition.
  • a method for creating a control file is illustrated in FlG. 11, discussed below, as v ell as in the discussion above with respect to FIG. 6 and FIG. 7.
  • a spreadsheet dataset, having data in the form of records, and the control file are inputted 410 into a spreadsheet loader.
  • Each rule of the control file is evaluated 415 for each record found in the dataset to determine 420 if the condition for the rule is true for that record. If 425 the condition is not trae, all the other rules for that record are evaluated 430, until complete.
  • the record is parsed 435 into one or more tokens.
  • the value of the parsed record is referenced 440 using a value clause. If all the rales have not been evaluated for the record 425, then evaluate 430 all other rules until complete, and then evaluate 445, 450 rules for all other records until complete. Once all rules for a record are completely evaluated, the parsed, valued data is loaded 455 into a database and the process ends 460.
  • rules may be variable rales or entity rules.
  • a rule may have an endcondition that evaluates to true if the rule is to be continually evaluated for subsequent data records.
  • an entity rule will have attributelist for the entity and may have a referenceentity used to establish the relational reference between the cunent entity and other entities.
  • FIG. 11 depicts a flowchart for how to create a control file in a preferred embodiment of the present invention.
  • a business object in an object tree section of the user interface
  • the attributes for the business object are dragged and dropped 510 into columns of a spreadsheet data area of the user interface, the spreadsheet data area reflecting a spreadsheet dataset that is to be loaded by the spreadsheet loader.
  • the spreadsheet loader maps 515 the columns into which the attributes were dragged to the business objects of the dragged attributes.
  • the spreadsheet loader generates 520 a control file reflecting the mapping step 515, and allows the control file to be previewed 525 in a control file preview area of the user interface. If 530 all business objects have not been mapped, the next business object is selected 535 and the process repeats, until complete 540.
  • the present invention solves the problem of inserting/ updating/ overvrating data coming in ASCII spreadsheet (including excel files) in a generic way. While loading data, the present invention hides the complexity of the target database from the end user .and resolves any relationship (using the ReferencedEntity clause) among the business objects, totally transparent to the user.
  • the present invention may be used to load in any target repository provided the generic data access layer supports a target adapter.
  • the present invention may also be used to create business objects in memory for direct use by applications.
  • the front end of spreadsheet loader which reads data as business objects (which can be defined by the user) from spreadsheet data file, may allow the user perform mapping using a generic user interface. This approach could also be used to load the data in memory in the user defined business objects for direct use by applications.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • User Interface Of Digital Computer (AREA)

Abstract

La présente invention concerne un appareil, un procédé et un système de chargement de données dans une base de données. L'invention concerne un ensemble de données sous forme de feuille de calcul, présentant des données sous forme d'un ou plusieurs enregistrements, un fichier de commande contenant un ensemble de règles, chaque règle ayant une condition et un chargeur de feuille de calcul. L'ensemble de données sous forme de feuille de calcul et le fichier de commande sont désaisis vers le chargeur de feuille de calcul. Chaque règle dans le fichier de commande est évaluée pour chaque enregistrement afin de déterminer si la condition est vraie pour l'enregistrement et les enregistrements sont analysés si la condition est vraie. Le chargeur de feuille de calcul envoie les données analysées vers la base de données. L'invention concerne une interface utilisateur permettant de faciliter la création du fichier de commande.
PCT/US2004/032188 2003-10-01 2004-10-01 Systeme, procede et appareil d'importation de donnees texte dans une base de donnees WO2005033980A1 (fr)

Priority Applications (6)

Application Number Priority Date Filing Date Title
MXPA06003684A MXPA06003684A (es) 2003-10-01 2004-10-01 Un sistema, un metodo y un aparato para importar datos de texto en una base de datos.
CA2540812A CA2540812C (fr) 2003-10-01 2004-10-01 Systeme, methode et dispositif d'importation de donnees texte dans une base de donnees
EP04793918A EP1671248A1 (fr) 2003-10-01 2004-10-01 Systeme, procede et appareil d'importation de donnees texte dans une base de donnees
GB0608392A GB2423391A (en) 2003-10-01 2004-10-01 A system, a method and an apparatus for importing text data in a database
EA200600651A EA010400B1 (ru) 2003-10-01 2004-10-01 Система, способ и устройство для загрузки текстовых данных в базу данных
NO20061923A NO339507B1 (no) 2003-10-01 2006-04-28 Fremgangsmåte, anordning og system for import av tekstdata til en database

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US50757603P 2003-10-01 2003-10-01
US60/507,576 2003-10-01

Publications (1)

Publication Number Publication Date
WO2005033980A1 true WO2005033980A1 (fr) 2005-04-14

Family

ID=34421635

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2004/032188 WO2005033980A1 (fr) 2003-10-01 2004-10-01 Systeme, procede et appareil d'importation de donnees texte dans une base de donnees

Country Status (7)

Country Link
EP (1) EP1671248A1 (fr)
CA (1) CA2540812C (fr)
EA (1) EA010400B1 (fr)
GB (1) GB2423391A (fr)
MX (1) MXPA06003684A (fr)
NO (1) NO339507B1 (fr)
WO (1) WO2005033980A1 (fr)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090187453A1 (en) * 2008-01-17 2009-07-23 Stephen Dill Method for evolving shared to-do lists into business processes
US7685152B2 (en) 2006-01-10 2010-03-23 International Business Machines Corporation Method and apparatus for loading data from a spreadsheet to a relational database table
US7849108B1 (en) * 2007-03-13 2010-12-07 Fundriver, Inc. Methods and systems for establishing a database
EP2979199A4 (fr) * 2013-03-29 2016-04-06 Services Petroliers Schlumberger Transfert de contexte pour un stockage de données
US9489386B2 (en) 2014-03-19 2016-11-08 International Business Machines Corporation Inferred operations for data analysis

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020046248A1 (en) * 2000-10-13 2002-04-18 Honeywell International Inc. Email to database import utility
US20030130878A1 (en) * 2001-10-23 2003-07-10 Kruk Jeffrey M. System and method for managing spending

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020046248A1 (en) * 2000-10-13 2002-04-18 Honeywell International Inc. Email to database import utility
US20030130878A1 (en) * 2001-10-23 2003-07-10 Kruk Jeffrey M. System and method for managing spending

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
ANONYMOUS: "ORACLE WAREHOUSE BUILDER: A TECHNICAL OVERVIEW", ORACLE TECHNICAL WHITE PAPER, XX, XX, 2000, pages 1 - 21, XP002249154 *
CHAMBERLIN D: "A complete guide to DB2 universal database", COMPLETE GUIDE TO DB2 UNIVERSAL DATABASE, XX, XX, 1998, pages 1 - 35, XP002239913 *
RAHM E AND DO H-H: "Data Cleaning: Problems and Current Approaches", QUARTERLY BULLETIN OF THE COMPUTER SOCIETY OF THE IEEE TECHNICAL COMMITTEE ON DATA ENGINEERING, THE COMMITTEE, WASHINGTON, DC,, US, December 2000 (2000-12-01), pages 1 - 11, XP002284896, ISSN: 1053-1238 *

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7685152B2 (en) 2006-01-10 2010-03-23 International Business Machines Corporation Method and apparatus for loading data from a spreadsheet to a relational database table
US7849108B1 (en) * 2007-03-13 2010-12-07 Fundriver, Inc. Methods and systems for establishing a database
US20090187453A1 (en) * 2008-01-17 2009-07-23 Stephen Dill Method for evolving shared to-do lists into business processes
US9922295B2 (en) * 2008-01-17 2018-03-20 International Business Machines Corporation Method for evolving shared to-do lists into business processes
EP2979199A4 (fr) * 2013-03-29 2016-04-06 Services Petroliers Schlumberger Transfert de contexte pour un stockage de données
US9626392B2 (en) 2013-03-29 2017-04-18 Schlumberger Technology Corporation Context transfer for data storage
US9489386B2 (en) 2014-03-19 2016-11-08 International Business Machines Corporation Inferred operations for data analysis
US9606997B2 (en) 2014-03-19 2017-03-28 International Business Machines Corporation Inferred operations for data analysis

Also Published As

Publication number Publication date
NO20061923L (no) 2006-06-30
NO339507B1 (no) 2016-12-27
EA010400B1 (ru) 2008-08-29
EA200600651A1 (ru) 2007-10-26
GB2423391A (en) 2006-08-23
EP1671248A1 (fr) 2006-06-21
MXPA06003684A (es) 2007-03-26
CA2540812A1 (fr) 2005-04-14
GB0608392D0 (en) 2006-06-07
CA2540812C (fr) 2011-01-25

Similar Documents

Publication Publication Date Title
US9213950B2 (en) Method and system for managing a plurality of processes or tasks
US7822795B2 (en) Apparatus and methods for displaying and determining dependency relationships among subsystems in a computer software system
EP1922641B1 (fr) Interface utilisateur pour la creation de table recapitulative de donnees de feuille de calcul
RU2417421C2 (ru) Автоматическое размещение полей в сводной таблице данных
US8326888B2 (en) Method and apparatus for oilfield data repository
US7542979B2 (en) System, method and apparatus for loading text data in a database
US8010909B1 (en) Derived hierarchy methods and system for definition, visualization and editing of data
EP2857962A1 (fr) Filtrage d'interface utilisateur pour une table récapitulative de données
RU2406115C2 (ru) Доступ к сложным данным
CA2558825A1 (fr) Systeme et procede de transformation et d'utilisation d'un contenu dans d'autres systemes
EP2396753A1 (fr) Constructeur etl
US20220335212A1 (en) Data visualization with derived dimensional hierarchy
US20130232158A1 (en) Data subscription
CA2540812C (fr) Systeme, methode et dispositif d'importation de donnees texte dans une base de donnees
GB2479654A (en) Subscription based retrieval from oil field database
CN112580140B (zh) 基于bim三维地质模型快速更新地质属性系统及方法
Fouché et al. Foundations of SQL server 2008 R2 business intelligence
Ibrahim et al. A Tree Method for Managing Documents in Mongodb
Alder GEMFORM: Forestry software for stand tables and yield projections in Guyana
AU2010347724B2 (en) Dynamic grouping of domain objects via smart groups
CA2540818C (fr) Procede, systeme et appareil pour acceder a des donnees geographiques stockees
Juggins TRAN (version 1.8) and ZONE (version 1.2) user manual
WO2022221585A1 (fr) Visualisation de données avec hiérarchie dimensionnelle dérivée
Albano et al. DBU+ A Geoscience Integrated Tool
AU2005246942A1 (en) Method and System for Merging and Visualising Metadata

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
WWE Wipo information: entry into national phase

Ref document number: 2540812

Country of ref document: CA

WWE Wipo information: entry into national phase

Ref document number: PA/a/2006/003684

Country of ref document: MX

Ref document number: 1117/CHENP/2006

Country of ref document: IN

WWE Wipo information: entry into national phase

Ref document number: 200600651

Country of ref document: EA

WWE Wipo information: entry into national phase

Ref document number: 0608392

Country of ref document: GB

WWE Wipo information: entry into national phase

Ref document number: 2004793918

Country of ref document: EP

WWP Wipo information: published in national office

Ref document number: 2004793918

Country of ref document: EP

ENPC Correction to former announcement of entry into national phase, pct application did not enter into the national phase

Ref country code: GB