EP3800548A1 - Techniques améliorées pour construire des interfaces utilisateur - Google Patents

Techniques améliorées pour construire des interfaces utilisateur Download PDF

Info

Publication number
EP3800548A1
EP3800548A1 EP20199477.9A EP20199477A EP3800548A1 EP 3800548 A1 EP3800548 A1 EP 3800548A1 EP 20199477 A EP20199477 A EP 20199477A EP 3800548 A1 EP3800548 A1 EP 3800548A1
Authority
EP
European Patent Office
Prior art keywords
user interface
data
builder
data objects
information
Prior art date
Legal status (The legal status 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 status listed.)
Pending
Application number
EP20199477.9A
Other languages
German (de)
English (en)
Inventor
Tiong Tjin SAW
Geoffrey Cameron
Sixin Li
Ali MAVRAKIS
Xinyi Wang
Myles Scolnick
Sander Kromwijk
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Palantir Technologies Inc
Original Assignee
Palantir Technologies Inc
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 Palantir Technologies Inc filed Critical Palantir Technologies Inc
Publication of EP3800548A1 publication Critical patent/EP3800548A1/fr
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/451—Execution arrangements for user interfaces
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0484—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
    • G06F3/04845—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range for image manipulation, e.g. dragging, rotation, expansion or change of colour
    • 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/25—Integrating or interfacing systems involving database management systems
    • G06F16/252—Integrating or interfacing systems involving database management systems between a Database Management System and a front-end application
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/903—Querying
    • G06F16/90335—Query processing
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/903—Querying
    • G06F16/9035—Filtering based on additional data, e.g. user or group profiles
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0481—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
    • G06F3/0482—Interaction with lists of selectable items, e.g. menus
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/20—Software design
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/30—Creation or generation of source code
    • G06F8/34—Graphical or visual programming
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/30—Creation or generation of source code
    • G06F8/38—Creation or generation of source code for implementing user interfaces

Definitions

  • the present disclosure relates to systems and techniques for data integration, analysis, and visualization. More specifically, the present disclosure relates to techniques for building user interfaces.
  • An example user interface editor may include a What You See Is What You Get (WYSIWYG) editor.
  • WYSIWYG What You See Is What You Get
  • a builder user may drag-and-drop user interface elements from a first portion of a builder user interface to a second portion. This second portion may represent an appearance of a consumer user interface which one or more consumers (e.g., end-users) may view.
  • the builder user may use the example editor to place user interface elements, include interactive features, include text and/or images, and so on.
  • a user interface editor may be directed to building web pages.
  • a user interface editor may be directed to building user interfaces for applications.
  • an application may include a mobile application specific to a certain mobile operating system.
  • While these user interface editors may be effective at creating rich user interfaces, they may provide a limited set of interactivity.
  • a builder user may prefer creating a user interface which dynamically presents information to a consumer user.
  • the dynamically presented information may include information generated according to each consumer who visits the user interface.
  • the builder user may prefer accessing information specific to each consumer and then presenting a portion of the accessed information.
  • This added interactivity may require substantive programming, limiting a reach of the user interface editors to addressing just the visual aspects of a user interface.
  • a user interface editor may additionally help standardize a workflow associated with creating such user interfaces.
  • an entity may standardize use of a particular user interface editor.
  • any user of the entity referred to herein as a 'builder user'
  • may rapidly create end-user user interfaces referred to herein as 'consumer user interfaces'
  • This standardized use may help ensure that resulting consumer user interfaces follow similar design guidelines and/or have a similar look and feel.
  • the entity may prefer that certain of the consumer user interfaces include portions which present dynamically determined information.
  • a consumer user interface may be created which presents analyses of certain information stored by a back-end system (e.g., a database system).
  • the information may be dynamically presented, such that a consumer user may adjust one or more sliders, filters, and so on, to adjust the information from which the analyses were determined.
  • the consumer user may also adjust the specific analyses which are performed on the information stored by the back-end system.
  • An example user interface editor described in U.S. Patent No. 10,324,609 describes an innovative user interface tool to create user interfaces with dynamic information.
  • the example user interface editor provides a standardized set of dynamic panels usable to present analyses of dynamically determined information.
  • a dynamic panel may be selected by a builder user.
  • the builder user can then associate the selected panel with one or more data sources (e.g., relational databases, Elasticsearch based, and so on).
  • the example user interface edits may provide a simple workflow for the creation of queries to access these data sources.
  • the dynamic panel may thus easily present information obtained from the data sources.
  • the above-described user interface editor may be used to create a consumer user interface which presents information associated with the National Football League (NFL).
  • NNL National Football League
  • an example query may be executed to obtain data regarding NFL teams from multiple data sources.
  • a first panel in the created consumer user interface may be a dropdown control usable to select a team.
  • a second panel may be a dropdown control usable to select a particular season.
  • a third panel may be a table that displays the games for the selected team and season. Any updates to the first panel or second panel may thus cause an updated query to be executed. The third panel may then present the results associated with the executed query.
  • the above-described user interface editor may cause execution of queries which use tabular data.
  • the tabular data may be stored in database tables of different data sources.
  • a user interface editor described herein may enable use of data objects in consumer user interfaces. Additionally, the user interface editor described herein may provide enhanced builder user interfaces to rapidly associate data objects with portions of a consumer user interface being created.
  • a data object may represent an abstraction of a particular thing.
  • a data object may represent a data container for information representing specific things in the world that have a number of definable properties (also referred to herein as parameters).
  • An example data object may represent a planet or a particular planet (e.g., Mars).
  • the data object for a planet may include properties for its name, size information, orbit information, and so on.
  • a builder user may create a consumer user interface which presents analyses performed on a multitude of these planet data objects.
  • the consumer user interface may enable the dynamic selection of particular planets by a consumer user.
  • the consumer user interface may present analyses of the selected planets.
  • average orbit information for the selected planets may be dynamically determined, and presented, to the consumer user.
  • Data objects may be used to represent certain information in a more natural way as compared with other forms of data representation (e.g., tabular data). Additionally, this more natural representation may provide technical enhancements with respect to performing analyses using data objects.
  • a builder user may quickly select certain planet data objects. The builder user may then quickly define one or more filters, logical operations, and so on, which use parameters of the planet data objects.
  • a builder user may also create links with objects which are associated with a particular object type. A build user can then query through the object type to obtain the related linked objects. For example, an additional object type "spacecraft probe" may be linked to one or more planet objects.
  • a builder user may obtain the related linked planet objects without constructing additional queries.
  • the builder user may be required to have substantive knowledge of how the information is stored. For example, the builder user may be required to create a query which joins specific information across from multiple database tables. In this way, the incorporation of data objects may greatly enhance the capabilities, and usability, of the user interface editor described herein.
  • an example user interface editor may enable a builder user to visually create complex queries which use data objects.
  • the builder user may additionally associate these complex queries with user interface elements of a consumer user interface.
  • the builder user may select from among a multitude of standardized user interface elements (e.g., graphs, charts, and so on) in which to present one or more analyses.
  • the builder user may associate certain interactive elements with a query.
  • an interactive slider may be selected by the builder user interface.
  • a query may be dynamically updated in response to a consumer user adjusting the interactive slider.
  • the slider may update a range of values for a particular parameter of a data object.
  • the slider may be associated with a size of a planet.
  • queries may be executed to filter planets which are below a size selected based on the slider's position.
  • any analyses presented to the consumer user may be dynamically updated.
  • an entity may use a standardized workflow to create complex, and interactive, consumer user interfaces.
  • builder users may leverage the efficiencies associated with storing information as discrete data objects.
  • the builder users may avoid having to learn specific database schemas for back-end data sources.
  • the data objects may be associated with specific parameters such that the builder user can easily reference information of interest.
  • the data objects may also have relationships already set up and the builder user can leverage this information when building their interface. In this way, the succinct builder user interfaces described herein mask the complexities of creating complex database queries.
  • large amounts of data are automatically and dynamically calculated interactively in response to user inputs, and the calculated data is efficiently and compactly presented to a user by the system.
  • the user interfaces described herein are more efficient as compared to previous user interfaces in which data is not dynamically updated and compactly and efficiently presented to the user in response to interactive inputs.
  • the system may be configured and/or designed to generate user interface data useable for rendering the various interactive user interfaces described.
  • the user interface data may be used by the system, and/or another computer system, device, and/or software program (for example, a browser program), to render the interactive user interfaces.
  • the interactive user interfaces may be displayed on, for example, electronic displays (including, for example, touch-enabled displays).
  • the various embodiments of interactive and dynamic user interfaces of the present disclosure are the result of significant research, development, improvement, iteration, and testing. This non-trivial development has resulted in the user interfaces described herein which may provide significant cognitive and ergonomic efficiencies and advantages over previous systems.
  • the interactive and dynamic user interfaces include improved human-computer interactions that may provide reduced mental workloads, improved decision-making, reduced work stress, and/or the like, for a user.
  • user interaction with the interactive user interfaces described herein may provide an optimized display of time-varying report-related information and may enable a user to more quickly access, navigate, assess, and digest such information than previous systems.
  • data may be presented in graphical representations, such as visual representations, such as charts and graphs, where appropriate, to allow the user to comfortably review the large amount of data and to take advantage of humans' particularly strong pattern recognition abilities related to visual stimuli.
  • the system may present aggregate quantities, such as totals, counts, and averages. The system may also utilize the information to interpolate or extrapolate, e.g. forecast, future developments.
  • the interactive and dynamic user interfaces described herein are enabled by innovations in efficient interactions between the user interfaces and underlying systems and components.
  • disclosed herein are improved methods of receiving user inputs, translation and delivery of those inputs to various system components, automatic and dynamic execution of complex processes in response to the input delivery, automatic interaction among various components and processes of the system, and automatic and dynamic updating of the user interfaces.
  • the interactions and presentation of data via the interactive user interfaces described herein may accordingly provide cognitive and ergonomic efficiencies and advantages over previous systems.
  • Various embodiments of the present disclosure provide improvements to various technologies and technological fields. For example, as described above, existing user interface editors are limited in various ways, and various embodiments of the disclosure provide significant improvements over such technology. Additionally, various embodiments of the present disclosure are inextricably tied to computer technology. In particular, various embodiments rely on detection of user inputs via graphical user interfaces, calculation of updates to displayed electronic data based on those user inputs, automatic processing of related electronic data, and presentation of the updates to displayed images via interactive graphical user interfaces. Such features and others (e.g., processing and analysis of large amounts of electronic data) are intimately tied to, and enabled by, computer technology, and would not exist except for computer technology.
  • systems and/or computer systems comprise a computer readable storage medium having program instructions embodied therewith, and one or more processors configured to execute the program instructions to cause the one or more processors to perform operations comprising one or more aspects of the above- and/or below-described embodiments (including one or more aspects of the appended claims).
  • computer program products comprising a computer readable storage medium
  • the computer readable storage medium has program instructions embodied therewith, the program instructions executable by one or more processors to cause the one or more processors to perform operations comprising one or more aspects of the above- and/or below-described embodiments (including one or more aspects of the appended claims).
  • An example user interface editor described herein may allow a builder user to create consumer user interfaces for use by consumer users (e.g., end-users).
  • the user interface editor may, in some embodiments, be an example of a What You See Is What You Get (WYSIWYG) editor.
  • a builder user may create a visual look of a consumer user interface. For example, the builder user may drag and drop certain user interface elements onto the consumer user interface being created.
  • Example user interface elements may include boxes, lines, textual portions, images, certain logos or identifiers, animations, and so on. Additionally, the builder user may prefer that certain user interface elements be configured to present dynamically determined information.
  • Example builder user interfaces described herein may, via succinct user input, enable complex queries to be created. These complex queries may cause analyses to be performed using data objects stored by a system described herein (e.g., the interface creation system 100).
  • the consumer user interface may be configured to cause execution of queries based, at least in part, on user input provided by a consumer user. In this way, the consumer user interface may be dynamically updated with information generated using the stored data objects.
  • the user input may cause adjustment to the queries, such that the consumer user interface is configured to dynamically update the analyses in real-time (e.g., substantially real-time).
  • U.S. Patent No. 10,324,609 An example of a user interface editor is described in U.S. Patent No. 10,324,609 .
  • This example user interface editor provides dynamic panels in a builder user interface. These dynamic panels may be configured for inclusion in a consumer user interface, and used to present dynamically determined information.
  • the dynamic panels may be associated with queries which use tabular data stored by one or more data sources. The queries may be executed and an output (e.g., one or more analyses) may be presented via the dynamic panels.
  • the above-described dynamic panels can display different pieces of data from one or more data sources.
  • a query can be run on one or more data sources, and different parts of the result from the query can be output using different dynamic panels.
  • each dynamic panel can be associated with a variable to output.
  • Different types of dynamic panels can be provided, such as charts (e.g., line chart, bar chart, etc.), controls (e.g., dropdown, multiselect box, search box, etc.), maps, tables, text boxes, etc.
  • the panels can be data source agnostic.
  • the panels can be associated with data from different types of data sources, such as relational databases (e.g., SQL Server), Elasticsearch based, and so on.
  • multiple panels can be used to display different aspects of the result from a query.
  • One query can be run to obtain the needed information, and the result can be parsed and displayed using multiple panels. Display of information can be simplified by using multiple panels.
  • the query can be reused across panels since each panel can extract a portion of the result to display.
  • each panel may have its own query and display the result of the query.
  • the panels can also be linked together so that the data from one panel can be used to display the data in another panel.
  • FIGS. 2A-2D of U.S. Patent No. 10,324,609 are example user interfaces associated with creating dynamic panels. These example user interfaces may be used by a builder user to manage the above-described panels.
  • the builder user may design a visual appearance associated with the panels and/or consumer user interface being created.
  • the builder user may select from among a plurality of templates or existing visual appearances of the panels.
  • the builder user may then use a user interface to create one or more queries to be associated with the panels.
  • the builder user may select from among an existing set of queries.
  • the panels may thus present information generated based on execution of the queries.
  • the queries may include certain variables which may be tied to interactive user interface elements of a consumer user interface.
  • a variable may be used for a certain parameter.
  • a variable may be used to represent a lower bound on certain size information of planets. This variable may then be tied to, for example, a slider user interface element in the consumer user interface.
  • the consumer user may adjust a lower bound of the size information.
  • a value for the variable in a query may be adjusted accordingly.
  • the consumer user interface may present an updated analysis based on execution of the adjusted query.
  • the consumer user interface may present dynamically determined information to the consumer user.
  • the information obtained using queries may, as an example, be stored in database tables.
  • the information may be stored as tabular data.
  • the builder user may therefore create queries which join disparate information from across the database tables.
  • the builder user interfaces described herein enable creation of consumer user interfaces which present dynamically determined analyses of data objects.
  • a builder user interface editor may allow for information associated with data objects to be included in a consumer user interface.
  • a builder user may select a data object type of interest.
  • the builder user may select a data object type corresponding to NFL teams.
  • the builder user may additionally select certain sets of data objects associated with the data object type.
  • the different sets of data objects may correspond to different geographical regions or NFL conferences.
  • the builder user may then optionally specify certain values of parameters associated with the data object type to generate one or more filters.
  • the builder user may specify values corresponding to certain team names.
  • One or more queries may be created based on these filters. Similar to the above-example user interface editor, the queries may then be associated with user interface elements in a consumer user interface.
  • an analysis may present NFL statistical information for certain teams in the consumer user interface.
  • the builder user may use curly brackets (e.g., ' ⁇ ⁇ ') to indicate that values of a property (also referred to herein as a parameter) will be dynamically determined based on user input provided by a consumer, via variables or other similar templating mechanism linking one or more user interface elements with the properties.
  • curly brackets e.g., ' ⁇ ⁇ '
  • a builder user may use curly brackets to specify that the value for a certain parameter will be supplied by a consumer user.
  • the value for the certain parameter may be linked to the output of one or more other user interface elements (e.g., sliders, dropdowns, radio buttons, etc.) via one or more variables or other similar templating mechanism.
  • a consumer user may provide user input to modify such user interface elements that are linked to the parameter, and the value for the certain parameter may thus be supplied based on the user input.
  • a variable or other similar templating mechanism may be used for the value of a parameter with the value being dynamically provided according to a slider or other user interface element. While reference to curly brackets or a variable is included herein, in some embodiments any handlebar templating mechanism may be used.
  • Figure 1A illustrates an example builder user interface 120 for dynamically filtering data objects.
  • the builder user interface 120 may form, in some embodiments, part of a workflow associated with creating a consumer user interface.
  • the builder user interface 120 may be used to create one or more queries which are to be associated with portions of the consumer user interface.
  • the builder user interface 120 may be an example of a user interface presented as a web page via a builder user device 150.
  • the builder user interface 120 may be a web application which is associated with a back-end system (e.g., the interface creation system 100).
  • the builder user interface 120 may additionally be an example of a user interface for an application.
  • An example application may include a mobile application, a desktop application, and so on.
  • the builder user device 150 may be used by a builder user, and may include a laptop, tablet, mobile device, wearable device, and so on.
  • the builder user may use the builder user interface 120 to cause creation of one or more queries. These queries may then be associated with user interface elements of a consumer user interface.
  • the builder user has provided user input 152 to specify an object type.
  • the builder user has selected 'Object Type A'.
  • user input 152 may encompass disparate input types.
  • the builder user may use a keyboard / mouse, provide touch-input to a touch sensitive display of the builder user device 150, provide verbal commands which are processed, at least in part, by the builder user device 150, and so on.
  • the builder user interface 120 may include functionality to search for existing object types.
  • the builder user interface 120 may include a search box.
  • the builder user may provide at least a portion of text indicative of an object type.
  • the interface creation system 100 may then search an ontology to identify responsive object types.
  • the builder user interface 120 may present indications of certain object types in the builder user interface 120.
  • the builder user interface 120 may identify a top threshold number of object types based on one or more measures. These measures may indicate, for example, popularity of object types across builder users.
  • the interface creation system 100 may determine contextual information associated with a consumer user interface being created.
  • the builder user may have created a portion of the consumer user interface.
  • the builder user may have included text which is indicative of a purpose of the consumer user interface.
  • Example text may include, "Analysis of [Object Type A]."
  • the system 100 may therefore infer that Object Type A is to be used.
  • the builder user interface 120 may present object types for selection which are determined to be contextually relevant for the builder user.
  • Each object type may optionally be associated with different object sets.
  • different object sets may each comprise multiple data objects. These object sets may be used to classify, or otherwise separate, certain data objects from each other.
  • planets there may be multitudes of different object sets.
  • Each of these object sets may include planet data objects which have been classified together.
  • a first object set may include planet data objects corresponding to planets which are within a threshold distance of Earth.
  • a second object set may include planet data objects corresponding to planets within a next threshold distance of Earth.
  • the builder user interface 120 indicates that there are, at least, four object sets. For example, Object Set A - Object Set D is included in the user interface 120. Similar to the above, the interface creation system 100 may select certain object sets of a selected object type which are contextually relevant. For example, the builder user may be creating a consumer user interface which describes 'Planets Within Our Solar System.” As another example, the builder user may be creating a consumer user interface which presents "Usage Information for Cloud Network in [City A]." The interface creation system 100 may thus analyze text, or other information (e.g., images), included in the consumer user interface.
  • information e.g., images
  • the interface creation system 100 may use example deep learning techniques (e.g., recurrent neural networks, convolutional neural networks). With respect to the above examples, the interface creation system 100 may thus present object sets corresponding to planets within our solar system or object sets associated with City A.
  • example deep learning techniques e.g., recurrent neural networks, convolutional neural networks.
  • the builder user has selected Object Set B 124A and Object Set D 124B from among the presented object sets.
  • the builder user interface 120 may respond to user input provided to a particular presented object set.
  • the builder user may use touch-based input to select Object Set B 124A.
  • the builder user may 'long-press' Object Set B 124A for greater than a threshold amount of time.
  • the builder user interface 120 may present indications of data objects included in Object Set B 124A. For example, a popup, or separate user interface window, may be presented which includes indications of data objects.
  • names associated with the data objects optionally along with example properties may be presented.
  • object types may be associated with parameters.
  • an ontology may provide a data model for the data objects. This ontology may be used by the interface creation system 100 to access the parameters for Object Type A 1222.
  • the parameters may be specified by the builder user to filter data objects.
  • the builder user may prefer that an analysis included in the consumer user interface includes only data objects with certain parameters.
  • An example consumer user interface may include an analysis of a network in a certain city. The builder user may prefer that the analysis use only certain systems associated with the network. Thus, the builder user may filter the data objects, such that only the certain systems are included in the analysis.
  • the builder user interface 120 includes a filter portion 126. This portion 126 may be used to specify logical expressions associated with parameters of a selected object type.
  • the builder user interface 120 may present a name, or other identifying information, associated with a parameter of the selected object type.
  • the builder user interface 120 may present indications of all parameters of the selected object type.
  • the builder user may then select a parameter of interest, for example via specifying at least a portion of the name.
  • the interface creation system 100 may additionally present an initial parameter which is contextually relevant to a consumer user interface being created. With respect to the example of a cloud network, the builder user interface 120 may present system latency as the initially presented parameter.
  • the builder user has selected Parameter A 128A.
  • the builder user has additionally included example values for Parameter A 128A.
  • Value A and Value B are specified. This may represent a range of values for Parameter A 128A. Thus, data objects with a value for Parameter A 128A outside of this range may be filtered out.
  • the builder user can chain values of parameters according to logical expressions.
  • the builder user can indicate that only data objects with a certain range of values for Parameter A 128A and a certain range of values for one or more other parameters are to be used in an analysis included in a consumer user interface.
  • the builder user may specify a logical expression using Boolean operations for set operations (e.g. AND, OR, NOT, and so on).
  • Boolean operations for set operations e.g. AND, OR, NOT, and so on.
  • the builder user has indicated that Parameter A 128A is to be logically combined with Parameter B 128B using an AND Boolean operation.
  • the builder user has used a variable or template for Parameter B 128B.
  • the builder user may associate a parameter with a user interface element in the consumer user interface.
  • the variable or template may indicate that values for Parameter B 128B are to be supplied in accordance with the user interface element.
  • Example user interface elements may include a slider, date picker, dropdown control, button (e.g., export button, query button, etc.), input box, multiselect box, text area, timeline, and so on.
  • values for Parameter B 128B may be supplied based on a position of a slider.
  • a consumer user may adjust the slider when viewing the consumer user interface and the value may be adjusted accordingly.
  • the builder user has used curly brackets for the value of Parameter B (e.g., ' ⁇ ⁇ '). While the illustrated example uses curly brackets, it may be appreciated that such a value is arbitrary. Indeed, other values may be used and fall within the scope of the disclosure.
  • the builder user interface 120 may include a user interface element associated with designating a variable for a parameter. For example, there may be a radio box or checkmark proximate to Parameter B. In this example, the builder user may select the radio box or checkmark to designate that values for Parameter B will be tied to a user interface element in a resulting consumer user interface.
  • the builder user may specify one or more logical expressions which are usable to filter data objects.
  • the builder user may use two or more object types. For example, the builder user may indicate that Object Type A and Object Type B are to be used. The builder user may then specify parameters as described above. In this way, data objects corresponding to both Object Type A and Object Type B may be used. An analysis may then be included in a consumer user interface which leverages both object types.
  • the builder user interface 120 may present example data objects 130 which satisfy the information specified in the filter portion 126.
  • the interface creation system 100 may access one or more databases (e.g., object database 112) to identify responsive data objects.
  • a query generation engine 110 may create a query in accordance with the information included in filter portion 126.
  • the query generation engine 110 may execute a query in accordance with the information.
  • the builder user interface 120 may be updated to reflect data objects obtained based on execution of the query. In this way, the builder user may view data objects which are to be used in one or more analyses.
  • the example data objects 130 may be presented along with values of example parameters for Object Type A.
  • builder user interface 120 includes an identification of each data object along with values for Parameter A and Parameter B.
  • the builder user interface may include a user interface element which is to be included in a consumer user interface.
  • the user interface element may be selected by the builder user to adjust a value of Parameter B 128B.
  • the user interface element may be a slider.
  • the builder user interface 120 may therefore include an example slider for adjustment by the builder user. In response to adjustment, a value for Parameter B 128B may be selected.
  • the builder user interface 120 may present an example analysis which is to be included in a consumer user interface.
  • the builder user may specify certain operations to be performed on information associated with data objects. The operations may aggregate information associated with the data objects.
  • the builder user interface 120 may present an example analysis based on the data objects which satisfy the information included in the filter portion 126.
  • the example analysis may be associated with one or more user interface elements which are to be included in the consumer user interface.
  • the example analysis may be presented as a graph.
  • the builder user interface 120 may present a graph as would be included in the consumer user interface. In this way, the builder user may quickly identify whether the analysis is accurate.
  • Figure 1B illustrates an example consumer user interface 160 presenting an example analysis of dynamically determined data objects.
  • the builder user may specify information usable to filter data objects.
  • the builder user may specify an object type.
  • the builder user may specify one or more logical expressions to filter data objects of the specified object type.
  • the interface creation system 100 may create one or more queries to filter the data objects in accordance with the specified information. As will be described, these queries may be executed by the interface creation system 100 to present information to a consumer user in a consumer user interface.
  • the consumer user interface 160 is being presented via a consumer user device 180.
  • the consumer user device 160 may be a laptop, tablet, mobile device, wearable device, and so on as described above.
  • the consumer user interface 160 may have been created by a builder user, such as the builder user described in Figure 1A .
  • the builder user may use a user interface editor (e.g., a WYSIWYG editor) to include the example visual elements of consumer user interface 160.
  • a certain user interface element 164 may be usable to present an analysis of information dynamically determined based on data objects.
  • a certain user interface element 166 may be usable to provide a value for a particular parameter in one or more queries being executed by the interface creation system 100.
  • the consumer user interface 160 includes an example description 162 of the analysis.
  • the user interface 160 indicates that an analysis is being performed for a certain object type (e.g., Object Type A).
  • the user interface 160 further indicates a range of values which are being used for data objects included in the analysis.
  • Parameter A is indicated being within a range from Value A to Value B.
  • the user interface 160 indicates that a value for Parameter B can be selected via adjustment of user interface element 166.
  • chart 164 An example analysis is represented in chart 164. While the example of Figure 1B illustrates a chart 164, it may be appreciated that other representations may be used.
  • a builder user may optionally select from among a multitude of existing representations. For example, the builder user may select from a table, a chart, a bar graph, a pie chart, three-dimensional representations, and so on.
  • the included analysis may be dynamically determined in real-time (e.g., substantially real-time).
  • a consumer user may provide user input 182 to the consumer user interface 160.
  • Example user input 182 may include adjustment of slider 166.
  • the slider 166 may indicate a value for Parameter B.
  • a movement of the slider 166 from a left to a right position may indicate an increase in a value for Parameter B.
  • This user input 182 may thus be routed to the interface creation system 100 to provide a value for the variable associated with Parameter B.
  • the system 100 may then execute a query 114 which includes the provided value for Parameter B.
  • the executed query 114 may cause access to one or more databases (e.g., the object database 112) to obtain responsive data objects.
  • object information 116 may be obtained by the interface creation system 100.
  • the interface creation system 100 may route the object information 116 to the consumer user device 180.
  • the data objects may be routed to the user device 180.
  • the object information 116 may be provided in a particular form (e.g., JavaScript Object Notation).
  • the consumer user device 180 may use the object information 116 to update the chart 164.
  • the user device 180 may effectuate one or more analyses via code included in, or otherwise associated with, user interface information associated with user interface 160.
  • the interface creation system 100 may perform the one or more analyses and update chart 164. With respect to a web application, the interface creation system 100 may thus generate a new graphical representation of the analyses. This new graphical representation may then be included in a web page presented via consumer user device 180.
  • Ontology Stored information that provides a data model for storage of data in one or more databases.
  • the stored data may comprise definitions for data object types and property types for data in a database, and how data objects and properties (also referred to herein as parameters) may be related.
  • Data Store Any computer readable storage medium and/or device (or collection of data storage mediums and/or devices). Examples of data stores include, but are not limited to, optical disks (e.g., CD-ROM, DVD-ROM, etc.), magnetic disks (e.g., hard disks, floppy disks, etc.), memory circuits (e.g., solid state drives, random-access memory (RAM), etc.), and/or the like.
  • optical disks e.g., CD-ROM, DVD-ROM, etc.
  • magnetic disks e.g., hard disks, floppy disks, etc.
  • memory circuits e.g., solid state drives, random-access memory (RAM), etc.
  • RAM random-access memory
  • Another example of a data store is a hosted storage environment that includes a collection of physical data storage devices that may be remotely accessible and may be rapidly provisioned as needed (commonly referred to as "cloud" storage).
  • Database Any data structure (and/or combinations of multiple data structures) for storing and/or organizing data, including, but not limited to, relational databases (e.g., Oracle databases, PostgreSQL databases, etc.), non-relational databases (e.g., NoSQL databases, Elasticsearch based etc.), in-memory databases, spreadsheets, as comma separated values (CSV) files, eXtendible markup language (XML) files, TeXT (TXT) files, flat files, spreadsheet files, and/or any other widely used or proprietary format for data storage.
  • Databases are typically stored in one or more data stores. Accordingly, each database referred to herein (e.g., in the description herein and/or the figures of the present application) is to be understood as being stored in one or more data stores.
  • Data Object or Object A data container for information representing specific things in the world that have a number of definable properties (herein also referred to as a parameter).
  • a data object can represent an entity such as a person, a place, an organization, a market instrument, or other noun.
  • a data object can represent an event that happens at a point in time or for a duration.
  • a data object can represent a document or other unstructured data source such as an e-mail message, a news report, or a written paper or article.
  • Each data object may be associated with a unique identifier that uniquely identifies the data object.
  • the data object's attributes e.g. metadata about the data object
  • Object Type Type of a data object (e.g., Person, Event, or Document).
  • Object types may be defined by an ontology and may be modified or updated to include additional object types.
  • An object definition e.g., in an ontology
  • An object definition may include how the object is related to other objects, such as being a sub-object type of another object type (e.g. an agent may be a sub-object type of a person object type), and the properties the object type may have.
  • Attributes of a data object that represent individual data items. At a minimum, each property of a data object has a property type and a value or values.
  • Property Type The type of data a property is, such as a string, an integer, or a double.
  • Property types may include complex property types, such as a series data values associated with timed ticks (e.g. a time series), etc.
  • Property Value The value associated with a property, which is of the type indicated in the property type associated with the property.
  • a property may have multiple values.
  • Link A connection between two data objects, based on, for example, a relationship, an event, and/or matching properties. Links may be directional, such as one representing a payment from person A to B, or bidirectional.
  • Link Set Set of multiple links that are shared between two or more data obj ects.
  • a user who creates, and/or designs, a consumer user interface for use by consumer users.
  • the user may use a user interface editor, such as example builder user interfaces.
  • Builder User Interface A user interface with which a builder user can create a consumer user interface.
  • Example builder user interfaces are represented in Figure 1A and 5A-5D . Additional builder user interfaces are included in U.S. Patent No. 10,324,609 .
  • Consumer User An end-user who uses a consumer user interface created, and/or designed, by one or more builder users.
  • the end-user may interact with the consumer user interface via a user device, such as a laptop, tablet, mobile device, wearable device, and so on.
  • the consumer user interface may, as an example, present one or more analyses of data objects. For example, information associated with the data objects may be aggregated.
  • the interface creation system 100 may implement, or otherwise be associated with, the example database system 210.
  • This description is provided for the purpose of providing an example and is not intended to limit the techniques to the example data model, the example database system, or the example database system's use of an ontology to represent information.
  • a body of data is conceptually structured according to an object-centric data model represented by ontology 205.
  • the conceptual data model is independent of any particular database used for durably storing one or more database(s) 209 based on the ontology 205.
  • each object of the conceptual data model may correspond to one or more rows in a relational database or an entry in Lightweight Directory Access Protocol (LDAP) database, or any combination of one or more databases.
  • LDAP Lightweight Directory Access Protocol
  • Figure 2 illustrates an object-centric conceptual data model according to an embodiment.
  • An ontology 205 may include stored information providing a data model for storage of data in the database 209.
  • the ontology 205 may be defined by one or more object types, which may each be associated with one or more property types.
  • data object 201 is a container for information representing things in the world.
  • data object 201 can represent an entity such as a person, a place, an organization, a market instrument, or other noun.
  • Data object 201 can represent an event that happens at a point in time or for a duration.
  • Data object 201 can represent a document or other unstructured data source such as an e-mail message, a news report, or a written paper or article.
  • Each data object 201 is associated with a unique identifier that uniquely identifies the data object within the database system.
  • Each property 203 as represented by data in the database system 210 may have a property type defined by the ontology 205 used by the database 205.
  • Objects may be instantiated in the database 209 in accordance with the corresponding object definition for the particular object in the ontology 205.
  • a specific monetary payment e.g., an object of type "event” of US$30.00 (e.g., a property of type "currency") taking place on 3/27/2009 (e.g., a property of type "date") may be stored in the database 209 as an event object with associated currency and date properties as defined within the ontology 205.
  • the data objects defined in the ontology 205 may support property multiplicity.
  • a data object 201 may be allowed to have more than one property 203 of the same property type.
  • a "Person" data object might have multiple "Address” properties or multiple "Name” properties.
  • Each link 202 represents a connection between two data objects 201.
  • the connection is either through a relationship, an event, or through matching properties.
  • a relationship connection may be asymmetrical or symmetrical.
  • "Person" data object A may be connected to "Person” data object B by a "Child Of' relationship (where "Person” data object B has an asymmetric "Parent Of' relationship to "Person” data object A), a "Kin Of' symmetric relationship to "Person” data object C, and an asymmetric "Member Of' relationship to "Organization" data object X.
  • the type of relationship between two data objects may vary depending on the types of the data objects.
  • "Person" data object A may have an "Appears In” relationship with "Document” data object Y or have a "Participate In” relationship with "Event” data object E.
  • two “Person” data objects may be connected by an "Airline Flight” data object representing a particular airline flight if they traveled together on that flight, or by a "Meeting” data object representing a particular meeting if they both attended that meeting.
  • relationships in which each data object has a specific relationship to the event, such as, for example, an "Appears In” relationship.
  • a link between two data objects may be established based on similar or matching properties (e.g., property types and/or property values) of the data objects.
  • similar or matching properties e.g., property types and/or property values
  • a document might contain references to two different objects.
  • a document may contain a reference to a payment (one object), and a person (a second object).
  • a link between these two objects may represent a connection between these two entities through their co-occurrence within the same document.
  • Each data object 201 can have multiple links with another data object 201 to form a link set 204.
  • two "Person” data objects representing a husband and a wife could be linked through a "Spouse Of' relationship, a matching "Address” property, and one or more matching "Event” properties (e.g., a wedding).
  • Each link 202 as represented by data in a database may have a link type defined by the database ontology used by the database.
  • Figure 3 is a block diagram illustrating exemplary components and data that may be used in identifying and storing data according to an ontology.
  • the ontology may be configured, and data in the data model populated, by a system of parsers and ontology configuration tools.
  • input data 300 is provided to parser 302.
  • the input data may comprise data from one or more sources.
  • an institution may have one or more databases with information on credit card transactions, rental cars, and people.
  • the databases may contain a variety of related information and attributes about each type of data, such as a "date" for a credit card transaction, an address for a person, and a date for when a rental car is rented.
  • the parser 302 is able to read a variety of source input data types and determine which type of data it is reading.
  • the example ontology 205 comprises stored information providing the data model of data stored in database 209, and the ontology is defined by one or more object types 310, one or more property types 316, and one or more link types 330.
  • one or more data objects 201 may be instantiated in the database 209 based on respective determined object types 310, and each of the objects 201 has one or more properties 203 that are instantiated based on property types 316.
  • Two data objects 201 may be connected by one or more links 202 that may be instantiated based on link types 330.
  • the property types 316 each may comprise one or more data types 318, such as a string, number, etc.
  • Property types 316 may be instantiated based on a base property type 320.
  • a base property type 320 may be "Locations” and a property type 316 may be "Home.”
  • a user of the system uses an object type editor 324 to create and/or modify the object types 310 and define attributes of the object types.
  • a user of the system uses a property type editor 326 to create and/or modify the property types 316 and define attributes of the property types.
  • a user of the system uses link type editor 328 to create the link types 330.
  • other programs, processes, or programmatic controls may be used to create link types and property types and define attributes, and using editors is not required.
  • creating a property type 316 using the property type editor 326 involves defining at least one parser definition using a parser editor 322.
  • a parser definition comprises metadata that informs parser 302 how to parse input data 300 to determine whether values in the input data can be assigned to the property type 316 that is associated with the parser definition.
  • each parser definition may comprise a regular expression parser 304A or a code module parser 304B. In other embodiments, other kinds of parser definitions may be provided using scripts or other programmatic elements. Once defined, both a regular expression parser 304A and a code module parser 304B can provide input to parser 302 to control parsing of input data 300.
  • input data 300 may be parsed by the parser 302 determine which object type 310 should receive data from a record created from the input data, and which property types 316 should be assigned to data from individual field values in the input data. Based on the object-property mapping 301, the parser 302 selects one of the parser definitions that is associated with a property type in the input data. The parser parses an input data field using the selected parser definition, resulting in creating new or modified data 303. The new or modified data 303 is added to the database 209 according to ontology 205 by storing values of the new or modified data in a property of the specified property type.
  • input data 300 having varying format or syntax can be created in database 209.
  • the ontology 205 may be modified at any time using object type editor 324, property type editor 326, and link type editor 328, or under program control without human use of an editor.
  • Parser editor 322 enables creating multiple parser definitions that can successfully parse input data 300 having varying format or syntax and determine which property types should be used to transform input data 300 into new or modified input data 303.
  • FIG. 4 is a flowchart of an example process 400 for enabling creation of a consumer user interface.
  • the process 400 will be described as being performed by a system of one or more computers (e.g., the interface creation system 100).
  • a builder user may use a user device of one or more processors in communication with the system.
  • the system causes presentation of a builder user interface.
  • a builder user may use an example user interface editor to create a consumer user interface.
  • the builder user may create the consumer user interface 160 illustrated in Figure 1B .
  • the builder user may prefer presenting dynamic information to a consumer user in the consumer user interface.
  • the builder user may prefer that one or more analyses, or aggregations, of information be presented.
  • the builder user may cause the performance of analyses using data objects.
  • the builder user may interact with the builder user interface to specify data objects which are to be used in one or more analyses.
  • the builder user may specify information usable to filter data objects.
  • each data object may be associated with one or more object types.
  • An example object type may be a planet.
  • data objects may include respective planets.
  • Parameters of the object type may include information associated with planets.
  • each data object may include information associated with a respective planet.
  • the builder user may interact with the presented builder user interface to select a particular object type.
  • the builder user may select two or more object types. For example, the builder user may specify that an analysis is to be performed using information from two or more object types.
  • a first object type may represent planets while a second object type may represent stars.
  • an analysis may be performed which includes planetary and star information.
  • the system receives filter information associated with a user interface element.
  • the builder user may prefer that only certain data objects are implicated in one or more analyses.
  • the builder user may specify values, ranges of values, or variables, for one or more parameters associated with the object type.
  • the builder user may indicate a particular range of values for a first parameter.
  • the builder user may indicate a particular range where at least one end of the range is a variable.
  • the builder user may use a certain variable or template designation (e.g., ' ⁇ ⁇ '). As described above, this variable may represent that a value is to be supplied dynamically based on user input from a consumer user.
  • the builder user may additionally associate this filter information with a user interface element.
  • a variable may be associated with a slider.
  • the slider may extend from a first value to a second value.
  • a consumer user may adjust the slider to cause selection of a particular value within this range.
  • the first value and second value may be automatically identified by the system according to a highest and lowest value for the associated parameter across data objects (e.g., all of the data objects, a subset of the data objects).
  • a dropdown control may be associated with the filter information (e.g., a variable).
  • a consumer user may interact with the dropdown control to select a value, range of values, and so on.
  • the builder user may specify certain values which may be selected in the dropdown control.
  • the builder user may specify cerate ranges of values, or may allow for a consumer user to specify a desired value for a parameter.
  • an input box may be used by a consumer user to specify a value or range of values. Additional examples of interactive elements may be used and fall within the scope of the present disclosure (e.g., hardware buttons on a mobile device such as the volume buttons may increase a value, a stepper, toggles, and so on).
  • variables or templates may be combined.
  • a first variable may be associated with a first parameter as described herein.
  • a builder user may cause this second parameter to reference the first variable.
  • a linear or non-linear formula may be used for the second parameter which uses the first variable.
  • the second parameter may reference a second variable or template. This second variable may be tied to a second user interface element.
  • the value for the second parameter may be tied to interactions with the first user interface element and second user interface element.
  • the builder user may interact with a builder user interface to select the user interface element. Additionally, the builder user may interact with a builder user interface to drag and drop the user interface element onto a consumer user interface being created. In this way, the builder user may quickly ascertain an overall look of the consumer user interface. Additionally, the builder user may then quickly associate the specific user interface element with a variable usable to filter data objects.
  • the system enables creation of a consumer user interface.
  • the builder user may use a user interface editor to drag and drop user interface elements onto a consumer user interface. Additional techniques to create a consumer user interface may be used and fall within the scope of the disclosure herein. For example, existing templates of consumer user interfaces may be accessed. The builder user may then select a template and adjust the template using a WYSIWYG editor.
  • the builder user may additionally select a user interface element to be associated with presentation of information generated based on data objects.
  • the user interface element may be a graphical depiction of the information.
  • the user interface element may be a chart, graph, and so on as described herein.
  • the user interface element may be generated as audio output via a user device.
  • the audio may be generated to describe aspects of the data objects.
  • the builder user may optionally specify techniques for generating an analysis with data objects.
  • the builder user may specify a particular formula which uses information associated with data objects.
  • the particular formula may reference certain parameters associated with the object type.
  • the builder user may select from among existing analyses.
  • existing analyses may include measures of central tendency of certain parameters.
  • the system enables access to the consumer user interface.
  • the system may therefore generate user interface information corresponding to the consumer user interface.
  • the system may generate information which may be rendered via a web browser.
  • the system may generate information which may be executed by a mobile device to cause presentation of the consumer user interface.
  • a consumer user may therefore view the consumer user interface.
  • the consumer user may interact with one or more user interface elements.
  • the consumer user may interact with a slider to specify a value for a particular parameter.
  • the system may execute a query to filter data objects based on the specified value.
  • the system may then update any analyses which are included in the consumer user interface.
  • Figure 5A illustrates an example builder user interface 500.
  • a builder user is selecting an object type.
  • the builder user has selected an object type 'Asteroid.
  • the builder user interface 500 includes indications of object sets 502 corresponding to this object type.
  • Each object set is identified with a number of included data objects (e.g., '2k').
  • the builder user may optionally select certain of these object sets, or all of the object sets may be selected.
  • Figure 5B illustrates another example builder user interface 510.
  • a builder user is specifying filter information 512.
  • the builder user has selected 'Asteroid' object type and is selecting a parameter to filter the data objects.
  • user interface 510 indicates example parameters 514.
  • the builder user can indicate values of, "period,” “semimajoraxis,” “rotationperiod,” and so on.
  • the builder user can define a logical expression which uses combinations of these parameters.
  • the builder user interface 510 additionally includes examples data objects on a right portion 516.
  • Figure 5C illustrates another example builder user interface 520.
  • the builder user has specified values for the parameter of 'Period" in the filter information portion 522. Specifically, the builder user has indicated a lower bound of "3.” The builder user has indicated that the upper bound is to be variable by using curly brackets. As described above, the system (e.g., interface creation system 100) may recognize the curly brackets as corresponding to a variable. The builder user may then associate this upper bound with a particular user interface element (e.g., slider).
  • a particular user interface element e.g., slider
  • the builder user interface 520 may update to present example user interface elements. The builder user may then select a particular user interface element as being associated with the upper bound of the parameter. In some embodiments, the system may store information indicating that a particular variable is the upper bound of the parameter. As the builder user, or another builder user, creates the consumer user interface, the system may prompt the builder user to associate a user interface element with the variable.
  • Figure 5C further includes example data objects 524 which satisfy the information specified in the filter information portion 522.
  • the system may execute a query which is generated based on the specified information. For example, the system may identify data objects which have a lower bound of '3' for parameter 'Period.'
  • Figure 5D illustrates another example builder user interface 530.
  • the builder user has created a complex logical operation in the filter information portion 532.
  • the builder user has specified values for parameter 'Period', 'Rotationperiod', and 'Diameter'.
  • Various embodiments of the present disclosure may be a system, a method, and/or a computer program product at any possible technical detail level of integration
  • the computer program product may include a computer readable storage medium (or mediums) having computer readable program instructions thereon for causing a processor to carry out aspects of the present disclosure
  • the functionality described herein may be performed as software instructions are executed by, and/or in response to software instructions being executed by, one or more hardware processors and/or any other suitable computing devices.
  • the software instructions and/or other executable code may be read from a computer readable storage medium (or mediums).
  • the computer readable storage medium can be a tangible device that can retain and store data and/or instructions for use by an instruction execution device.
  • the computer readable storage medium may be, for example, but is not limited to, an electronic storage device (including any volatile and/or non-volatile electronic storage devices), a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing.
  • a non-exhaustive list of more specific examples of the computer readable storage medium includes the following: a portable computer diskette, a hard disk, a solid state drive, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing.
  • RAM random access memory
  • ROM read-only memory
  • EPROM or Flash memory erasable programmable read-only memory
  • SRAM static random access memory
  • CD-ROM compact disc read-only memory
  • DVD digital versatile disk
  • memory stick a floppy disk
  • a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon
  • a computer readable storage medium is not to be construed as being transitory signals per se , such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.
  • Computer readable program instructions described herein can be downloaded to respective computing/processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and/or a wireless network.
  • the network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers.
  • a network adapter card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing/processing device.
  • Computer readable program instructions (as also referred to herein as, for example, "code,” “instructions,” “module,” “application,” “software application,” and/or the like) for carrying out operations of the present disclosure may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, configuration data for integrated circuitry, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Java, C++, or the like, and procedural programming languages, such as the "C” programming language or similar programming languages.
  • Computer readable program instructions may be callable from other instructions or from itself, and/or may be invoked in response to detected events or interrupts.
  • Computer readable program instructions configured for execution on computing devices may be provided on a computer readable storage medium, and/or as a digital download (and may be originally stored in a compressed or installable format that requires installation, decompression or decryption prior to execution) that may then be stored on a computer readable storage medium.
  • Such computer readable program instructions may be stored, partially or fully, on a memory device (e.g., a computer readable storage medium) of the executing computing device, for execution by the computing device.
  • the computer readable program instructions may execute entirely on a user's computer (e.g., the executing computing device), partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server.
  • the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
  • electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present disclosure.
  • These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
  • These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart(s) and/or block diagram(s) block or blocks.
  • the computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.
  • the instructions may initially be carried on a magnetic disk or solid state drive of a remote computer.
  • the remote computer may load the instructions and/or modules into its dynamic memory and send the instructions over a telephone, cable, or optical line using a modem.
  • a modem local to a server computing system may receive the data on the telephone/cable/optical line and use a converter device including the appropriate circuitry to place the data on a bus.
  • the bus may carry the data to a memory, from which a processor may retrieve and execute the instructions.
  • the instructions received by the memory may optionally be stored on a storage device (e.g., a solid state drive) either before or after execution by the computer processor.
  • each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s).
  • the functions noted in the blocks may occur out of the order noted in the Figures.
  • two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved.
  • certain blocks may be omitted in some implementations.
  • the methods and processes described herein are also not limited to any particular sequence, and the blocks or states relating thereto can be performed in other sequences that are appropriate.
  • any of the processes, methods, algorithms, elements, blocks, applications, or other functionality (or portions of functionality) described in the preceding sections may be embodied in, and/or fully or partially automated via, electronic hardware such application-specific processors (e.g., application-specific integrated circuits (ASICs)), programmable processors (e.g., field programmable gate arrays (FPGAs)), application-specific circuitry, and/or the like (any of which may also combine custom hard-wired logic, logic circuits, ASICs, FPGAs, etc. with custom programming/execution of software instructions to accomplish the techniques).
  • ASICs application-specific integrated circuits
  • FPGAs field programmable gate arrays
  • any of the above-mentioned processors, and/or devices incorporating any of the above-mentioned processors may be referred to herein as, for example, "computers,” “computer devices,” “computing devices,” “hardware computing devices,” “hardware processors,” “processing units,” and/or the like.
  • Computing devices of the above-embodiments may generally (but not necessarily) be controlled and/or coordinated by operating system software, such as Mac OS, iOS, Android, Chrome OS, Windows OS (e.g., Windows XP, Windows Vista, Windows 7, Windows 8, Windows 10, Windows Server, etc.), Windows CE, Unix, Linux, SunOS, Solaris, Blackberry OS, VxWorks, or other suitable operating systems.
  • operating system software such as Mac OS, iOS, Android, Chrome OS, Windows OS (e.g., Windows XP, Windows Vista, Windows 7, Windows 8, Windows 10, Windows Server, etc.), Windows CE, Unix, Linux, SunOS, Solaris, Blackberry OS, VxWorks, or other suitable operating systems.
  • the computing devices may be controlled by a proprietary operating system.
  • Conventional operating systems control and schedule computer processes for execution, perform memory management, provide file system, networking, I/O services, and provide a user interface functionality, such as a graphical user interface ("GUI”), among other things.
  • GUI graphical user interface
  • Figure 6 is a block diagram that illustrates a computer system 600 upon which various embodiments may be implemented.
  • Computer system 600 includes a bus 602 or other communication mechanism for communicating information, and a hardware processor, or multiple processors, 604 coupled with bus 602 for processing information.
  • Hardware processor(s) 604 may be, for example, one or more general purpose microprocessors.
  • Computer system 600 also includes a main memory 606, such as a random access memory (RAM), cache and/or other dynamic storage devices, coupled to bus 602 for storing information and instructions to be executed by processor 604.
  • Main memory 606 also may be used for storing temporary variables or other intermediate information during execution of instructions to be executed by processor 604.
  • Such instructions when stored in storage media accessible to processor 604, render computer system 600 into a special-purpose machine that is customized to perform the operations specified in the instructions.
  • Computer system 600 further includes a read only memory (ROM) 608 or other static storage device coupled to bus 602 for storing static information and instructions for processor 604.
  • ROM read only memory
  • a storage device 610 such as a magnetic disk, optical disk, or USB thumb drive (Flash drive), etc., is provided and coupled to bus 602 for storing information and instructions.
  • Computer system 600 may be coupled via bus 602 to a display 612, such as a cathode ray tube (CRT) or LCD display (or touch screen), for displaying information to a computer user.
  • a display 612 such as a cathode ray tube (CRT) or LCD display (or touch screen)
  • An input device 614 is coupled to bus 602 for communicating information and command selections to processor 604.
  • cursor control 616 is Another type of user input device
  • cursor control 616 such as a mouse, a trackball, or cursor direction keys for communicating direction information and command selections to processor 604 and for controlling cursor movement on display 612.
  • This input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allows the device to specify positions in a plane.
  • the same direction information and command selections as cursor control may be implemented via receiving touches on a touch screen without a cursor.
  • Computing system 600 may include a user interface module to implement a GUI that may be stored in a mass storage device as computer executable program instructions that are executed by the computing device(s).
  • Computer system 600 may further, as described below, implement the techniques described herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware and/or program logic which in combination with the computer system causes or programs computer system 600 to be a special-purpose machine.
  • the techniques herein are performed by computer system 600 in response to processor(s) 604 executing one or more sequences of one or more computer readable program instructions contained in main memory 606. Such instructions may be read into main memory 606 from another storage medium, such as storage device 610. Execution of the sequences of instructions contained in main memory 606 causes processor(s) 604 to perform the process steps described herein.
  • hard-wired circuitry may be used in place of or in combination with software instructions.
  • Various forms of computer readable storage media may be involved in carrying one or more sequences of one or more computer readable program instructions to processor 604 for execution.
  • the instructions may initially be carried on a magnetic disk or solid state drive of a remote computer.
  • the remote computer can load the instructions into its dynamic memory and send the instructions over a telephone line using a modem.
  • a modem local to computer system 600 can receive the data on the telephone line and use an infra-red transmitter to convert the data to an infra-red signal.
  • An infra-red detector can receive the data carried in the infra-red signal and appropriate circuitry can place the data on bus 602.
  • Bus 602 carries the data to main memory 606, from which processor 604 retrieves and executes the instructions.
  • the instructions received by main memory 606 may optionally be stored on storage device 610 either before or after execution by processor 604.
  • Computer system 600 also includes a communication interface 618 coupled to bus 602.
  • Communication interface 618 provides a two-way data communication coupling to a network link 620 that is connected to a local network 622.
  • communication interface 618 may be an integrated services digital network (ISDN) card, cable modem, satellite modem, or a modem to provide a data communication connection to a corresponding type of telephone line.
  • ISDN integrated services digital network
  • communication interface 618 may be a local area network (LAN) card to provide a data communication connection to a compatible LAN (or WAN component to communicated with a WAN).
  • LAN local area network
  • Wireless links may also be implemented.
  • communication interface 618 sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.
  • Network link 620 typically provides data communication through one or more networks to other data devices.
  • network link 620 may provide a connection through local network 622 to a host computer 624 or to data equipment operated by an Internet Service Provider (ISP) 626.
  • ISP 626 in turn provides data communication services through the world wide packet data communication network now commonly referred to as the "Internet" 628.
  • Internet 628 uses electrical, electromagnetic or optical signals that carry digital data streams.
  • the signals through the various networks and the signals on network link 620 and through communication interface 618, which carry the digital data to and from computer system 600, are example forms of transmission media.
  • Computer system 600 can send messages and receive data, including program code, through the network(s), network link 620 and communication interface 618.
  • a server 630 might transmit a requested code for an application program through Internet 628, ISP 626, local network 622 and communication interface 618.
  • the received code may be executed by processor 604 as it is received, and/or stored in storage device 610, or other non-volatile storage for later execution.
  • certain functionality may be accessible by a user through a web-based viewer (such as a web browser), or other suitable software program).
  • the user interface may be generated by a server computing system and transmitted to a web browser of the user (e.g., running on the user's computing system).
  • data e.g., user interface data
  • the user interface may be generated (e.g., the user interface data may be executed by a browser accessing a web service and may be configured to render the user interfaces based on the user interface data).
  • the user may then interact with the user interface through the web-browser.
  • User interfaces of certain implementations may be accessible through one or more dedicated software applications.
  • one or more of the computing devices and/or systems of the disclosure may include mobile computing devices, and user interfaces may be accessible through such mobile computing devices (for example, smartphones and/or tablets).
  • a general purpose computer comprising one or more processors should not be interpreted as excluding other computer components, and may possibly include such components as memory, input/output devices, and/or network interfaces, among others.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Databases & Information Systems (AREA)
  • Human Computer Interaction (AREA)
  • Data Mining & Analysis (AREA)
  • Computational Linguistics (AREA)
  • User Interface Of Digital Computer (AREA)
EP20199477.9A 2019-10-02 2020-09-30 Techniques améliorées pour construire des interfaces utilisateur Pending EP3800548A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201962909413P 2019-10-02 2019-10-02
US16/669,298 US11199955B2 (en) 2019-10-02 2019-10-30 Enhanced techniques for building user interfaces

Publications (1)

Publication Number Publication Date
EP3800548A1 true EP3800548A1 (fr) 2021-04-07

Family

ID=72717670

Family Applications (1)

Application Number Title Priority Date Filing Date
EP20199477.9A Pending EP3800548A1 (fr) 2019-10-02 2020-09-30 Techniques améliorées pour construire des interfaces utilisateur

Country Status (2)

Country Link
US (2) US11199955B2 (fr)
EP (1) EP3800548A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11199955B2 (en) 2019-10-02 2021-12-14 Palantir Technologies Inc. Enhanced techniques for building user interfaces

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115291876B (zh) * 2022-09-29 2023-03-17 安徽商信政通信息技术股份有限公司 一种表单设计工具构建方法、系统、电子设备和存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6300948B1 (en) * 1996-09-17 2001-10-09 Scott D. Geller Methods and systems for user interfaces and constraint handling in configuration software
US20090222749A1 (en) * 2008-02-29 2009-09-03 Business Objects, S.A. Apparatus and method for automated creation and update of a web service application
US10324609B2 (en) 2016-07-21 2019-06-18 Palantir Technologies Inc. System for providing dynamic linked panels in user interface

Family Cites Families (94)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5339433A (en) * 1992-11-19 1994-08-16 Borland International, Inc. Symbol browsing in an object-oriented development system
US5550971A (en) * 1993-06-30 1996-08-27 U S West Technologies, Inc. Method and system for generating a user interface adaptable to various database management systems
US6963920B1 (en) * 1993-11-19 2005-11-08 Rose Blush Software Llc Intellectual asset protocol for defining data exchange rules and formats for universal intellectual asset documents, and systems, methods, and computer program products related to same
US5642511A (en) * 1994-12-16 1997-06-24 International Business Machines Corporation System and method for providing a visual application builder framework
US5701400A (en) * 1995-03-08 1997-12-23 Amado; Carlos Armando Method and apparatus for applying if-then-else rules to data sets in a relational data base and generating from the results of application of said rules a database of diagnostics linked to said data sets to aid executive analysis of financial data
US5696702A (en) * 1995-04-17 1997-12-09 Skinner; Gary R. Time and work tracker
US5838563A (en) * 1996-04-12 1998-11-17 Fisher-Rosemont Systems, Inc. System for configuring a process control environment
JP3763937B2 (ja) * 1996-06-28 2006-04-05 富士通株式会社 オブジェクト指向プログラミング装置、およびオブジェクト結合プログラム記憶媒体
US5991535A (en) * 1996-07-03 1999-11-23 Sun Microsystems, Inc. Visual composition tool for constructing application programs using distributed objects on a distributed object network
US5949998A (en) * 1996-07-03 1999-09-07 Sun Microsystems, Inc. Filtering an object interface definition to determine services needed and provided
US6101509A (en) * 1996-09-27 2000-08-08 Apple Computer, Inc. Method and apparatus for transmitting documents over a network
US6253195B1 (en) * 1998-09-21 2001-06-26 Microsoft Corporation Optimized query tree
EP1135723A4 (fr) * 1998-11-30 2005-02-16 Siebel Systems Inc Systeme, procede et outil de developpement d'applications d'un serveur client
US7089530B1 (en) * 1999-05-17 2006-08-08 Invensys Systems, Inc. Process control configuration system with connection validation and configuration
US6754885B1 (en) * 1999-05-17 2004-06-22 Invensys Systems, Inc. Methods and apparatus for controlling object appearance in a process control configuration system
WO2000070417A1 (fr) * 1999-05-17 2000-11-23 The Foxboro Company Systeme de configuration de commande de processus via des objets parametres
US6963867B2 (en) * 1999-12-08 2005-11-08 A9.Com, Inc. Search query processing to provide category-ranked presentation of search results
US6829615B2 (en) * 2000-02-25 2004-12-07 International Business Machines Corporation Object type relationship graphical user interface
US7370040B1 (en) * 2000-11-21 2008-05-06 Microsoft Corporation Searching with adaptively configurable user interface and extensible query language
US7188091B2 (en) * 2001-03-21 2007-03-06 Resolutionebs, Inc. Rule processing system
US6996569B1 (en) * 2001-06-20 2006-02-07 Microstrategy Incorporated Systems and methods for custom grouping of data
US7055104B1 (en) * 2002-03-29 2006-05-30 Digeo, Inc. System and method for focused navigation using filters
US20040010629A1 (en) * 2001-11-01 2004-01-15 Telecommunications Research Associates System for accelerating delivery of electronic presentations
US7383513B2 (en) * 2002-09-25 2008-06-03 Oracle International Corporation Graphical condition builder for facilitating database queries
US20050015363A1 (en) * 2003-07-15 2005-01-20 International Business Machines Corporation Method and structure for representing complex query elements in a modelling tool
US7617196B2 (en) * 2003-10-22 2009-11-10 International Business Machines Corporation Context-sensitive term expansion with multiple levels of expansion
US20050108206A1 (en) * 2003-11-14 2005-05-19 Microsoft Corporation System and method for object-oriented interaction with heterogeneous data stores
US7590669B2 (en) * 2004-04-06 2009-09-15 Microsoft Corporation Managing client configuration data
US7603624B2 (en) * 2004-10-21 2009-10-13 Microsoft Corporation System and method for styling content in a graphical user interface control
US7590972B2 (en) * 2004-10-28 2009-09-15 Cogency Software, Inc. Role-oriented development environment
US20060095403A1 (en) * 2004-11-03 2006-05-04 International Business Machines Corporation Method, system and program product for filtering model objects
US8418075B2 (en) * 2004-11-16 2013-04-09 Open Text Inc. Spatially driven content presentation in a cellular environment
US7899756B2 (en) * 2004-12-01 2011-03-01 Xerox Corporation Critical parameter/requirements management process and environment
GB0500579D0 (en) * 2005-01-12 2005-02-16 Electra Entertainment Ltd Memory card handling
US7716630B2 (en) * 2005-06-27 2010-05-11 Ab Initio Technology Llc Managing parameters for graph-based computations
US7870162B2 (en) * 2005-07-29 2011-01-11 Sap Ag Method for generating properly formed expressions
US20070074156A1 (en) * 2005-09-01 2007-03-29 Microsoft Corporation Componentization of software computer programs
US8799166B1 (en) * 2005-10-11 2014-08-05 Apple Inc. Providing a gift of downloadable digital content
US8219919B2 (en) * 2006-02-06 2012-07-10 Attachmate Group Method for automating construction of the flow of data driven applications in an entity model
US7636697B1 (en) * 2007-01-29 2009-12-22 Ailive Inc. Method and system for rapid evaluation of logical expressions
US8042035B2 (en) * 2007-09-10 2011-10-18 International Business Machines Corporation Method and system for rapid access to frequently used or searched objects
US7437686B1 (en) * 2007-11-16 2008-10-14 International Business Machines Corporation Systems, methods and computer program products for graphical user interface presentation to implement filtering of a large unbounded hierarchy to avoid repetitive navigation
US8265053B2 (en) * 2008-08-12 2012-09-11 Texas Instruments Incorporated Configuration of rank indicator reporting instances
US8386960B1 (en) * 2008-08-29 2013-02-26 Adobe Systems Incorporated Building object interactions
US8484233B2 (en) * 2008-10-21 2013-07-09 Microsoft Corporation Facet, logic and textual-based query composer
US20100332350A1 (en) * 2009-06-24 2010-12-30 Cbs Interactive,Inc. Systems and methods for building a product
US20110107194A1 (en) * 2009-11-05 2011-05-05 Xu Cui System, methods, and user interface for conveniently creating citations in a document
US8756515B2 (en) * 2009-11-16 2014-06-17 Microsoft Corporation Dynamic editors for functionally composed UI
US20110271250A1 (en) * 2010-04-30 2011-11-03 Microsoft Corporation Software Development Tool
CA2706741C (fr) * 2010-06-29 2011-12-13 Ibm Canada Limited - Ibm Canada Limitee Gestion des parametres des expressions de filtrage
US9092410B1 (en) * 2010-08-16 2015-07-28 Amazon Technologies, Inc. Selection of popular highlights
US20120137238A1 (en) * 2010-11-29 2012-05-31 Microsoft Corporation Data visualization interface including range control and treemap integration
US8869052B2 (en) * 2010-11-30 2014-10-21 Sap Se Context-dependent object types in an integrated development environment
US8788545B2 (en) * 2010-12-08 2014-07-22 International Business Machines Corporation Calculating state of cryptographic objects and generating search filter for querying cryptographic objects
WO2012092263A1 (fr) * 2010-12-28 2012-07-05 Citrix Systems, Inc. Systèmes et procédés permettant un routage basé sur une politique pour de multiples bonds suivants
US8635530B2 (en) * 2011-02-09 2014-01-21 International Business Machines Corporation Statistical filtering of data using graphical user interfaces in information technology systems
EP2673942B1 (fr) * 2011-02-09 2015-08-19 Citrix Systems Inc. Systèmes et méthodes de rédirection en cache n-tier
US20120210296A1 (en) * 2011-02-14 2012-08-16 Microsoft Corporation Automatically creating business applications from description of business processes
US8271520B1 (en) * 2011-03-31 2012-09-18 Accenture Global Services Limited Expression editor tool
US9589070B2 (en) * 2011-10-10 2017-03-07 Salesforce.Com, Inc. Method and system for updating a filter logic expression representing a boolean filter
US9378526B2 (en) * 2012-03-02 2016-06-28 Palantir Technologies, Inc. System and method for accessing data objects via remote references
US9417760B2 (en) * 2012-04-13 2016-08-16 Google Inc. Auto-completion for user interface design
US9122383B2 (en) * 2012-04-16 2015-09-01 Hewlett-Packard Development Company, L.P. Object visualization
EP2859414A4 (fr) * 2012-06-07 2016-01-27 Zoll Medical Corp Systèmes et procédés de capture vidéo, retour vers l'utilisateur, signalement, paramètres adaptatifs et accès à des données à distance au cours d'une surveillance de la sécurité d'un véhicule
US10127810B2 (en) * 2012-06-07 2018-11-13 Zoll Medical Corporation Vehicle safety and driver condition monitoring, and geographic information based road safety systems
US8879112B2 (en) * 2012-09-28 2014-11-04 Interactive Memories, Inc. Method for optimizing printing quality for image-laden PDF files at lower file sizes
US20190188813A1 (en) * 2012-11-05 2019-06-20 Rosemarie D. Maljanian Healthcare accountability and support platform
US10001909B2 (en) * 2013-03-14 2018-06-19 Microsoft Technology Licensing, Llc Touch optimizations for range slider controls
US9773264B2 (en) * 2013-03-26 2017-09-26 Blackberry Limited Method for providing composite user interface controls and an online storefront for same
US9576263B2 (en) * 2013-09-19 2017-02-21 Oracle International Corporation Contextualized report building
US9348888B1 (en) * 2013-09-24 2016-05-24 Emc Corporation Iterative filter expression processing for filtering embedded data objects
US20150095365A1 (en) * 2013-09-30 2015-04-02 Microsoft Corporation Query building using schema
US8924872B1 (en) * 2013-10-18 2014-12-30 Palantir Technologies Inc. Overview user interface of emergency call data of a law enforcement agency
US9116975B2 (en) * 2013-10-18 2015-08-25 Palantir Technologies Inc. Systems and user interfaces for dynamic and interactive simultaneous querying of multiple data stores
US20150339373A1 (en) * 2014-05-20 2015-11-26 Matthew Christian Carlson Graphical interface for relevance-based rendering of electronic messages from multiple accounts
US9454281B2 (en) * 2014-09-03 2016-09-27 Palantir Technologies Inc. System for providing dynamic linked panels in user interface
US10867273B2 (en) * 2014-09-26 2020-12-15 Oracle International Corporation Interface for expanding logical combinations based on relative placement
US9892269B2 (en) * 2015-06-11 2018-02-13 Qualcomm Incorporated Techniques for data monitoring to mitigate transitive problem in object-oriented contexts
US10839010B2 (en) * 2015-06-30 2020-11-17 International Business Machines Corporation Compact visualization of query search results
WO2017024113A1 (fr) * 2015-08-06 2017-02-09 Schlumberger Technology Corporation Procédé de l'évaluation des propriétés de transport de fluide dans une formation géologique hétérogène
US10643291B2 (en) * 2015-09-28 2020-05-05 Smartvid.io, Inc. Media management system
US10824403B2 (en) * 2015-10-23 2020-11-03 Oracle International Corporation Application builder with automated data objects creation
US10437423B2 (en) * 2015-10-30 2019-10-08 Hyland Software, Inc. Methods and apparatuses for providing an infinitely scrolling accumulator
US10810271B2 (en) * 2016-06-30 2020-10-20 Atlassian Pty Ltd Systems and methods for issue tracking systems
US20180165724A1 (en) * 2016-12-13 2018-06-14 International Business Machines Corporation Method and system for contextual business intelligence report generation and display
US10133953B2 (en) * 2017-01-26 2018-11-20 Nice Ltd. System and method for enabling graphic-based interoperability with a run-time application
US10402174B2 (en) * 2017-08-25 2019-09-03 Salesforce.Com, Inc. Overriding component attributes in a web application builder
US10509633B2 (en) * 2017-08-30 2019-12-17 Salesforce.Com, Inc. Base editor component in a web application builder framework
KR101944353B1 (ko) * 2017-12-20 2019-04-17 주식회사 카카오 챗봇 빌더 사용자 인터페이스 제공 방법 및 장치
US10846060B2 (en) * 2018-01-29 2020-11-24 Q2 Software, Inc. Single-page web application builder system and method based on a finite-state machine
US10620937B1 (en) * 2018-06-01 2020-04-14 Appian Corporation Automated backward-compatible function updates
US11733669B2 (en) * 2019-09-27 2023-08-22 Rockwell Automation Technologies, Inc. Task based configuration presentation context
US11199955B2 (en) 2019-10-02 2021-12-14 Palantir Technologies Inc. Enhanced techniques for building user interfaces
US11086602B2 (en) * 2019-11-13 2021-08-10 Palantir Technologies Inc. Workflow application and user interface builder integrating objects, relationships, and actions

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6300948B1 (en) * 1996-09-17 2001-10-09 Scott D. Geller Methods and systems for user interfaces and constraint handling in configuration software
US20090222749A1 (en) * 2008-02-29 2009-09-03 Business Objects, S.A. Apparatus and method for automated creation and update of a web service application
US10324609B2 (en) 2016-07-21 2019-06-18 Palantir Technologies Inc. System for providing dynamic linked panels in user interface

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
DILLON, A., USER INTERFACE DESIGN, 2003
MACMILLAN, ENCYCLOPEDIA OF COGNITIVE SCIENCE, vol. 4, pages 453 - 458

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11199955B2 (en) 2019-10-02 2021-12-14 Palantir Technologies Inc. Enhanced techniques for building user interfaces

Also Published As

Publication number Publication date
US20210103380A1 (en) 2021-04-08
US11199955B2 (en) 2021-12-14
US20220244837A1 (en) 2022-08-04

Similar Documents

Publication Publication Date Title
US12079357B2 (en) Multi-user access controls in electronic simultaneously editable document editor
US11402985B2 (en) Systems and user interfaces for dynamic and interactive access of, investigation of, and analysis of data objects stored in one or more databases
US10824632B2 (en) System and method for generating event visualizations
US12026810B2 (en) Ontology-backed automatic chart creation
US10360252B1 (en) Detection and enrichment of missing data or metadata for large data sets
US11262904B2 (en) Object time series system and investigation graphical user interface
US20220244837A1 (en) Enhanced techniques for building user interfaces
US11842171B2 (en) Function access system
US12124464B2 (en) Object-centric data analysis system and graphical user interface
US20210349803A1 (en) Audit logging database system and user interface
US11580164B1 (en) Ontology-based time series visualization and analysis
US20230121615A1 (en) Central user interface for accessing and upgrading of dataset integrations

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN PUBLISHED

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20211006

RBV Designated contracting states (corrected)

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20220303

RAP3 Party data changed (applicant data changed or rights of an application transferred)

Owner name: PALANTIR TECHNOLOGIES INC.