Abstract:
Methods, systems and articles of manufacture are provided for migrating entity relationship data residing in an object oriented program environment to a relational database schema. Further, functionality is provided to facilitate more efficient searching and reconstruction of the entity relationship data in the relational database.
Abstract:
Methods, systems and articles of manufacture are provided for accessing data within data repositories. Public UDTFs, private UDTFs and a metadata processor are utilized to provide access to data residing in a variety of data repositories.
Abstract:
Methods, systems, and articles of manufacture that may be used to attach annotations to a particular view of data described by the annotation are provided. The annotation may be attached in a manner that allows the annotation to be viewed when subsequent views having at least some visible cells in common with the annotated view are displayed. An annotation created for a view of data may be stored with links to each cell visible in the view. When a predetermined set of cells visible in the annotated view are subsequently displayed in another view, the annotation may be retrieved via the cell links and an indication of the annotation may be provided.
Abstract:
Methods, systems, and articles of manufacture that may be used for identifying and indicating annotations made for a variety of different type (i.e., heterogeneous) data objects are provided. According to some embodiments, an annotation store may be queried to identify annotations for data objects in a current view of data. For certain identifiable portions of the view (e.g., a row in a relational view), a callable function may be created that returns a set of indicia maps indicating which objects in the portions are annotated. Bits in an indicia map may correspond to different objects (e.g., individual cells in a row or the row itself). Using these indicia maps, an indication of which data objects are annotated may be provided in the view, for example, by displaying annotation icons proximate annotated objects.
Abstract:
Methods, systems, and articles of manufacture for indexing annotations made for a variety of different type (i.e., heterogeneous) data objects are provided. A set of parameters uniquely identifying an annotated data object may be converted to an index comprising a set of index values, each corresponding to a column in a homogeneous index table. In order to accommodate the indexing of heterogeneous data objects, a mapping may be provided for each different type (or classification) of data object that may be annotated, that defines how the identifying parameters of that type will be mapped to the columns of the homogeneous index table.
Abstract:
Methods, systems and articles of manufacture are disclosed for providing secure access to data. Public UDTFs, private UDTFs and a metadata processor are utilized to facilitate secure access to data residing in a variety of data repositories.
Abstract:
Techniques are provided for accessing data within data repositories. Public UDTFs, private UDTFs and a metadata processor are utilized to provide access to data residing in a variety of data repositories.
Abstract:
The present invention generally provides methods, systems, and articles of manufacture for managing an annotation system that includes storing annotations for a document family, i.e., a series of versions of a data source. Annotations created for one version of the data source may be viewed in context from both subsequent and prior versions of the same data source. Embodiments of the invention associate annotations with both a data source “family identifier” as well as a “version identifier.” Other than adding a family ID to the data source, the data source remains unchanged. The family ID is maintained across different versions of the data source, whereas version IDs are determined for a specific version of the data source. Version IDs can be constructed from each data source directly, and do not need to be stored.
Abstract:
Methods, systems, and articles of manufacture for referencing a selection of data including a plurality of individual data points (e.g., database cells) are provided. Rather than store a reference to each individual data point, only sufficient information necessary to describe a bounding edge of the data selection (an “edge definition”) may be stored, thus significantly reducing the amount of storage. Depending on the application, edge definitions may be used to describe two-dimensional or higher order selections of data.
Abstract:
The present invention generally provides methods, systems, and articles of manufacture for managing an annotation system that includes storing annotations for a document family, i.e., a series of versions of a data source. Annotations created for one version of the data source may be viewed in context from both subsequent and prior versions of the same data source. Embodiments of the invention associate annotations with both a data source “family identifier” as well as a “version identifier.” Other than adding a family ID to the data source, the data source remains unchanged. The family ID is maintained across different versions of the data source, whereas version IDs are determined for a specific version of the data source. Version IDs can be constructed from each data source directly, and do not need to be stored.