IP Library Granted Patent US 10,380,138
Granted Patent B1
US 10,380,138 · App. 15/292,078 · Granted Aug 13, 2019

Systems and methods for importing data from electronic data files

Inventors: Stephen Yazicioglu (McLean, VA); Christopher Luck (Washington, DC); Robert Giardina (Falls Church, VA); Justin Streufert (Germantown, MD); Timothy Slatcher (London, GB); Gregory O'Connor (London, GB); Brandon Marc-Aurele (Arlington, VA); Olivia Zhu (Saratoga, CA); Howard Schindel (Washington, DC); Henry Tung (Palo Alto, CA); Lucas Ray (San Francisco, CA); Christopher Leech (Pittsburgh, PA); Eric Jeney (Metuchen, NJ); Stefan Negrus (Washington, DC); Jason Lee (Berkeley, CA); Alessandro Mingione (London, GB); John McKinstry Doyle (Washington, DC); Hunter Pitelka (Arlington, VA); Ethan Lozano (Los Altos Hills, CA); Joel Ossher (Vienna, VA); Matthew Fedderly (Baltimore, MD)
Assignee: Palantir Technologies Inc.
G06F16/258G06F16/22G06F16/245G06F16/86
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,380,138
App. No.
15/292,078
Granted
Aug 13, 2019
Kind
B1
Abstract

Computer implemented systems and methods are disclosed for importing data from electronic data files. In accordance with some embodiments, a file format is assigned to a source electronic data files by a data importation system. The data importation system may further identify a file type identifier associated with the source electronic data file and map the source electronic data file to a transformation template. The data importation system may further store the file format, file type identifier, and an indication of the transformation template as a file type profile associated with the source electronic data file in a database.

Claims (41)

1. A system comp rising:

one or more memory devices that store a set of instructions;

at least one processor that executes the set of instructions to perform operations for generating a transformed source electronic data file from a source electronic data file based on inputs received from an interactive mapping graphical user interface presented on a client device, the interactive mapping graphical user interface facilitating a mapping of a format of the source electronic data file to a canonical format included in a transformation template, the operations comprising:

detecting that a file type associated with the source electronic data file is an unknown file type;

providing for a selection of the transformation template via the interactive mapping graphical user interface for associating with the file type;

generating the interactive mapping graphical user interface for presentation on the client device, the interactive mapping graphical user interface including interactive user interface elements for combining data fields in the source electronic data file and mapping the combined data fields to a canonical data field included in the transformation template;

generating the transformed source electronic data file from the source electronic data file based on mappings received via the interactive mapping graphical user interface presented on the client device; and

storing the mappings as a file type profile in a database for subsequent use in importing updates of additional source electronic data files of the file type into a data analysis system without user intervention.

2. The system of claim 1 , wherein the detecting of the file type is based on properties of the source electronic data file.

3. The system of claim 1 , wherein the operations further include receiving an assignment of the transformation template to the source electronic data file via the interactive mapping graphical user interface.

4. The system of claim 1 , wherein the detecting of the file type includes determining file type identifier associated with the source electronic data file, the file type identifier including at least one of a structure of the source electronic data file, a combination of file headers included in the source electronic data file, and an order of file headers included in the source electronic data file.

5. The system of claim 1 , wherein the detecting of the file type includes determining a file type identifier associated with the source electronic data file, the file type identifier including at least one of a string of text included in the source electronic data file and a type of data included in the source electronic data file.

6. The system of claim 1 , wherein the detecting of the file type identifier associated with the source electronic data file includes receiving an identification of the file type identifier associated with the source electronic data file as user input via the interactive mapping graphical user interface.

7. The system of claim 1 , wherein the generating of the transformed source electronic data file includes conforming a format of the data fields included in the source electronic data file to a format of the canonical data fields included in the transformation template.

8. The system of claim 1 , the operations further comprising:

receiving an up date as an up dated electronic source data file;

loading a detector/transformer plugin from a detector/transformer plugin database based on a file type of the up dated electronic source data file;

using the detector/transformer plugin to generate an updated transformed electronic data file based on data included in the update and replace the transformed electronic data file with the updated transformed electronic data file.

9. The system of claim 8 , the operations further comprising selecting the detector/transformer plugin from a plurality of detector/transformer plugins based on a priority of the detector/transformer plugin being higher than priorities of other detector/transformer plugins of the plurality of detector/transformer plugins.

10. The system of claim 1 , wherein the data fields in the source electronic data file represent bank wire transfer data and the combined data fields include a first field for a date and a second field for a time.

11. The system of claim 1 , wherein the canonical field defines an arrangement of content in the canonical field and the interactive mapping graphical user interface includes elements for mapping an arrangement of content in the combined data field with the arrangement of content in the canonical field.

12. A method comprising:

incorporating one or more instructions into one or more memory devices, the one or more instructions configuring one or more computer processors to perform operations for generating a transformed source electronic data file from a source electronic data file based on inputs received from an interactive mapping graphical user interface presented on a client device, the interactive mapping graphical user interface facilitating a mapping a format of the source electronic data file to a canonical format included in a transformation template, the operations comprising:

detecting that a file type associated with the source electronic data file is an unknown file type;

providing for a selection of the transformation template via the interactive mapping graphical user interface for associating with the file type;

generating the interactive mapping graphical user interface for presentation on the client device, the interactive mapping graphical user interface including interactive user interface elements for combining data fields in the source electronic data file and mapping the combined data fields to a canonical data field included in the transformation template;

generating the transformed source electronic data file from the source electronic data file based on mappings received via the interactive mapping graphical user interface presented on the client device; and

storing the mappings as a file type profile in a database for use in automatically transforming additional source electronic data files of the file type without user intervention.

13. The method of claim 12 , wherein the detecting of the file type is based on properties of the source electronic data file.

14. The method of claim 12 , wherein the operations further include receiving an assignment of the transformation template to the source electronic data file via the interactive mapping graphical user interface.

15. The method of claim 12 , wherein the detecting of the file type includes determining file type identifier associated with the source electronic data file, the file type identifier including at least one of a structure of the source electronic data file, a combination of file headers included in the source electronic data file, and an order of file headers included in the source electronic data file.

16. The method of claim 12 , wherein the detecting of the file type includes determining a file type identifier associated with the source electronic data file, the file type identifier including at least one of a string of text included in the source electronic data file and a type of data included in the source electronic data file.

17. The method of claim 12 , wherein the detecting of the file type identifier associated with the source electronic data file includes receiving an identification of the file type identifier associated with the source electronic data file as user input via the interactive mapping graphical user interface.

18. The method of claim 12 , wherein the generating of the transformed source electronic data file includes conforming a format of the data fields included in the source electronic data file to a format of the canonical data fields included in the transformation template.

19. The system of claim 12 , wherein the generating of the transformed source electronic data file includes conforming data included in the source electronic data file to canonical data included in the transformation template.

20. A non-transitory computer-readable storage medium comprising instructions that, when executed by at least one processor of a machine, cause the machine to perform operations for generating a transformed source electronic data file from a source electronic data file based on inputs received from an interactive mapping graphical user interface presented on a client device, the interactive mapping graphical user interface facilitating a mapping a format of the source electronic data file to a canonical format included in a transformation template, the operations comprising:

detecting a file type associated with the source electronic data file;

providing for a selection of the transformation template via the interactive mapping graphical user interface for associating with the file type;

generating the interactive mapping graphical user interface for presentation on the client device, the interactive mapping graphical user interface including interactive user interface elements for combining data fields in the source electronic data file and mapping the combined data fields to a canonical data field included in the transformation template;

generating the transformed source electronic data file from the source electronic data file based on mappings received via the interactive mapping graphical user interface presented on the client device; and

storing the mappings as a file type profile in a database for use in automatically transforming additional source electronic data files of the file type without user intervention.

Assignments (9)
ASSIGNMENT OF INTELLECTUAL PROPERTY SECURITY AGREEMENTS Recorded Jul 3, 2022
From: MORGAN STANLEY SENIOR FUNDING, INC.
To: WELLS FARGO BANK, N.A.
Reel/Frame 060572/0640 →
SECURITY INTEREST Recorded Jul 3, 2022
From: PALANTIR TECHNOLOGIES INC.
To: WELLS FARGO BANK, N.A.
Reel/Frame 060572/0506 →
CORRECTIVE ASSIGNMENT TO CORRECT THE ERRONEOUSLY LISTED PATENT BY REMOVING APPLICATION NO. 16/832267 FROM THE RELEASE OF SECURITY INTEREST PREVIOUSLY RECORDED ON REEL 052856 FRAME 0382. ASSIGNOR(S) HEREBY CONFIRMS THE RELEASE OF SECURITY INTEREST. Recorded Aug 26, 2021
From: ROYAL BANK OF CANADA
To: PALANTIR TECHNOLOGIES INC.
Reel/Frame 057335/0753 →
RELEASE OF SECURITY INTEREST Recorded Jun 4, 2020
From: ROYAL BANK OF CANADA
To: PALANTIR TECHNOLOGIES INC.
Reel/Frame 052856/0382 →
SECURITY INTEREST Recorded Jun 4, 2020
From: PALANTIR TECHNOLOGIES INC.
To: MORGAN STANLEY SENIOR FUNDING, INC.
Reel/Frame 052856/0817 →
SECURITY INTEREST Recorded Jan 27, 2020
From: PALANTIR TECHNOLOGIES INC.
To: MORGAN STANLEY SENIOR FUNDING, INC., AS ADMINISTRATIVE AGENT
Reel/Frame 051713/0149 →
SECURITY INTEREST Recorded Jan 27, 2020
From: PALANTIR TECHNOLOGIES INC.
To: ROYAL BANK OF CANADA, AS ADMINISTRATIVE AGENT
Reel/Frame 051709/0471 →
PROPRIETARY INFORMATION AND INVENTOR AGREEMENT Recorded May 7, 2019
From: PITELKA, HUNTER
To: PALANTIR TECHNOLOGIES INC.
Reel/Frame 049103/0788 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 2, 2017
From: YAZICIOGLU, STEPHEN; LUCK, CHRISTOPHER; GIARDINA, ROBERT; STREUFERT, JUSTIN; SLATCHER, TIMOTHY; O'CONNOR, GREGORY; MARC-AURELE, BRANDON; ZHU, OLIVIA; SCHINDEL, HOWARD; TUNG, HENRY; RAY, LUCAS; LEECH, CHRISTOPHER; JENEY, ERIC; NEGRUS, STEFAN; LEE, JASON; MINGIONE, ALESSANDRO; DOYLE, JOHN MCKINSIRY; LOZANO, ETHAN; OSSHER, JOEL; FEDDERLY, MATTHEW
To: PALANTIR TECHNOLOGIES INC.
Reel/Frame 043415/0313 →
Continuity (2)
Continuation 15092814 · Apr 7, 2016
Provisional Application 62214874 · Sep 4, 2015
Cited By (1)
US 12,326,872