Abstract: The present disclosure relates clustering similar data records together in a hierarchical clustering scheme. Each tier in a cluster corresponds to a minimal match score, which reflects a degree of confidence. In this respect, a higher confidence may lead to smaller sized clusters while a lower confidence may lead to larger sized clusters. Ordinal classification may be used to generate hierarchical clusters. In some embodiments, hierarchical clustering with conflict resolution is used to resolve user-defined hard conflicts in each tier of the clustering results.

Abstract: The present disclosure relates clustering similar data records together in a hierarchical clustering scheme. Each tier in a cluster corresponds to a minimal match score, which reflects a degree of confidence. A hierarchical cluster ID is generated for respective data records. The hierarchical cluster ID may be made up of a series of values, wherein each value reflects a tier within the hierarchical clustering scheme. A user may enter a partial hierarchical cluster ID to select clusters associated with a lower confidence. Thus, in some embodiments, the hierarchical cluster ID is variable in length in a manner that corresponds to the tiers in the hierarchical clustering scheme.

Abstract: The present disclosure relates clustering similar data records together in a hierarchical clustering scheme. Each tier in a cluster corresponds to a minimal match score, which reflects a degree of confidence. In this respect, a higher confidence may lead to smaller sized clusters while a lower confidence may lead to larger sized clusters. Ordinal classification may be used to generate hierarchical clusters. In some embodiments, hierarchical clustering with conflict resolution is used to resolve user-defined hard conflicts in each tier of the clustering results.

Abstract: The present disclosure relates clustering similar data records together in a hierarchical clustering scheme. Each tier in a cluster corresponds to a minimal match score, which reflects a degree of confidence. A hierarchical cluster ID is generated for respective data records. The hierarchical cluster ID may be made up of a series of values, wherein each value reflects a tier within the hierarchical clustering scheme. A user may enter a partial hierarchical cluster ID to select clusters associated with a lower confidence. Thus, in some embodiments, the hierarchical cluster ID is variable in length in a manner that corresponds to the tiers in the hierarchical clustering scheme.

Abstract: The present disclosure relates clustering similar data records together in a hierarchical clustering scheme. Each tier in a cluster corresponds to a minimal match score, which reflects a degree of confidence. A hierarchical cluster ID is generated for respective data records. The hierarchical cluster ID may be made up of a series of values, wherein each value reflects a tier within the hierarchical clustering scheme. A user may enter a partial hierarchical cluster ID to select clusters associated with a lower confidence. Thus, in some embodiments, the hierarchical cluster ID is variable in length in a manner that corresponds to the tiers in the hierarchical clustering scheme.

Abstract: The present disclosure relates clustering similar data records together in a hierarchical clustering scheme. Each tier in a cluster corresponds to a minimal match score, which reflects a degree of confidence. In this respect, a higher confidence may lead to smaller sized clusters while a lower confidence may lead to larger sized clusters. Ordinal classification may be used to generate hierarchical clusters. In some embodiments, hierarchical clustering with conflict resolution is used to resolve user-defined hard conflicts in each tier of the clustering results.

Abstract: A user may operate many devices, each of which may provide a set of actions, such as installing firmware or software or viewing the contents of the device. However, in order to perform these actions, the user may have to interact with each device using a different user interface, resulting in an inconsistent user experience. Instead, a device action service may allow a user to identify his or her devices, may identify the actions available for each device (e.g., by interacting with a device source of each device, such as a manufacturer); and upon the request of the user, may present a list of the user's devices and the actions available for each device. The actions may comprise hyperlinks to various portions of the website of the device source (e.g., a driver page and a service registration page), or controls invoking the requested action upon the device.

Abstract: A user may operate many devices, each of which may provide a set of actions, such as installing firmware or software or viewing the contents of the device. However, in order to perform these actions, the user may have to interact with each device using a different user interface, resulting in an inconsistent user experience. Instead, a device action service may allow a user to identify his or her devices, may identify the actions available for each device (e.g., by interacting with a device source of each device, such as a manufacturer); and upon the request of the user, may present a list of the user's devices and the actions available for each device. The actions may comprise hyperlinks to various portions of the website of the device source (e.g., a driver page and a service registration page), or controls invoking the requested action upon the device.

Abstract: A user of a set of devices may wish to view the availability statuses of respective devices (e.g., an indication of connectivity, and optionally associated information such as battery power and processor availability). However, users are often familiar with availability statuses (and the indicators representing such statuses) of contacts in a chat environment, such as “available,” “busy,” and “unavailable.” Therefore, device availability statuses may be presented using the same semantics and aesthetics of contact availability statuses, e.g., using the statuses and indicators of a chat environment, including an “available” (available and ready to provide services), “busy” (reachable but unable to provide services), and “unavailable” (unreachable). This user interface design may result in a more easily understandable semantics and a more visually consistent user experience.

Abstract: A user may operate many devices, each of which may provide a set of actions, such as installing firmware or software or viewing the contents of the device. However, in order to perform these actions, the user may have to interact with each device using a different user interface, resulting in an inconsistent user experience. Instead, a device action service may allow a user to identify his or her devices, may identify the actions available for each device (e.g., by interacting with a device source of each device, such as a manufacturer); and upon the request of the user, may present a list of the user's devices and the actions available for each device. The actions may comprise hyperlinks to various portions of the website of the device source (e.g., a driver page and a service registration page), or controls invoking the requested action upon the device.

Abstract: A computer readable medium stores executable instructions to graphically display file object attributes of one or more file objects. Executable instructions receive from a list of file object attribute perspectives a selection of a selected file object attribute perspective specifying one or more file object attribute categories. Executable instructions also display the file object attribute categories for the selected file object attribute perspective and the corresponding file object attributes for each file object.