US20070073770A1 - Methods, systems, and computer program products for resource-to-resource metadata association - Google Patents
Methods, systems, and computer program products for resource-to-resource metadata association Download PDFInfo
- Publication number
- US20070073770A1 US20070073770A1 US11/239,276 US23927605A US2007073770A1 US 20070073770 A1 US20070073770 A1 US 20070073770A1 US 23927605 A US23927605 A US 23927605A US 2007073770 A1 US2007073770 A1 US 2007073770A1
- Authority
- US
- United States
- Prior art keywords
- resource
- metadata
- destination
- source
- data
- 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.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/40—Information retrieval; Database structures therefor; File system structures therefor of multimedia data, e.g. slideshows comprising image and additional audio data
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
- G06F16/258—Data format conversion from or to a database
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/30—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
- G06F16/38—Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/50—Information retrieval; Database structures therefor; File system structures therefor of still image data
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/50—Information retrieval; Database structures therefor; File system structures therefor of still image data
- G06F16/53—Querying
Definitions
- the subject matter described herein relates to methods, systems, and computer program products for automatically associating data with a resource as metadata. More particularly, the subject matter described herein relates to methods, systems, and computer program products for resource-to-resource metadata association.
- files are used to store data created by users, software applications, and devices.
- a computer file may be associated with descriptive information regarding the contents or other aspects of the file. This descriptive information is referred to as metadata.
- metadata is stored in the file. In other instances, metadata is stored outside of the file but is linked to the file.
- Some application programs allow users to manually create and associate metadata with a file.
- digital image organization programs sold with digital cameras may allow a userto manually enter captions to be stored and/or displayed with an image. While such manual metadata creation tools are useful, they require unnecessary time and labor on the part of the end user, because the end user is required to manually input the metadata for each resource.
- Some current computer operating systems include limited functionality for automatically associating file system information with files.
- the Windows® 2000 and Windows® XP operating systems automatically associate a file's location in a file directory tree with the file in response to the file being stored in a particular directory.
- the Windows® 2000 and Windows® XP operating systems do not allow mapping between data or metadata of one resource type to metadata fields or tags of another resource type where the data is independent of location information used by the file system to identify a file's location.
- Newer operating systems include file systems that are more database-oriented than previous operating systems.
- the Longhorn operating system expected to be released by Microsoft in 2006 includes an unstructured file system and a structured file system.
- the unstructured file system is the same NTFS file system included in Windows® 2000 and Windows® XP.
- the structured file system is a database-oriented file system in which file properties are stored and organized as structured database objects.
- When an application modifies unstructured properties of a file structured database objects corresponding to the unstructured properties are updated.
- the process of updating the structured database objects is referred to as promotion.
- the promotion process only maps existing unstructured properties of the file to structured objects maintained by the structured file system.
- the subject matter described herein includes a method for resource-to-resource metadata association.
- the method includes identifying the source resource and identifying an existing destination resource.
- a type of the source and/or the destination resource is also identified.
- a transform is selected for mapping at least one data value associated with the source resource to the destination resource as metadata.
- a data value associated with the source resource is associated with the destination resource as metadata.
- the metadata is independent of an association between the destination resource and a file system for storing the destination resource.
- the subject matter described herein for resource-to-resource metadata association may be implemented using a computer program product comprising computer executable instructions embodied in a computer readable medium.
- Exemplary computer readable media suitable for implementing the subject matter described herein include disk memory devices, chip memory devices, programmable logic devices, application specific integrated circuits, and downloadable electrical signals.
- a computer program product for implementing the subject matter described herein may be implemented on a single device or computing platform or may be distributed across multiple devices or computing platforms.
- FIG. 1 is a flow chart illustrating exemplary process for resource-to-resource metadata association according to an embodiment of the subject matter described herein;
- FIG. 2 is a block diagram illustrating an exemplary system for resource-to-resource metadata association according to an embodiment of the subject matter described herein;
- FIGS. 3A and 3B are a flow chart illustrating an exemplary process for resource-to-resource metadata association according to an embodiment of the subject matter described herein;
- FIG. 4 is a block diagram of an exemplary protocol handler according to an embodiment of the subject matter described herein;
- FIG. 5 is a block diagram illustrating an exemplary content handler according to an embodiment of the subject matter described herein;
- FIG. 6 is a block diagram illustrating a portion of an exemplary database for storing metadata apart from a resource according to an embodiment of the subject matter described herein;
- FIG. 7 is a block diagram of a portion of an exemplary database for storing data apart from a resource according to an embodiment of the subject matter described herein;
- FIG. 8 is a block diagram illustrating an exemplary database for storing resource metadata apart from a resource according to embodiment of the subject matter described herein;
- FIG. 9 is a block diagram illustrating an exemplary desktop or application pane demonstrating user action for resource-to-resource metadata association according to an embodiment of the subject matter described herein;
- FIG. 10 is a block diagram illustrating an exemplary desktop or application pane demonstrating user action for resource-to-resource metadata association according to an embodiment of the subject matter described herein;
- FIG. 11 is a block diagram illustrating an exemplary desktop or application pane demonstrating modal input for resource-to-resource metadata association according to an embodiment of the subject matter described herein;
- FIG. 12 is a block diagram illustrating an exemplary desktop or application pane demonstrating a metadata mixer for resource-to-resource metadata association according to an embodiment of the subject matter described herein;
- FIG. 13 is a block diagram illustrating an exemplary desktop or application pane for resource-to-resource metadata association where one of the resources is data accessible through an executing application according to an embodiment of the subject matter described herein;
- FIG. 14 is a block diagram illustrating an exemplary desktop or application pane including a dialogue box for resource-to-resource metadata association according to an embodiment of the subject matter described herein;
- FIG. 15 is a block diagram illustrating an exemplary user interface for automatically exchanging metadata between a resource and a resource cluster according to an embodiment of the subject matter described herein.
- FIG. 1 is a flow chart illustrating an exemplary process for resource-to-resource metadata association according to an embodiment of the subject matter described herein.
- a source resource is identified.
- the source resource may be a system file, application, or other resource recognized by a computer operating system.
- an existing destination resource is identified.
- the destination resource may likewise be a system file, an executable application, or other resource recognized by a computer operating system.
- the type of the source and/or the destination resource is identified.
- a transform for mapping one or more data values is associated with the source resource to the destination resource as metadata is selected.
- at least one data value associated with the source resource is mapped to the destination resource as metadata.
- FIG. 2 is a block diagram illustrating one example of such a system.
- the system includes means for identifying source and destination resources and a type of at least one of the source and the destination resource.
- metadata hub 200 may identify source and destination resource types and invoke an appropriate protocol handler 202 A- 202 E that provides access to the source and destination resources in a resource-to-resource metadata transaction.
- Metadata hub 200 may register itself with the operating system to receive notification when a metadata association action occurs. When such an action occurs, the operating system may communicate the source and destination resource identifiers to metadata hub 200 .
- Metadata hub 200 may also include an application programming interface (API) that allows programmers to write applications that trigger hub functions. For example, an associate function that may be defined for metadata hub 200 may be accessed using the following call:
- the system illustrated in FIG. 1 may further include means for selecting, based on the type, a transform for mapping data values associated with the source resource to the destination resource as metadata.
- metadata hub 200 may invoke appropriate content handlers 204 A- 204 H based on the source and destination resource types to access data and/or metadata associated with the source and destination resources.
- Metadata hub 200 may further invoke transformer 205 to perform any conversions between data exchanged between the source and destination resource types as metadata.
- the conversions may include data format conversions and mappings from source resource metadata fields to destination resource metadata fields.
- Transformer 205 may access one or more transforms stored in a transform data store 206 to perform the appropriate conversions.
- transformer 205 may be implemented using extensible style sheet transformations (XSLT). In alternate implementations, scripts and/or executables may be used.
- XSLT extensible style sheet transformations
- Metadata hub 200 may identify data items as candidates for exclusion for metadata association. For example, certain data associated with the source resource may not be appropriate for association with a destination resource as metadata. Metadata hub 200 may identify the data that is not appropriate for association with a destination resource as metadata when transformer 205 fails to map the data to the destination resource. In one example, if the source resource is an image file with metadata tags relating to the tint or brightness of the image, such data values may not be appropriate for inclusion in a document relating to the image. Metadata hub 200 may identify such data from the source resource as a candidate for exclusion and allow the user to manually determine whether to map or exclude the data value from association with the destination resource as metadata. Alternatively, metadata hub 200 may automatically exclude data from the source resource that does not map to the destination resource as metadata.
- metadata hub 200 may present a user with a menu of source resource data values and destination resource metadata fields.
- the source data items presented in the menu may include all source data items, source data items that are determined to be appropriate for association with the destination resource as metadata, or source data items that did not automatically map to one or more destination resource metadata fields.
- the destination metadata fields that are presented may likewise be a complete set of metadata fields of the destination resource, a set of fields to which source resource data maps, or a set of fields for which source data mapping failed.
- metadata hub 200 may monitor user input for association actions for associating source resource data with destination metadata fields and perform the user-selected associations.
- An exemplary menu that may be presented by metadata hub 200 will be described in detail below.
- Content handlers 204 A- 204 H understand the format of the data and the metadata and any rules or restrictions that must be enforced on both the structure and values of the data or metadata.
- Transformer 205 may apply a transform or chain of transforms from transform data store 206 where the input is provided by the source content handler and the output is compatible with the destination content handler. It is not required for the input to the transform to be the same format that the content handler receives. That is, the source content handler may perform a format conversion to make it compatible with the transform. Likewise, the output of the last transform is not required to be the same format as the destination. The destination content handler may convert the output from the transform to a format compatible with a destination resource.
- the system illustrated in FIG. 2 may further include means for associating, based on the transform, at least one of the data values associated with the source resource with the destination resource as metadata.
- metadata hub 200 may invoke the appropriate content handlers 204 A- 204 H and transformers 205 to associate data from a source resource with a destination resource as metadata.
- the system resources for which it may be desirable to perform metadata to metadata association include files accessible via a file system 208 , or content accessible via one or more applications 210 A- 210 E.
- files accessible via a file system 208 or content accessible via one or more applications 210 A- 210 E.
- applications 210 A- 210 E For example, it may be desirable to associate data from a file in file system 208 with an address book entry accessible via mail client 210 E or vice versa.
- Specific metadata association examples will be described in detail below.
- metadata is stored separately from resources in various metadata databases 212 A- 212 C.
- the metadata or references to the metadata may be directly associated or embedded in the resource. Either embodiment is intended to be within the scope of the subject matter described herein.
- metadata hub 200 may update the corresponding entry in one of metadata databases 212 A- 212 C.
- metadata hub 200 may write the data or reference to the appropriate metadata fields within the resource.
- a communication subsystem 214 provides the mechanism by which metadata hub 200 can access system resources 208 and 210 A- 210 E as well as metadata databases 212 A- 212 C.
- communication subsystem 212 may be implemented using a network communications protocol stack, such as a TCP/IP protocol stack.
- FIGS. 3A and 3B are a flow chart illustrating an exemplary process for associating data from a source resource to a destination resource as metadata using the components illustrated in FIG. 2 .
- identifiers of resources to be associated are determined. The identifiers may be received in response to selection of the source and destination resources by a user via a user interface.
- the directionality of the association is determined, and, for each direction, the actions specified by the remaining blocks in FIG. 3 are executed.
- Directionality for metadata association may be source-to-destination, destination-to-source, or both.
- mapable data refers to data in the source resource that is may be accessed by a source content handler mapping to a destination resource. If mapable data is present, control proceeds to block 308 where a source content handler is invoked. The source content handler may be invoked based on the source resource type to extract data from the source resource. The destination resource type may also be used to determine the source content handler to invoke and data to extract. Referring to FIG. 3B , in block 310 , it is determined whether a data conversion is required.
- Block 312 may be performed by content handlers and/or transformer 205 as described above with respect to FIG. 2 .
- source data is associated with the destination resource as metadata by invoking the content handler for the destination type.
- the mapped data can be written to a metadata file associated with the destination resource. In an alternate implementation, the mapped data may be written directly to the destination resource.
- the entire source resource may be associated with the destination-resource. Accordingly, control may proceed to block 316 where the entire source resource is associated with the destination resource. Additionally, the decision made in block 306 may be predefined as “no” for certain source and/or destination resource types. For example, in the case of a contact associated with a contact management application, such as Microsoft Outlook®, it may be desirable to associate the entire source resource with the contact whether there is mapable data in the source resource or not. This example is shown below with reference to FIG. 13 .
- FIG. 4 is a block diagram illustrating an exemplary protocol handler 202 C for a mail client.
- mail client protocol handler 202 C uses a mail client proprietary application programming interface (API) library 400 to gain access to messages, folders, address books, or other data accessible via a mail client for which it may be desirable to associate with another resource as metadata or for which it may be desirable to associate data from another resource as metadata.
- Protocol handler 202 C handles requests and responses to and from the mail client and forwards and receives data to and from the appropriate content handlers for the source and destination resources.
- API application programming interface
- FIG. 5 is a block diagram of an exemplary content handler 204 .
- content handler 204 is a generic content handler capable of parsing and formatting keyword/value pairs.
- Content handler 204 includes a resource ID handler for parsing resource identifiers received from hub 200 and a keyword/value formatter/parser 502 for interpreting keyword value pairs associated with a source or a destination resource.
- resource ID handler for parsing resource identifiers received from hub 200
- keyword/value formatter/parser 502 for interpreting keyword value pairs associated with a source or a destination resource.
- data associated with a source or a destination resource may include metadata tags that correspond to the keywords and corresponding data values paired with each keyword.
- FIGS. 6 and 7 illustrate exemplary database structures that may be used to link metadata with resources. More particularly, FIG. 6 illustrates an example of a resource table, a link table, and a type table used to associate each resource with metadata. More particularly, in FIG. 6 , a single resource table entry 600 A of resource table 600 is shown for an image resource type. Entry 600 A includes an identifier that links the resource to a link table 602 . Link table 602 includes a link to an image schema table 604 A that stores metadata for an image resource.
- FIG. 7 is a higher level view of the database illustrated in FIG. 6 . As illustrated in FIG. 7 , each resource type may include its own schema table 604 A- 604 C that contains the associated metadata.
- FIG. 8 illustrates an example of another data structure that may be used to associate a resource with metadata.
- the data structure includes a resource table 800 that stores a resource identifier and its type.
- a schema table 802 links the resource type to keyword-value pairs that represent metadata fields and data for each resource type.
- the relationships between the tables are shown as bidirectional.
- the subject matter described herein is not limited to bidirectional associations between resources and metadata.
- the relationships may be unidirectional.
- many-to-many, one-to-one, one-to-many, one-to-zero, and relationships with other cardinalities between resources and metadata are supported without departing from the scope of the subject matter described herein.
- FIG. 9 is a block diagram illustrating an exemplary desktop or application pane associated with resource-to-resource metadata association according to an embodiment of the subject matter described herein.
- the desktop or application pane may be monitored by hub 200 illustrated in FIG. 2 .
- desktop or application pane 900 includes a plurality of resource representations 902 A- 902 E.
- Resource representations 902 A- 902 E may be graphical and/or textural representations of resources, as defined by the underlying operating system.
- a user selects a resource representation 902 A that corresponds to a PDF file. The user drags resource representation 902 A and hovers resource representation 902 A over resource representation 902 E and resource representation 902 D.
- hub 200 may invoke the appropriate content handlers, protocol handlers, and transformer 205 for associating data from resource 902 A with resources 902 E and 902 D.
- transformer 205 may be configured to associate data from resources 902 E and 902 D with resource 902 A in response to this drag hover action.
- all appropriate data extracted from resource 902 A may be automatically associated with resources 902 E and 902 D as metadata without further input from the user.
- hub 200 may associate data from resource 902 A with resources 902 E and 902 D for which mappings are defined in transform data store 206 .
- the user may be presented with a menu that allows the user to manually associate the unmapped data with the destination resource as metadata.
- An exemplary user interface for performing such mapping will be described in detail below.
- data associated with the source resource may be displayed, metadata fields associated with the destination resource 902 E or 902 F may be displayed, and the user may manually select all of the mappings. The selected mapping may be saved and automatically applied in like scenarios in the future.
- FIG. 10 is a block diagram illustrating desktop or application pane 900 in which the user performs resource-to-resource metadata association using drag-and-drop actions.
- the user selects resource representation 902 E, drags resource representation 902 E over resource representation 902 A and drops resource representation 902 E onto resource representation 902 A.
- the user repeats the same actions for dropping resource representation 902 E onto resource representation 902 B.
- the result of the two actions illustrated in FIG. 10 are the association of data extracted from the resource represented by resource representation 902 E with resources represented by resource representations 902 A and 902 B as metadata.
- resource representation 902 B is a file system folder.
- the data extracted from resource representation 902 B may be data associated with the folder itself, may be data associated with resources linked to the folder, or may be data associated with both.
- the data associated with resource representation 902 E as metadata as a result of drag-and-drop action will be independent of an association between resource representation 902 E and the file system.
- data indicating a path to a location in the file system or data indicating a category within the file system is not associated with resource representation 902 E as a result of the drag-and-drop action.
- transformer 205 can be configured so that the same drag-and-drop action illustrated in FIG. 10 results in the association of data extracted from the resource represented by resource representations 902 A and 902 B with resources represented by resource representation 902 E as metadata.
- FIG. 11 is a block diagram illustrating yet another example of desktop or application pane 900 where the user performs resource-to-resource metadata association using modal input.
- modal input it is meant that once an indication is received to enter the metadata association mode, user input is interpreted in the context of the mode rather than normal desktop of application input processing.
- a user can assign default actions to a context menu associated with a resource using a resource management interface, such as Windows Explorer®.
- a create relation action and an associate metadata action have been defined for resource 902 E such that when a user clicks on resource 902 E, menu 1100 appears with these options.
- the associate metadata action when selected causes the desktop or application pane to enter metadata association mode, allowing a user to associate metadata between source and destination resources using drag-and-drop or drag-and-hover, which would have other results in the normal desktop or application mode.
- FIG. 12 is a block diagram illustrating another example of desktop or application pane 900 where resource-to-resource metadata association is performed using a metadata mixer.
- a metadata mixer representation 1200 is displayed.
- Metadata mixer representation may represent access to an application that creates metadata associations between resources that are associated with it, such as hub 200 . For example, if resources A and B are associated with metadata mixer representation 1200 , metadata from resource A may be associated with resource B and vice versa.
- resource representations 902 B, 902 E, and 902 F are associated with mixer representation 1200 .
- Representation 902 B is identified as a metadata source.
- Representations 902 E and 902 F are identified as metadata targets. Accordingly, data from the resource represented by representation 902 B may be associated with the resources represented by representations 902 E and 902 F using the methods described above.
- mixer representation 1200 may have two sides. For example, resources associated with the left side of mixer representation 1200 may be designated as targets and resource representations associated with the right side of mixer representation 1200 may be designated as sources.
- a mouse gesture may be used to indicate a source resource and a different mouse gesture may be used to indicate a destination resource.
- mouse gestures may be used in combination with keyboard input to distinguish between source and target resources. For example, the user may depress the S key after selecting a resource to identify that resource as the source and the D key after selecting a resource to identify the resource as a destination.
- FIG. 13 illustrates another example of desktop or application pane 900 where data from an open application is associated with a resource as metadata and where a resource is associated with data from an open application as metadata.
- an address book application 1300 displays contact information associated with an email address book.
- the user drags and drops contact B information on to resource representation 902 A, which corresponds to a PDF file.
- the user may be presented with a menu or dialogue box that allows the user to select source data and corresponding target fields.
- FIG. 14 illustrates an example of such an interface.
- desktop or application pane 900 includes a dialogue box 1400 that displays source data fields in the left hand column and target resource metadata fields in the right hand column.
- the user may select data in the left hand column and associate that data with the metadata fields in the right hand column by any suitable action, such as drag-and-drop or drag-and-hover.
- any suitable action such as drag-and-drop or drag-and-hover.
- the user may define and associate custom metadata fields and values for the source resource and custom metadata fields for the destination resource.
- the source content handler may allow custom metadata fields and data to be defined for and associated with the source resource.
- the destination content handler may allow custom metadata fields to be defined for and associated with the destination resource.
- a transform may be defined for mapping the data in the custom metadata fields from the source resource to the custom metadata fields of the destination resource. For example, once custom source and/or destination fields are defined, the user may perform the initial mapping from source data to destination fields manually using an interface such as that illustrated in FIG. 14 .
- Metadata hub 200 may record the mappings and store the mappings in transform data store 206 . The next time that resources of the type for which the transform was defined are associated with each other, transformer 205 may access transform data store 206 , extract the mapping, and perform the association.
- a user may associate a resource representation 902 D with data displayed in address book application 1300 .
- the user may associate a picture with a contact.
- the example illustrated by the lower arrow in FIG. 13 illustrates the association of an entire resource with a destination as metadata. That is, the resource represented by resource representation 902 D becomes metadata of the destination, which in this case is the contact.
- FIG. 15 is a block diagram illustrating another example of resource-to-resource metadata association according to an embodiment of the subject matter described herein.
- resource clusters 1500 , 1502 , 1504 , 1506 , and 1508 each include multiple resource representations 1510 that have at least some metadata in common.
- resource cluster 1500 includes the metadata “Boston”, which can be used in resource-to-resource metadata association.
- a user may move resource representation 902 to a location corresponding to one of the clusters and drop resource representation 902 onto the cluster or hover resource representation 902 over the cluster.
- data that is associated with the cluster as metadata may be associated with the resource represented by resource representation 902 or vice versa.
- resource representations can be members of more than one cluster.
- resource representation ‘C’ is a member of two different clusters.
Abstract
Description
- This application is related to a commonly-assigned, co-pending U.S. patent application entitled, “Methods, Systems, and Computer Program Products for Automatically Associating Data with a Resource as Metadata Based on a Characteristic of the Resource” (serial no. not yet assigned) and a U.S. patent application entitled, “User Interfaces and Related Methods, Systems, and Computer Program Products for Automatically Associating Data with a Resource as Metadata” (serial no. not yet assigned), both filed on even date herewith, the disclosure of each of which is incorporated herein by reference in its entirety.
- The subject matter described herein relates to methods, systems, and computer program products for automatically associating data with a resource as metadata. More particularly, the subject matter described herein relates to methods, systems, and computer program products for resource-to-resource metadata association.
- In computer file systems, files are used to store data created by users, software applications, and devices. In addition to user-created content, a computer file may be associated with descriptive information regarding the contents or other aspects of the file. This descriptive information is referred to as metadata. In some instances, metadata is stored in the file. In other instances, metadata is stored outside of the file but is linked to the file.
- Some application programs allow users to manually create and associate metadata with a file. For example, digital image organization programs sold with digital cameras may allow a userto manually enter captions to be stored and/or displayed with an image. While such manual metadata creation tools are useful, they require unnecessary time and labor on the part of the end user, because the end user is required to manually input the metadata for each resource.
- Some current computer operating systems include limited functionality for automatically associating file system information with files. For example, the Windows® 2000 and Windows® XP operating systems automatically associate a file's location in a file directory tree with the file in response to the file being stored in a particular directory. However, the Windows® 2000 and Windows® XP operating systems do not allow mapping between data or metadata of one resource type to metadata fields or tags of another resource type where the data is independent of location information used by the file system to identify a file's location.
- Newer operating systems include file systems that are more database-oriented than previous operating systems. For example, the Longhorn operating system expected to be released by Microsoft in 2006 includes an unstructured file system and a structured file system. The unstructured file system is the same NTFS file system included in Windows® 2000 and Windows® XP. The structured file system is a database-oriented file system in which file properties are stored and organized as structured database objects. When an application modifies unstructured properties of a file, structured database objects corresponding to the unstructured properties are updated. The process of updating the structured database objects is referred to as promotion. However, the promotion process only maps existing unstructured properties of the file to structured objects maintained by the structured file system. There is no ability in the promotion process to automatically map and associate file-system-independent data from one resource of one type to another resource of the same or a different type. In addition, there is no ability in the promotion process to automatically associate data from one resource as metadata in another “destination” resource, where the metadata is independent of an association between the destination resource and a file system for storing the destination resource.
- Accordingly, there exists a long felt need for methods, systems, and computer program products for resource-to-resource metadata association.
- According to one aspect, the subject matter described herein includes a method for resource-to-resource metadata association. The method includes identifying the source resource and identifying an existing destination resource. A type of the source and/or the destination resource is also identified. Based on the type, a transform is selected for mapping at least one data value associated with the source resource to the destination resource as metadata. Based on the transform, a data value associated with the source resource is associated with the destination resource as metadata. The metadata is independent of an association between the destination resource and a file system for storing the destination resource.
- The subject matter described herein for resource-to-resource metadata association may be implemented using a computer program product comprising computer executable instructions embodied in a computer readable medium. Exemplary computer readable media suitable for implementing the subject matter described herein include disk memory devices, chip memory devices, programmable logic devices, application specific integrated circuits, and downloadable electrical signals. In addition, a computer program product for implementing the subject matter described herein may be implemented on a single device or computing platform or may be distributed across multiple devices or computing platforms.
- Preferred embodiments of the subject matter described herein will now be explained with reference to the accompanying drawings of which:
-
FIG. 1 is a flow chart illustrating exemplary process for resource-to-resource metadata association according to an embodiment of the subject matter described herein; -
FIG. 2 is a block diagram illustrating an exemplary system for resource-to-resource metadata association according to an embodiment of the subject matter described herein; -
FIGS. 3A and 3B are a flow chart illustrating an exemplary process for resource-to-resource metadata association according to an embodiment of the subject matter described herein; -
FIG. 4 is a block diagram of an exemplary protocol handler according to an embodiment of the subject matter described herein; -
FIG. 5 is a block diagram illustrating an exemplary content handler according to an embodiment of the subject matter described herein; -
FIG. 6 is a block diagram illustrating a portion of an exemplary database for storing metadata apart from a resource according to an embodiment of the subject matter described herein; -
FIG. 7 is a block diagram of a portion of an exemplary database for storing data apart from a resource according to an embodiment of the subject matter described herein; -
FIG. 8 is a block diagram illustrating an exemplary database for storing resource metadata apart from a resource according to embodiment of the subject matter described herein; -
FIG. 9 is a block diagram illustrating an exemplary desktop or application pane demonstrating user action for resource-to-resource metadata association according to an embodiment of the subject matter described herein; -
FIG. 10 is a block diagram illustrating an exemplary desktop or application pane demonstrating user action for resource-to-resource metadata association according to an embodiment of the subject matter described herein; -
FIG. 11 is a block diagram illustrating an exemplary desktop or application pane demonstrating modal input for resource-to-resource metadata association according to an embodiment of the subject matter described herein; -
FIG. 12 is a block diagram illustrating an exemplary desktop or application pane demonstrating a metadata mixer for resource-to-resource metadata association according to an embodiment of the subject matter described herein; -
FIG. 13 is a block diagram illustrating an exemplary desktop or application pane for resource-to-resource metadata association where one of the resources is data accessible through an executing application according to an embodiment of the subject matter described herein; -
FIG. 14 is a block diagram illustrating an exemplary desktop or application pane including a dialogue box for resource-to-resource metadata association according to an embodiment of the subject matter described herein; and -
FIG. 15 is a block diagram illustrating an exemplary user interface for automatically exchanging metadata between a resource and a resource cluster according to an embodiment of the subject matter described herein. - The subject matter described herein includes methods, systems, and computer program products for resource-to-resource metadata association. According to one aspect, a method or process for resource-to-resource metadata association is disclosed.
FIG. 1 is a flow chart illustrating an exemplary process for resource-to-resource metadata association according to an embodiment of the subject matter described herein. Referring toFIG. 1 , in block 100 a source resource is identified. The source resource may be a system file, application, or other resource recognized by a computer operating system. Inblock 102, an existing destination resource is identified. The destination resource may likewise be a system file, an executable application, or other resource recognized by a computer operating system. Inblock 104, the type of the source and/or the destination resource is identified. Inblock 106, based on the type of the source and/or destination resource, a transform for mapping one or more data values is associated with the source resource to the destination resource as metadata is selected. Inblock 108, at least one data value associated with the source resource is mapped to the destination resource as metadata. - According to another aspect, the subject matter described herein includes a system for resource-to-resource metadata association.
FIG. 2 is a block diagram illustrating one example of such a system. InFIG. 2 , the system includes means for identifying source and destination resources and a type of at least one of the source and the destination resource. For example,metadata hub 200 may identify source and destination resource types and invoke anappropriate protocol handler 202A-202E that provides access to the source and destination resources in a resource-to-resource metadata transaction. - In order to identify source and destination resource types,
metadata hub 200 may register itself with the operating system to receive notification when a metadata association action occurs. When such an action occurs, the operating system may communicate the source and destination resource identifiers tometadata hub 200.Metadata hub 200 may also include an application programming interface (API) that allows programmers to write applications that trigger hub functions. For example, an associate function that may be defined formetadata hub 200 may be accessed using the following call: -
- bool associate(source_res_id, dest_res_id, direction)
The above-listed function call allows a programmer to trigger resource-to-resource metadata association by specifying the source and destination resource identifiers as parameters to the associate function. The resource identifiers may be. file names, process identifiers, or other suitable resource identifiers. The programmer may also specify a direction parameterto indicate whether the association is source-to-destination, destination-to-source, or both., The call may triggerhub 200 to perform resource-to-resource metadata association, as illustrated inFIG. 1 . The associate function may return a different boolean value depending on whether the association is successful.
- bool associate(source_res_id, dest_res_id, direction)
- The system illustrated in
FIG. 1 may further include means for selecting, based on the type, a transform for mapping data values associated with the source resource to the destination resource as metadata. For example,metadata hub 200 may invokeappropriate content handlers 204A-204H based on the source and destination resource types to access data and/or metadata associated with the source and destination resources.Metadata hub 200 may further invoketransformer 205 to perform any conversions between data exchanged between the source and destination resource types as metadata. The conversions may include data format conversions and mappings from source resource metadata fields to destination resource metadata fields.Transformer 205 may access one or more transforms stored in atransform data store 206 to perform the appropriate conversions. In one exemplary implementation,transformer 205 may be implemented using extensible style sheet transformations (XSLT). In alternate implementations, scripts and/or executables may be used. - The following pseudo code is an example of a transform that may be defined for mapping data from a document resource to an image resource as metadata:
- 1. image.subject=document.subject
- 2. image.photographer=document.author
- 3. image.caption=document.content
- In
line 1 of the pseudo code above, content of the subject metadata tag of the document is mapped to the content of the subject metadata tag of the image. In line 2 of the pseudo code above, the content of the author metadata tag of the document is mapped to the photographer metadata tag of the image. Inline 3 of the pseudo code above, content from the document is mapped to the caption image metadata tag of the image. It should be noted that the content of the document may not be initially stored as tagged metadata. That is,transformer 205 may convert the content of the document to a tagged content field and automatically map that content to the captioned field of the image. -
Metadata hub 200 may identify data items as candidates for exclusion for metadata association. For example, certain data associated with the source resource may not be appropriate for association with a destination resource as metadata.Metadata hub 200 may identify the data that is not appropriate for association with a destination resource as metadata whentransformer 205 fails to map the data to the destination resource. In one example, if the source resource is an image file with metadata tags relating to the tint or brightness of the image, such data values may not be appropriate for inclusion in a document relating to the image.Metadata hub 200 may identify such data from the source resource as a candidate for exclusion and allow the user to manually determine whether to map or exclude the data value from association with the destination resource as metadata. Alternatively,metadata hub 200 may automatically exclude data from the source resource that does not map to the destination resource as metadata. - In one exemplary implementation,
metadata hub 200 may present a user with a menu of source resource data values and destination resource metadata fields. The source data items presented in the menu may include all source data items, source data items that are determined to be appropriate for association with the destination resource as metadata, or source data items that did not automatically map to one or more destination resource metadata fields. The destination metadata fields that are presented may likewise be a complete set of metadata fields of the destination resource, a set of fields to which source resource data maps, or a set of fields for which source data mapping failed. After presenting the user with the menu,metadata hub 200 may monitor user input for association actions for associating source resource data with destination metadata fields and perform the user-selected associations. An exemplary menu that may be presented bymetadata hub 200 will be described in detail below. -
Content handlers 204A-204H understand the format of the data and the metadata and any rules or restrictions that must be enforced on both the structure and values of the data or metadata.Transformer 205 may apply a transform or chain of transforms fromtransform data store 206 where the input is provided by the source content handler and the output is compatible with the destination content handler. It is not required for the input to the transform to be the same format that the content handler receives. That is, the source content handler may perform a format conversion to make it compatible with the transform. Likewise, the output of the last transform is not required to be the same format as the destination. The destination content handler may convert the output from the transform to a format compatible with a destination resource. - The system illustrated in
FIG. 2 may further include means for associating, based on the transform, at least one of the data values associated with the source resource with the destination resource as metadata. InFIG. 2 ,metadata hub 200 may invoke theappropriate content handlers 204A-204H andtransformers 205 to associate data from a source resource with a destination resource as metadata. - In the example illustrated in
FIG. 2 , the system resources for which it may be desirable to perform metadata to metadata association include files accessible via afile system 208, or content accessible via one ormore applications 210A-210E. For example, it may be desirable to associate data from a file infile system 208 with an address book entry accessible viamail client 210E or vice versa. Specific metadata association examples will be described in detail below. - In the example illustrated in
FIG. 2 , metadata is stored separately from resources invarious metadata databases 212A-212C. In an alternate example, the metadata or references to the metadata may be directly associated or embedded in the resource. Either embodiment is intended to be within the scope of the subject matter described herein. Thus, whenmetadata hub 200 associates data from a source resource with a destination resource as metadata,metadata hub 200 may update the corresponding entry in one ofmetadata databases 212A-212C. In an embodiment in which metadata is directly embedded in a resource,metadata hub 200 may write the data or reference to the appropriate metadata fields within the resource. - The components illustrated in
FIG. 2 may communicate in any suitable manner. In the illustrated example, acommunication subsystem 214 provides the mechanism by whichmetadata hub 200 can accesssystem resources metadata databases 212A-212C. In one example, communication subsystem 212 may be implemented using a network communications protocol stack, such as a TCP/IP protocol stack. -
FIGS. 3A and 3B are a flow chart illustrating an exemplary process for associating data from a source resource to a destination resource as metadata using the components illustrated inFIG. 2 . Referring toFIG. 3A , inblock 300, identifiers of resources to be associated are determined. The identifiers may be received in response to selection of the source and destination resources by a user via a user interface. Inblock 302, the directionality of the association is determined, and, for each direction, the actions specified by the remaining blocks inFIG. 3 are executed. Directionality for metadata association may be source-to-destination, destination-to-source, or both. - In
block 304, resource protocols are inspected and protocol handlers are invoked to access the resources. Inblock 306, it is determined whether any mapable data is present in the source resource. Here, the term “mapable data” refers to data in the source resource that is may be accessed by a source content handler mapping to a destination resource. If mapable data is present, control proceeds to block 308 where a source content handler is invoked. The source content handler may be invoked based on the source resource type to extract data from the source resource. The destination resource type may also be used to determine the source content handler to invoke and data to extract. Referring toFIG. 3B , inblock 310, it is determined whether a data conversion is required. If a data conversion is required, control proceeds to block 312 where data is converted from the source format to the destination resource format.Block 312 may be performed by content handlers and/ortransformer 205 as described above with respect toFIG. 2 . After the data conversion is performed or if no data conversion is required, control proceeds to block 314 where source data is associated with the destination resource as metadata by invoking the content handler for the destination type. For example, the mapped data can be written to a metadata file associated with the destination resource. In an alternate implementation, the mapped data may be written directly to the destination resource. - Returning to block 306 in
FIG. 3A , if it is determined that mapable data is not present in the source resource, the entire source resource may be associated with the destination-resource. Accordingly, control may proceed to block 316 where the entire source resource is associated with the destination resource. Additionally, the decision made inblock 306 may be predefined as “no” for certain source and/or destination resource types. For example, in the case of a contact associated with a contact management application, such as Microsoft Outlook®, it may be desirable to associate the entire source resource with the contact whether there is mapable data in the source resource or not. This example is shown below with reference toFIG. 13 . -
FIG. 4 is a block diagram illustrating anexemplary protocol handler 202C for a mail client. InFIG. 4 , mailclient protocol handler 202C uses a mail client proprietary application programming interface (API)library 400 to gain access to messages, folders, address books, or other data accessible via a mail client for which it may be desirable to associate with another resource as metadata or for which it may be desirable to associate data from another resource as metadata.Protocol handler 202C handles requests and responses to and from the mail client and forwards and receives data to and from the appropriate content handlers for the source and destination resources. -
FIG. 5 is a block diagram of anexemplary content handler 204. InFIG. 5 ,content handler 204 is a generic content handler capable of parsing and formatting keyword/value pairs.Content handler 204 includes a resource ID handler for parsing resource identifiers received fromhub 200 and a keyword/value formatter/parser 502 for interpreting keyword value pairs associated with a source or a destination resource. For example, data associated with a source or a destination resource may include metadata tags that correspond to the keywords and corresponding data values paired with each keyword. - As stated above, metadata may be associated with a resource using entries stored in a metadata database.
FIGS. 6 and 7 illustrate exemplary database structures that may be used to link metadata with resources. More particularly,FIG. 6 illustrates an example of a resource table, a link table, and a type table used to associate each resource with metadata. More particularly, inFIG. 6 , a singleresource table entry 600A of resource table 600 is shown for an image resource type.Entry 600A includes an identifier that links the resource to a link table 602. Link table 602 includes a link to an image schema table 604A that stores metadata for an image resource.FIG. 7 is a higher level view of the database illustrated inFIG. 6 . As illustrated inFIG. 7 , each resource type may include its own schema table 604A-604C that contains the associated metadata. -
FIG. 8 illustrates an example of another data structure that may be used to associate a resource with metadata. InFIG. 8 , the data structure includes a resource table 800 that stores a resource identifier and its type. A schema table 802 links the resource type to keyword-value pairs that represent metadata fields and data for each resource type. - In the examples illustrated in
FIGS. 6-8 , the relationships between the tables are shown as bidirectional. However, the subject matter described herein is not limited to bidirectional associations between resources and metadata. In an alternate implementation, the relationships may be unidirectional. Similarly, many-to-many, one-to-one, one-to-many, one-to-zero, and relationships with other cardinalities between resources and metadata are supported without departing from the scope of the subject matter described herein. -
FIG. 9 is a block diagram illustrating an exemplary desktop or application pane associated with resource-to-resource metadata association according to an embodiment of the subject matter described herein. The desktop or application pane may be monitored byhub 200 illustrated in FIG. 2. Referring toFIG. 9 , desktop orapplication pane 900 includes a plurality ofresource representations 902A-902E.Resource representations 902A-902E may be graphical and/or textural representations of resources, as defined by the underlying operating system. In the illustrated example, a user selects aresource representation 902A that corresponds to a PDF file. The user dragsresource representation 902A and hoversresource representation 902A overresource representation 902E andresource representation 902D. In response to this drag hover action,hub 200 may invoke the appropriate content handlers, protocol handlers, andtransformer 205 for associating data fromresource 902A withresources transformer 205 may be configured to associate data fromresources resource 902A in response to this drag hover action. In one exemplary implementation, all appropriate data extracted fromresource 902A may be automatically associated withresources hub 200 may associate data fromresource 902A withresources transform data store 206. If the transform is not defined for a particular source or destination resource, the user may be presented with a menu that allows the user to manually associate the unmapped data with the destination resource as metadata. An exemplary user interface for performing such mapping will be described in detail below. In yet another alternate implementation, data associated with the source resource may be displayed, metadata fields associated with thedestination resource -
FIG. 10 is a block diagram illustrating desktop orapplication pane 900 in which the user performs resource-to-resource metadata association using drag-and-drop actions. In the example illustrated inFIG. 10 , the user selectsresource representation 902E, dragsresource representation 902E overresource representation 902A and dropsresource representation 902E ontoresource representation 902A. The user repeats the same actions for droppingresource representation 902E ontoresource representation 902B. The result of the two actions illustrated inFIG. 10 are the association of data extracted from the resource represented byresource representation 902E with resources represented byresource representations FIG. 10 ,resource representation 902B is a file system folder. The data extracted fromresource representation 902B may be data associated with the folder itself, may be data associated with resources linked to the folder, or may be data associated with both. In each case, the data associated withresource representation 902E as metadata as a result of drag-and-drop action will be independent of an association betweenresource representation 902E and the file system. For example, data indicating a path to a location in the file system or data indicating a category within the file system is not associated withresource representation 902E as a result of the drag-and-drop action. Again, as with the drag-and-hover actions described with reference toFIG. 9 ,transformer 205 can be configured so that the same drag-and-drop action illustrated inFIG. 10 results in the association of data extracted from the resource represented byresource representations resource representation 902E as metadata. -
FIG. 11 is a block diagram illustrating yet another example of desktop orapplication pane 900 where the user performs resource-to-resource metadata association using modal input. By modal input, it is meant that once an indication is received to enter the metadata association mode, user input is interpreted in the context of the mode rather than normal desktop of application input processing. For example, in Windows®-based operating systems, a user can assign default actions to a context menu associated with a resource using a resource management interface, such as Windows Explorer®. In the illustrated example, it is assumed that a create relation action and an associate metadata action have been defined forresource 902E such that when a user clicks onresource 902E,menu 1100 appears with these options. The associate metadata action when selected causes the desktop or application pane to enter metadata association mode, allowing a user to associate metadata between source and destination resources using drag-and-drop or drag-and-hover, which would have other results in the normal desktop or application mode. -
FIG. 12 is a block diagram illustrating another example of desktop orapplication pane 900 where resource-to-resource metadata association is performed using a metadata mixer. Referring toFIG. 12 , ametadata mixer representation 1200 is displayed. Metadata mixer representation may represent access to an application that creates metadata associations between resources that are associated with it, such ashub 200. For example, if resources A and B are associated withmetadata mixer representation 1200, metadata from resource A may be associated with resource B and vice versa. In the illustrated example,resource representations mixer representation 1200.Representation 902B is identified as a metadata source.Representations representation 902B may be associated with the resources represented byrepresentations - In order to distinguish between source and target resources,
mixer representation 1200 may have two sides. For example, resources associated with the left side ofmixer representation 1200 may be designated as targets and resource representations associated with the right side ofmixer representation 1200 may be designated as sources. Alternatively, rather than using a two-sided mixer, a mouse gesture may be used to indicate a source resource and a different mouse gesture may be used to indicate a destination resource. In yet another alternate implementation, mouse gestures may be used in combination with keyboard input to distinguish between source and target resources. For example, the user may depress the S key after selecting a resource to identify that resource as the source and the D key after selecting a resource to identify the resource as a destination. -
FIG. 13 illustrates another example of desktop orapplication pane 900 where data from an open application is associated with a resource as metadata and where a resource is associated with data from an open application as metadata. More particularly, inFIG. 13 , anaddress book application 1300 displays contact information associated with an email address book. In the illustrated example, the user drags and drops contact B information on toresource representation 902A, which corresponds to a PDF file. In one implementation, the user may be presented with a menu or dialogue box that allows the user to select source data and corresponding target fields.FIG. 14 illustrates an example of such an interface. Referring toFIG. 14 , desktop orapplication pane 900 includes adialogue box 1400 that displays source data fields in the left hand column and target resource metadata fields in the right hand column. The user may select data in the left hand column and associate that data with the metadata fields in the right hand column by any suitable action, such as drag-and-drop or drag-and-hover. Once the user has defined all of the associations that the user desires to make, the user may select the save button to save the changes. - Although in the example illustrated in
FIG. 14 , only existing metadata fields associated with the destination resources are shown, the subject matter described herein is not limited to such an implementation. In an alternate implementation, the user may define and associate custom metadata fields and values for the source resource and custom metadata fields for the destination resource. The source content handler may allow custom metadata fields and data to be defined for and associated with the source resource. The destination content handler may allow custom metadata fields to be defined for and associated with the destination resource. A transform may be defined for mapping the data in the custom metadata fields from the source resource to the custom metadata fields of the destination resource. For example, once custom source and/or destination fields are defined, the user may perform the initial mapping from source data to destination fields manually using an interface such as that illustrated inFIG. 14 .Metadata hub 200 may record the mappings and store the mappings intransform data store 206. The next time that resources of the type for which the transform was defined are associated with each other,transformer 205 may access transformdata store 206, extract the mapping, and perform the association. - Returning to
FIG. 13 , in another example, a user may associate aresource representation 902D with data displayed inaddress book application 1300. For example, the user may associate a picture with a contact. Thus, the example illustrated by the lower arrow inFIG. 13 illustrates the association of an entire resource with a destination as metadata. That is, the resource represented byresource representation 902D becomes metadata of the destination, which in this case is the contact. -
FIG. 15 is a block diagram illustrating another example of resource-to-resource metadata association according to an embodiment of the subject matter described herein. Referring toFIG. 15 ,resource clusters multiple resource representations 1510 that have at least some metadata in common. For example,resource cluster 1500 includes the metadata “Boston”, which can be used in resource-to-resource metadata association. A user may moveresource representation 902 to a location corresponding to one of the clusters and dropresource representation 902 onto the cluster or hoverresource representation 902 over the cluster. Once the user performs the association action, data that is associated with the cluster as metadata may be associated with the resource represented byresource representation 902 or vice versa. It should be noted that resource representations can be members of more than one cluster. For example, inFIG. 15 , resource representation ‘C’ is a member of two different clusters. - The following scenarios illustrate resource-to-resource metadata association according to an embodiment of the subject matter described herein.
- Scenario 1:
-
-
- 1. Larry has a picture of Bob on his desktop. However, there is no metadata related to Bob associated with the picture.
- 2. Larry opens his address book and locates Bob's address book record.
- 3. He drags Bob's entry over the image and hovers over it until the image indicates that it has focus, and a rollover display pops up showing the metadata associated with the picture including the relevant info in the address book entry. When Larry releases the mouse, a dialogue box is displayed showing data from Bob's address book entry on one side. On the other side are image schema element names “creator,” “owner,” “subject.” Larry drags Bob's information onto the “subject.” (He later assigns his own address book entry to both “creator” and “owner” using the same UI operations.)
- 4. The picture was taken at Churchill Downs racetrack. Larry pulls up the home page for the track in his web browser. He selects the URL in the location bar via a copy operation and executes a paste from the context menu of the image. The content handler for the image adds the URL to the metadata as a relation.
- 5. Larry edits the metadata to indicate that the metadata is a location reference. Note: A protocol handler could have been used to retrieve the page and have it parsed by an HTML content handler into a format known to the image content handler, which would identify data from the page to associate with the image
Scenario 2: - 1. Larry has a picture of Bob on his desktop. He has captured metadata about Bob for the picture.
- 2. Larry uses his system search tool to find all resources either with “Bob” in the content or “Bob” in the metadata.
- 3. He drags and drops the picture of Bob onto the group of resources returned. Larry uses one of several keyboard sequences while hovering over the group to cause metadata associations to be made in one or both directions between the picture and the group of resources. (Note: conflicts can be resolved via a set of system and user configurable rules; and through dialogs allowing the user to take care of unresolved problems).
- 4. Bob's picture has also been embedded in a number of related resources such as his address book entry. Metadata has been exchanged between Bob's picture and the related resources.
- It will be understood that various details of the invention may be changed without departing from the scope of the invention. Furthermore, the foregoing description is for the purpose of illustration only, and not for the purpose of limitation, as the invention is defined by the claims as set forth hereinafter.
Claims (45)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/239,276 US20070073770A1 (en) | 2005-09-29 | 2005-09-29 | Methods, systems, and computer program products for resource-to-resource metadata association |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/239,276 US20070073770A1 (en) | 2005-09-29 | 2005-09-29 | Methods, systems, and computer program products for resource-to-resource metadata association |
Publications (1)
Publication Number | Publication Date |
---|---|
US20070073770A1 true US20070073770A1 (en) | 2007-03-29 |
Family
ID=37895421
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/239,276 Abandoned US20070073770A1 (en) | 2005-09-29 | 2005-09-29 | Methods, systems, and computer program products for resource-to-resource metadata association |
Country Status (1)
Country | Link |
---|---|
US (1) | US20070073770A1 (en) |
Cited By (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070078885A1 (en) * | 2005-10-03 | 2007-04-05 | Klein Eric N Jr | System and method for generating homogeneous metadata from pre-existing metadata |
US20070273774A1 (en) * | 2006-05-26 | 2007-11-29 | Lifetouch, Inc. | Identifying and tracking digital images with customized metadata |
US20090049123A1 (en) * | 2005-10-26 | 2009-02-19 | Yahoo! Inc. | System and method for seamlessly integrating separate information systems within an application |
US20090240698A1 (en) * | 2008-03-20 | 2009-09-24 | Microsoft Corporation | Computing environment platform |
US20090248737A1 (en) * | 2008-03-27 | 2009-10-01 | Microsoft Corporation | Computing environment representation |
US20100332559A1 (en) * | 2005-09-29 | 2010-12-30 | Fry Jared S | Methods, Systems, And Computer Program Products For Automatically Associating Data With A Resource As Metadata Based On A Characteristic Of The Resource |
US20110040850A1 (en) * | 2007-05-04 | 2011-02-17 | Microsoft Corporation | Mesh-managing data across a distributed set of devices |
US20120166827A1 (en) * | 2010-12-23 | 2012-06-28 | Qualcomm Incorporated | Method and Apparatus for Reducing Dynamic Power within System-on-a-Chip Routing Resources |
US8484174B2 (en) | 2008-03-20 | 2013-07-09 | Microsoft Corporation | Computing environment representation |
US8572033B2 (en) | 2008-03-20 | 2013-10-29 | Microsoft Corporation | Computing environment configuration |
US9753712B2 (en) | 2008-03-20 | 2017-09-05 | Microsoft Technology Licensing, Llc | Application management within deployable object hierarchy |
US20170262461A1 (en) * | 2016-03-08 | 2017-09-14 | International Business Machines Corporation | Key-value store for managing user files based on pairs of key-value pairs |
Citations (68)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5301268A (en) * | 1990-10-10 | 1994-04-05 | Fuji Xerox Co., Ltd. | Apparatus for transferring information between different window systems |
US5398312A (en) * | 1992-04-07 | 1995-03-14 | International Business Machines Corporation | Method of creating, defining, or editing a graphical user interface panel file |
US5428734A (en) * | 1992-12-22 | 1995-06-27 | Ibm Corporation | Method and apparatus for enhancing drag and drop manipulation of objects in a graphical user interface |
US5878410A (en) * | 1996-09-13 | 1999-03-02 | Microsoft Corporation | File system sort order indexes |
US5899995A (en) * | 1997-06-30 | 1999-05-04 | Intel Corporation | Method and apparatus for automatically organizing information |
US5920861A (en) * | 1997-02-25 | 1999-07-06 | Intertrust Technologies Corp. | Techniques for defining using and manipulating rights management data structures |
US5980096A (en) * | 1995-01-17 | 1999-11-09 | Intertech Ventures, Ltd. | Computer-based system, methods and graphical interface for information storage, modeling and stimulation of complex systems |
US6002402A (en) * | 1997-04-09 | 1999-12-14 | Symantec Corporation | System and method for producing a drag-and-drop object from a popup menu item |
US6009442A (en) * | 1997-10-08 | 1999-12-28 | Caere Corporation | Computer-based document management system |
US6151624A (en) * | 1998-02-03 | 2000-11-21 | Realnames Corporation | Navigating network resources based on metadata |
US6243724B1 (en) * | 1992-04-30 | 2001-06-05 | Apple Computer, Inc. | Method and apparatus for organizing information in a computer system |
US6259448B1 (en) * | 1998-06-03 | 2001-07-10 | International Business Machines Corporation | Resource model configuration and deployment in a distributed computer network |
US6345288B1 (en) * | 1989-08-31 | 2002-02-05 | Onename Corporation | Computer-based communication system and method using metadata defining a control-structure |
US20020016800A1 (en) * | 2000-03-27 | 2002-02-07 | Victor Spivak | Method and apparatus for generating metadata for a document |
US6353823B1 (en) * | 1999-03-08 | 2002-03-05 | Intel Corporation | Method and system for using associative metadata |
US20020065844A1 (en) * | 2000-11-30 | 2002-05-30 | Rich Robinson | Metadata internet platform for enabling customization of tags in digital images |
US20020073104A1 (en) * | 2000-07-24 | 2002-06-13 | Centor Software Corporation | Open format for file storage system indexing, searching and data retrieval |
US20020083099A1 (en) * | 2000-12-27 | 2002-06-27 | Ge Information Services, Inc. | Document/message management |
US20020087601A1 (en) * | 2000-12-29 | 2002-07-04 | Anderson Eric C. | Client-server system for merging of metadata with images |
US6418448B1 (en) * | 1999-12-06 | 2002-07-09 | Shyam Sundar Sarkar | Method and apparatus for processing markup language specifications for data and metadata used inside multiple related internet documents to navigate, query and manipulate information from a plurality of object relational databases over the web |
US6510434B1 (en) * | 1999-12-29 | 2003-01-21 | Bellsouth Intellectual Property Corporation | System and method for retrieving information from a database using an index of XML tags and metafiles |
US20030034892A1 (en) * | 2001-08-20 | 2003-02-20 | John Light | Atomic virtual document generation and tagging |
US20030078987A1 (en) * | 2001-10-24 | 2003-04-24 | Oleg Serebrennikov | Navigating network communications resources based on telephone-number metadata |
US6582474B2 (en) * | 1998-08-31 | 2003-06-24 | Xerox Corporation | Tagging related files in a document management system |
US20030126212A1 (en) * | 2001-12-28 | 2003-07-03 | Morris Robert Paul | Specifying, assigning, and maintaining user defined metadata in a network-based photosharing system |
US20030131013A1 (en) * | 2002-01-07 | 2003-07-10 | Cameron Pope | Automated system and methods for determining relationships between information resources |
US20030208499A1 (en) * | 2002-05-03 | 2003-11-06 | David Bigwood | Methods and apparatus for visualizing relationships among triples of resource description framework (RDF) data sets |
US20040006575A1 (en) * | 2002-04-29 | 2004-01-08 | Visharam Mohammed Zubair | Method and apparatus for supporting advanced coding formats in media files |
US20040019658A1 (en) * | 2001-03-26 | 2004-01-29 | Microsoft Corporation | Metadata retrieval protocols and namespace identifiers |
US20040027382A1 (en) * | 2002-04-17 | 2004-02-12 | Marion Kuehn | Method for a software application for triggering an action relating to a data object, and data processing device having the software application |
US20040093323A1 (en) * | 2002-11-07 | 2004-05-13 | Mark Bluhm | Electronic document repository management and access system |
US20040096110A1 (en) * | 2001-04-20 | 2004-05-20 | Front Porch Digital Inc. | Methods and apparatus for archiving, indexing and accessing audio and video data |
US6741994B1 (en) * | 1998-07-27 | 2004-05-25 | Hewlett-Packard Development Company, L.P. | Method and automatic organization of data |
US20040111728A1 (en) * | 2002-12-05 | 2004-06-10 | Schwalm Brian E. | Method and system for managing metadata |
US20040133589A1 (en) * | 2002-12-19 | 2004-07-08 | Rick Kiessig | System and method for managing content |
US20040153467A1 (en) * | 2000-01-21 | 2004-08-05 | Conover Joan Evelyn | System and method for cataloguing digital information for searching and retrieval |
US20040172241A1 (en) * | 2002-12-11 | 2004-09-02 | France Telecom | Method and system of correcting spectral deformations in the voice, introduced by a communication network |
US20040177319A1 (en) * | 2002-07-16 | 2004-09-09 | Horn Bruce L. | Computer system for automatic organization, indexing and viewing of information from multiple sources |
US20040210946A1 (en) * | 2002-07-23 | 2004-10-21 | Samsung Electronics Co., Ltd. | Index structure of metadata, method for providing indices of metadata, and metadata searching method and apparatus using the indices of metadata |
US20040210552A1 (en) * | 2003-04-16 | 2004-10-21 | Richard Friedman | Systems and methods for processing resource description framework data |
US6810404B1 (en) * | 1997-10-08 | 2004-10-26 | Scansoft, Inc. | Computer-based document management system |
US6820094B1 (en) * | 1997-10-08 | 2004-11-16 | Scansoft, Inc. | Computer-based document management system |
US20040250215A1 (en) * | 2003-06-05 | 2004-12-09 | International Business Machines Corporation | System and method for content and information transfer between program entities |
US20040260702A1 (en) * | 2003-06-20 | 2004-12-23 | International Business Machines Corporation | Universal annotation configuration and deployment |
US20050015391A1 (en) * | 2001-09-10 | 2005-01-20 | Siemens Aktiengesellschaft | Visualization of a comparison result of at least two data structures organized in directory trees |
US20050038813A1 (en) * | 2003-08-12 | 2005-02-17 | Vidur Apparao | System for incorporating information about a source and usage of a media asset into the asset itself |
US20050044089A1 (en) * | 2003-08-21 | 2005-02-24 | Microsoft Corporation | Systems and methods for interfacing application programs with an item-based storage platform |
US20050050537A1 (en) * | 2003-08-21 | 2005-03-03 | Thompson J. Patrick | Systems and method for representing relationships between units of information manageable by a hardware/software interface system |
US20050060653A1 (en) * | 2003-09-12 | 2005-03-17 | Dainippon Screen Mfg. Co., Ltd. | Object operation apparatus, object operation method and object operation program |
US20050063083A1 (en) * | 2003-08-21 | 2005-03-24 | Dart Scott E. | Systems and methods for the implementation of a digital images schema for organizing units of information manageable by a hardware/software interface system |
US20050071865A1 (en) * | 2003-09-30 | 2005-03-31 | Martins Fernando C. M. | Annotating meta-data with user responses to digital content |
US6877138B2 (en) * | 2002-03-14 | 2005-04-05 | International Business Machines Corporation | Transferring properties between computer objects |
US20050080802A1 (en) * | 2000-04-03 | 2005-04-14 | Jean-Yves Cras | Analytical reporting on top of multidimensional data model |
US20050091184A1 (en) * | 2003-10-24 | 2005-04-28 | Praveen Seshadri | Personalized folders |
US20050091285A1 (en) * | 2003-10-23 | 2005-04-28 | Krishnan Prasanna V. | Promotion and demotion techniques to facilitate file property management between object systems |
US20050097120A1 (en) * | 2003-10-31 | 2005-05-05 | Fuji Xerox Co., Ltd. | Systems and methods for organizing data |
US20050114356A1 (en) * | 2003-11-20 | 2005-05-26 | Bhatti Shahzad H. | Organizing data objects in a storage device |
US20050114381A1 (en) * | 2003-11-26 | 2005-05-26 | Veritas Operating Corporation | System and method for generating extensible file system metadata |
US20050120021A1 (en) * | 2003-12-02 | 2005-06-02 | Microsoft Corporation | Metadata driven intelligent data navigation |
US20050131871A1 (en) * | 2003-12-15 | 2005-06-16 | Howard Mark A. | Multi-tiered structure for file sharing based on social roles |
US20050166159A1 (en) * | 2003-02-13 | 2005-07-28 | Lumapix | Method and system for distributing multiple dragged objects |
US20050177796A1 (en) * | 2004-01-08 | 2005-08-11 | Fuji Photo Film Co., Ltd. | File management program |
US20060031486A1 (en) * | 2000-02-29 | 2006-02-09 | International Business Machines Corporation | Method for automatically associating contextual input data with available multimedia resources |
US7162488B2 (en) * | 2005-04-22 | 2007-01-09 | Microsoft Corporation | Systems, methods, and user interfaces for storing, searching, navigating, and retrieving electronic information |
US20070067290A1 (en) * | 2005-09-22 | 2007-03-22 | Nokia Corporation | Metadata triggered notification for content searching |
US20070073688A1 (en) * | 2005-09-29 | 2007-03-29 | Fry Jared S | Methods, systems, and computer program products for automatically associating data with a resource as metadata based on a characteristic of the resource |
US20080222170A1 (en) * | 2002-02-20 | 2008-09-11 | Microsoft Corporation | Computer system architecture for automatic context associations |
US20090138789A1 (en) * | 2003-10-24 | 2009-05-28 | Hyperion Solutions Corp., A Delaware Corporation | User interface for establishing mappings from internal metadata to external metadata |
-
2005
- 2005-09-29 US US11/239,276 patent/US20070073770A1/en not_active Abandoned
Patent Citations (69)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6345288B1 (en) * | 1989-08-31 | 2002-02-05 | Onename Corporation | Computer-based communication system and method using metadata defining a control-structure |
US5301268A (en) * | 1990-10-10 | 1994-04-05 | Fuji Xerox Co., Ltd. | Apparatus for transferring information between different window systems |
US5398312A (en) * | 1992-04-07 | 1995-03-14 | International Business Machines Corporation | Method of creating, defining, or editing a graphical user interface panel file |
US6243724B1 (en) * | 1992-04-30 | 2001-06-05 | Apple Computer, Inc. | Method and apparatus for organizing information in a computer system |
US6613101B2 (en) * | 1992-04-30 | 2003-09-02 | Apple Computer, Inc. | Method and apparatus for organizing information in a computer system |
US5428734A (en) * | 1992-12-22 | 1995-06-27 | Ibm Corporation | Method and apparatus for enhancing drag and drop manipulation of objects in a graphical user interface |
US5980096A (en) * | 1995-01-17 | 1999-11-09 | Intertech Ventures, Ltd. | Computer-based system, methods and graphical interface for information storage, modeling and stimulation of complex systems |
US5878410A (en) * | 1996-09-13 | 1999-03-02 | Microsoft Corporation | File system sort order indexes |
US5920861A (en) * | 1997-02-25 | 1999-07-06 | Intertrust Technologies Corp. | Techniques for defining using and manipulating rights management data structures |
US6002402A (en) * | 1997-04-09 | 1999-12-14 | Symantec Corporation | System and method for producing a drag-and-drop object from a popup menu item |
US5899995A (en) * | 1997-06-30 | 1999-05-04 | Intel Corporation | Method and apparatus for automatically organizing information |
US6820094B1 (en) * | 1997-10-08 | 2004-11-16 | Scansoft, Inc. | Computer-based document management system |
US6810404B1 (en) * | 1997-10-08 | 2004-10-26 | Scansoft, Inc. | Computer-based document management system |
US6009442A (en) * | 1997-10-08 | 1999-12-28 | Caere Corporation | Computer-based document management system |
US6151624A (en) * | 1998-02-03 | 2000-11-21 | Realnames Corporation | Navigating network resources based on metadata |
US6259448B1 (en) * | 1998-06-03 | 2001-07-10 | International Business Machines Corporation | Resource model configuration and deployment in a distributed computer network |
US6741994B1 (en) * | 1998-07-27 | 2004-05-25 | Hewlett-Packard Development Company, L.P. | Method and automatic organization of data |
US6582474B2 (en) * | 1998-08-31 | 2003-06-24 | Xerox Corporation | Tagging related files in a document management system |
US6353823B1 (en) * | 1999-03-08 | 2002-03-05 | Intel Corporation | Method and system for using associative metadata |
US6418448B1 (en) * | 1999-12-06 | 2002-07-09 | Shyam Sundar Sarkar | Method and apparatus for processing markup language specifications for data and metadata used inside multiple related internet documents to navigate, query and manipulate information from a plurality of object relational databases over the web |
US6510434B1 (en) * | 1999-12-29 | 2003-01-21 | Bellsouth Intellectual Property Corporation | System and method for retrieving information from a database using an index of XML tags and metafiles |
US20040153467A1 (en) * | 2000-01-21 | 2004-08-05 | Conover Joan Evelyn | System and method for cataloguing digital information for searching and retrieval |
US20060031486A1 (en) * | 2000-02-29 | 2006-02-09 | International Business Machines Corporation | Method for automatically associating contextual input data with available multimedia resources |
US20020016800A1 (en) * | 2000-03-27 | 2002-02-07 | Victor Spivak | Method and apparatus for generating metadata for a document |
US20050080802A1 (en) * | 2000-04-03 | 2005-04-14 | Jean-Yves Cras | Analytical reporting on top of multidimensional data model |
US20020073104A1 (en) * | 2000-07-24 | 2002-06-13 | Centor Software Corporation | Open format for file storage system indexing, searching and data retrieval |
US20020065844A1 (en) * | 2000-11-30 | 2002-05-30 | Rich Robinson | Metadata internet platform for enabling customization of tags in digital images |
US20020083099A1 (en) * | 2000-12-27 | 2002-06-27 | Ge Information Services, Inc. | Document/message management |
US20020087601A1 (en) * | 2000-12-29 | 2002-07-04 | Anderson Eric C. | Client-server system for merging of metadata with images |
US20040019658A1 (en) * | 2001-03-26 | 2004-01-29 | Microsoft Corporation | Metadata retrieval protocols and namespace identifiers |
US20040096110A1 (en) * | 2001-04-20 | 2004-05-20 | Front Porch Digital Inc. | Methods and apparatus for archiving, indexing and accessing audio and video data |
US20030034892A1 (en) * | 2001-08-20 | 2003-02-20 | John Light | Atomic virtual document generation and tagging |
US20050015391A1 (en) * | 2001-09-10 | 2005-01-20 | Siemens Aktiengesellschaft | Visualization of a comparison result of at least two data structures organized in directory trees |
US20030078987A1 (en) * | 2001-10-24 | 2003-04-24 | Oleg Serebrennikov | Navigating network communications resources based on telephone-number metadata |
US20030126212A1 (en) * | 2001-12-28 | 2003-07-03 | Morris Robert Paul | Specifying, assigning, and maintaining user defined metadata in a network-based photosharing system |
US20030131013A1 (en) * | 2002-01-07 | 2003-07-10 | Cameron Pope | Automated system and methods for determining relationships between information resources |
US20080222170A1 (en) * | 2002-02-20 | 2008-09-11 | Microsoft Corporation | Computer system architecture for automatic context associations |
US6877138B2 (en) * | 2002-03-14 | 2005-04-05 | International Business Machines Corporation | Transferring properties between computer objects |
US20040027382A1 (en) * | 2002-04-17 | 2004-02-12 | Marion Kuehn | Method for a software application for triggering an action relating to a data object, and data processing device having the software application |
US20040006575A1 (en) * | 2002-04-29 | 2004-01-08 | Visharam Mohammed Zubair | Method and apparatus for supporting advanced coding formats in media files |
US20030208499A1 (en) * | 2002-05-03 | 2003-11-06 | David Bigwood | Methods and apparatus for visualizing relationships among triples of resource description framework (RDF) data sets |
US20040177319A1 (en) * | 2002-07-16 | 2004-09-09 | Horn Bruce L. | Computer system for automatic organization, indexing and viewing of information from multiple sources |
US20040210946A1 (en) * | 2002-07-23 | 2004-10-21 | Samsung Electronics Co., Ltd. | Index structure of metadata, method for providing indices of metadata, and metadata searching method and apparatus using the indices of metadata |
US20040093323A1 (en) * | 2002-11-07 | 2004-05-13 | Mark Bluhm | Electronic document repository management and access system |
US20040111728A1 (en) * | 2002-12-05 | 2004-06-10 | Schwalm Brian E. | Method and system for managing metadata |
US20040172241A1 (en) * | 2002-12-11 | 2004-09-02 | France Telecom | Method and system of correcting spectral deformations in the voice, introduced by a communication network |
US20040133589A1 (en) * | 2002-12-19 | 2004-07-08 | Rick Kiessig | System and method for managing content |
US20050166159A1 (en) * | 2003-02-13 | 2005-07-28 | Lumapix | Method and system for distributing multiple dragged objects |
US20040210552A1 (en) * | 2003-04-16 | 2004-10-21 | Richard Friedman | Systems and methods for processing resource description framework data |
US20040250215A1 (en) * | 2003-06-05 | 2004-12-09 | International Business Machines Corporation | System and method for content and information transfer between program entities |
US20040260702A1 (en) * | 2003-06-20 | 2004-12-23 | International Business Machines Corporation | Universal annotation configuration and deployment |
US20050038813A1 (en) * | 2003-08-12 | 2005-02-17 | Vidur Apparao | System for incorporating information about a source and usage of a media asset into the asset itself |
US20050044089A1 (en) * | 2003-08-21 | 2005-02-24 | Microsoft Corporation | Systems and methods for interfacing application programs with an item-based storage platform |
US20050050537A1 (en) * | 2003-08-21 | 2005-03-03 | Thompson J. Patrick | Systems and method for representing relationships between units of information manageable by a hardware/software interface system |
US20050063083A1 (en) * | 2003-08-21 | 2005-03-24 | Dart Scott E. | Systems and methods for the implementation of a digital images schema for organizing units of information manageable by a hardware/software interface system |
US20050060653A1 (en) * | 2003-09-12 | 2005-03-17 | Dainippon Screen Mfg. Co., Ltd. | Object operation apparatus, object operation method and object operation program |
US20050071865A1 (en) * | 2003-09-30 | 2005-03-31 | Martins Fernando C. M. | Annotating meta-data with user responses to digital content |
US20050091285A1 (en) * | 2003-10-23 | 2005-04-28 | Krishnan Prasanna V. | Promotion and demotion techniques to facilitate file property management between object systems |
US20050091184A1 (en) * | 2003-10-24 | 2005-04-28 | Praveen Seshadri | Personalized folders |
US20090138789A1 (en) * | 2003-10-24 | 2009-05-28 | Hyperion Solutions Corp., A Delaware Corporation | User interface for establishing mappings from internal metadata to external metadata |
US20050097120A1 (en) * | 2003-10-31 | 2005-05-05 | Fuji Xerox Co., Ltd. | Systems and methods for organizing data |
US20050114356A1 (en) * | 2003-11-20 | 2005-05-26 | Bhatti Shahzad H. | Organizing data objects in a storage device |
US20050114381A1 (en) * | 2003-11-26 | 2005-05-26 | Veritas Operating Corporation | System and method for generating extensible file system metadata |
US20050120021A1 (en) * | 2003-12-02 | 2005-06-02 | Microsoft Corporation | Metadata driven intelligent data navigation |
US20050131871A1 (en) * | 2003-12-15 | 2005-06-16 | Howard Mark A. | Multi-tiered structure for file sharing based on social roles |
US20050177796A1 (en) * | 2004-01-08 | 2005-08-11 | Fuji Photo Film Co., Ltd. | File management program |
US7162488B2 (en) * | 2005-04-22 | 2007-01-09 | Microsoft Corporation | Systems, methods, and user interfaces for storing, searching, navigating, and retrieving electronic information |
US20070067290A1 (en) * | 2005-09-22 | 2007-03-22 | Nokia Corporation | Metadata triggered notification for content searching |
US20070073688A1 (en) * | 2005-09-29 | 2007-03-29 | Fry Jared S | Methods, systems, and computer program products for automatically associating data with a resource as metadata based on a characteristic of the resource |
Cited By (37)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20100332559A1 (en) * | 2005-09-29 | 2010-12-30 | Fry Jared S | Methods, Systems, And Computer Program Products For Automatically Associating Data With A Resource As Metadata Based On A Characteristic Of The Resource |
US9280544B2 (en) | 2005-09-29 | 2016-03-08 | Scenera Technologies, Llc | Methods, systems, and computer program products for automatically associating data with a resource as metadata based on a characteristic of the resource |
US8862620B2 (en) * | 2005-10-03 | 2014-10-14 | Intel Corporation | System and method for generating homogeneous metadata from pre-existing metadata |
US9529802B2 (en) | 2005-10-03 | 2016-12-27 | Intel Corporation | System and method for generating homogeneous metadata from pre-existing metadata |
US9176961B2 (en) | 2005-10-03 | 2015-11-03 | Intel Corporation | System and method for generating homogeneous metadata from pre-existing metadata |
US20070078885A1 (en) * | 2005-10-03 | 2007-04-05 | Klein Eric N Jr | System and method for generating homogeneous metadata from pre-existing metadata |
US8346789B2 (en) * | 2005-10-03 | 2013-01-01 | Intel Corporation | System and method for generating homogeneous metadata from pre-existing metadata |
US20130117309A1 (en) * | 2005-10-03 | 2013-05-09 | Eric N. Klein, Jr. | System and method for generating homogeneous metadata from pre-existing metadata |
US20090100367A1 (en) * | 2005-10-26 | 2009-04-16 | Yahoo! Inc. | System and method for seamlessly integrating separate information systems within an application |
US20090100010A1 (en) * | 2005-10-26 | 2009-04-16 | Zimbra, Inc. | System and method for seamlessly integrating separate information systems within an application |
US10481764B2 (en) | 2005-10-26 | 2019-11-19 | Vmware, Inc. | System and method for seamlessly integrating separate information systems within an application |
US20090049123A1 (en) * | 2005-10-26 | 2009-02-19 | Yahoo! Inc. | System and method for seamlessly integrating separate information systems within an application |
US8631065B2 (en) | 2005-10-26 | 2014-01-14 | Vmware, Inc. | System and method for seamlessly integrating separate information systems within an application |
US8380747B2 (en) * | 2005-10-26 | 2013-02-19 | Vmware, Inc. | System and method for seamlessly integrating separate information systems within an application |
US8619157B2 (en) * | 2006-05-26 | 2013-12-31 | Lifetouch Inc. | Identifying and tracking digital images with customized metadata |
US7714908B2 (en) * | 2006-05-26 | 2010-05-11 | Lifetouch Inc. | Identifying and tracking digital images with customized metadata |
US9924128B2 (en) * | 2006-05-26 | 2018-03-20 | Lifetouch Inc. | Identifying and tracking digital images with customized metadata |
US20070273774A1 (en) * | 2006-05-26 | 2007-11-29 | Lifetouch, Inc. | Identifying and tracking digital images with customized metadata |
US11095846B2 (en) | 2006-05-26 | 2021-08-17 | Shutterfly, Llc | Identifying and tracking digital images with customized metadata |
US10341603B2 (en) | 2006-05-26 | 2019-07-02 | Lifetouch Inc. | Identifying and tracking digital images with customized metadata |
US20100177212A1 (en) * | 2006-05-26 | 2010-07-15 | Lifetouch Inc. | Identifying and Tracking Digital Images With Customized Metadata |
US20160014368A1 (en) * | 2006-05-26 | 2016-01-14 | Lifetouch Inc. | Identifying and Tracking Digital Images With Customized Metadata |
US20110040850A1 (en) * | 2007-05-04 | 2011-02-17 | Microsoft Corporation | Mesh-managing data across a distributed set of devices |
US9135279B2 (en) | 2007-05-04 | 2015-09-15 | Microsoft Technology Licensing, Llc | Mesh-managing data across a distributed set of devices |
US8364759B2 (en) | 2007-05-04 | 2013-01-29 | Microsoft Corporation | Mesh-managing data across a distributed set of devices |
US10514901B2 (en) | 2008-03-20 | 2019-12-24 | Microsoft Technology Licensing, Llc | Application management within deployable object hierarchy |
US9298747B2 (en) | 2008-03-20 | 2016-03-29 | Microsoft Technology Licensing, Llc | Deployable, consistent, and extensible computing environment platform |
US9332063B2 (en) | 2008-03-20 | 2016-05-03 | Microsoft Technology Licensing, Llc | Versatile application configuration for deployable computing environments |
US20090240698A1 (en) * | 2008-03-20 | 2009-09-24 | Microsoft Corporation | Computing environment platform |
US9753712B2 (en) | 2008-03-20 | 2017-09-05 | Microsoft Technology Licensing, Llc | Application management within deployable object hierarchy |
US8572033B2 (en) | 2008-03-20 | 2013-10-29 | Microsoft Corporation | Computing environment configuration |
US8484174B2 (en) | 2008-03-20 | 2013-07-09 | Microsoft Corporation | Computing environment representation |
US20090248737A1 (en) * | 2008-03-27 | 2009-10-01 | Microsoft Corporation | Computing environment representation |
US8966291B2 (en) * | 2010-12-23 | 2015-02-24 | Qualcomm Incorporated | Method and apparatus for reducing dynamic power within system-on-a-chip routing resources |
US20120166827A1 (en) * | 2010-12-23 | 2012-06-28 | Qualcomm Incorporated | Method and Apparatus for Reducing Dynamic Power within System-on-a-Chip Routing Resources |
US10235374B2 (en) * | 2016-03-08 | 2019-03-19 | International Business Machines Corporation | Key-value store for managing user files based on pairs of key-value pairs |
US20170262461A1 (en) * | 2016-03-08 | 2017-09-14 | International Business Machines Corporation | Key-value store for managing user files based on pairs of key-value pairs |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20070073770A1 (en) | Methods, systems, and computer program products for resource-to-resource metadata association | |
US8918447B2 (en) | Methods, apparatus, systems and computer readable mediums for use in sharing information between entities | |
US7590939B2 (en) | Storage and utilization of slide presentation slides | |
US7493561B2 (en) | Storage and utilization of slide presentation slides | |
AU2005225130B2 (en) | Management and use of data in a computer-generated document | |
KR101238541B1 (en) | Methods and systems for providing a customized user interface for viewing and editing meta-data | |
CN100489849C (en) | Programmability for binding data | |
US7725454B2 (en) | Indexing and searching of information including handler chaining | |
US9495376B2 (en) | Content migration tool and method associated therewith | |
JP2005521161A (en) | Processing system used with user interface display | |
US11361035B2 (en) | Batch generation of links to documents based on document name and page content matching | |
GB2499500A (en) | Document merge | |
US20090265372A1 (en) | Management of Document Attributes in a Document Managing System | |
US20060282402A1 (en) | Information processing apparatus, method of controlling information processing apparatus, computer program, and storage medium | |
US20070185832A1 (en) | Managing tasks for multiple file types | |
US20070083546A1 (en) | Information management system and information display device | |
US10262026B2 (en) | Relational file database and graphic interface for managing such a database | |
US11675748B2 (en) | External data repository file integration using a virtual file system | |
WO2011023959A1 (en) | Database access | |
Rodrigues et al. | Control Flow Basics |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: IPAC ACQUISITION SUBSIDIARY I, LLC, NEW HAMPSHIRE Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:MORRIS, ROBERT P.;FRY, JARED S.;REEL/FRAME:017175/0985 Effective date: 20050928 |
|
AS | Assignment |
Owner name: SCENERA TECHNOLOGIES, LLC,NEW HAMPSHIRE Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:IPAC ACQUISITION SUBSIDIARY I, LLC;REEL/FRAME:018489/0421 Effective date: 20061102 Owner name: SCENERA TECHNOLOGIES, LLC, NEW HAMPSHIRE Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:IPAC ACQUISITION SUBSIDIARY I, LLC;REEL/FRAME:018489/0421 Effective date: 20061102 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |