Abstract: This disclosure includes a process for merging legacy databases having different data schema into a principal data store. A computing device retrieves a legacy database from each of a plurality of domains of an organization to form a plurality of legacy databases, where at least two legacy databases in the plurality of legacy databases have a different data schema. For each of the plurality of legacy databases, the computing device retrieves data from the respective legacy database, places the data from the respective legacy database into a respective unstructured database, and merges the respective unstructured database into a principal data store designed to hold data for every domain of the plurality of domains.

Abstract: This disclosure includes a process for merging legacy databases having different data schema into a principal data store. A computing device retrieves a legacy database from each of a plurality of domains of an organization to form a plurality of legacy databases, where at least two legacy databases in the plurality of legacy databases have a different data schema. For each of the plurality of legacy databases, the computing device retrieves data from the respective legacy database, places the data from the respective legacy database into a respective unstructured database, and merges the respective unstructured database into a principal data store designed to hold data for every domain of the plurality of domains.

Abstract: A system for collecting and analyzing metadata from peer-to-peer (P2P) media networks. The present invention gathers metadata about P2P media from the P2P network directly as well as relevant 3rd party social networks where that media is discussed. Users access the system via any Internet enabled device. The users' media streaming behavior is collected so that it can determine what they like. That data is indexed for future analysis. The system also monitors social network dialog keyed to the media (e.g. titles, actors, singers). The system then can identify related media on P2P networks and source it so that it is immediately available. The social data collection agents then extract data about the media that users of social networks are providing for the computing of demand for the media and/or performers.

Abstract: A domestic appliance is provided having an appliance body; a control panel mounted to the appliance body, the control panel having a front side visible to a user of the domestic appliance when the appliance is in an operating condition, and a back side facing the appliance body; a light box attached to the back side of the control panel, the light box having an opening that faces the back side of the control panel, a protrusion that protrudes in a direction away from the control panel and surrounds the opening; and a light emitting display board attached to the light box, the light emitting display board having a light source that emits light and directs the light toward the control panel. The light source is surrounded by the protrusion.

Abstract: A system for collecting and analyzing metadata from peer-to-peer (P2P) media networks. The present invention gathers metadata about P2P media from the P2P network directly as well as relevant 3rd party social networks where that media is discussed. Users access the system via any Internet enabled device. The users' media streaming behavior is collected so that it can determine what they like. That data is indexed for future analysis. The system also monitors social network dialog keyed to the media (e.g. titles, actors, singers). The system then can identify related media on P2P networks and source it so that it is immediately available. The social data collection agents then extract data about the media that users of social networks are providing for the computing of sentiment about the media and/or performers.

Abstract: Application responsiveness over a network, such as for a web site or web-based application, is monitored and optionally recorded by tracking actual end users interacting with the application and the time it takes for their requested web pages to load. The process involves a web server that sends instrumented web pages or pointers to such instrumentation code in response to browser requests. This instrumentation causes scripting code on the client browser to gather data sufficient to enable determination of how long the page took to load, with separate measurements for latency time and/or intra-page load time, and to classify the type of request for which the measurements correspond. The scripting code can report the values to a record keeper or an external process. In one embodiment, Page Lifecycle Events are used to track and update a Marker and Timestamp from which the page load times and classifications are derived.

Abstract: Application responsiveness over a network, such as for a web site or web-based application, is monitored and optionally recorded by tracking actual end users interacting with the application and the time it takes for their requested web pages to load. The process involves a web server that sends instrumented web pages or pointers to such instrumentation code in response to browser requests. This instrumentation causes scripting code on the client browser to gather data sufficient to enable determination of how long the page took to load, with separate measurements for latency time and/or intra-page load time, and to classify the type of request for which the measurements correspond. The scripting code can report the values to a record keeper or an external process. In one embodiment, Page Lifecycle Events are used to track and update a Marker and Timestamp from which the page load times and classifications are derived.

Abstract: Described is a collection of type versions (objects) associated with an application program that lists only those type versions that can be bound to an application program. This ensures stability and security by preventing other type versions from being bound to the application program, unless overridden by policy. A type binding process only materializes objects for stored types that correspond to matching type versions in the application's known types collection. The type may be loaded from a local folder, or from a global cache, providing installation flexibility. A data container accessible to the application may be populated with data for fields defined on a type in the collection having a version not bound to the application program, and for fields of a related type not maintained in the collection. Default values are used to populate any unpopulated fields when policy specifies that a different type version be used.

Abstract: Described is a collection of type versions (objects) associated with an application program that lists only those type versions that can be bound to an application program. This ensures stability and security by preventing other type versions from being bound to the application program, unless overridden by policy. A type binding process only materializes objects for stored types that correspond to matching type versions in the application's known types collection. The type may be loaded from a local folder, or from a global cache, providing installation flexibility. A data container accessible to the application may be populated with data for fields defined on a type in the collection having a version not bound to the application program, and for fields of a related type not maintained in the collection. Default values are used to populate any unpopulated fields when policy specifies that a different type version be used.

Abstract: Application responsiveness over a network, such as for a web site or web-based application, is monitored and optionally recorded by tracking actual end users interacting with the application and the time it takes for their requested web pages to load. The process involves a web server that sends instrumented web pages or pointers to such instrumentation code in response to browser requests. This instrumentation causes scripting code on the client browser to gather data sufficient to enable determination of how long the page took to load, with separate measurements for latency time and/or intra-page load time, and to classify the type of request for which the measurements correspond. The scripting code can report the values to a record keeper or an external process. In one embodiment, Page Lifecycle Events are used to track and update a Marker and Timestamp from which the page load times and classifications are derived.

Abstract: An order fulfillment tool may indicate fulfillability information for a plurality of open orders and receive user input specifying one or more orders for potential fulfillment. In response, the order fulfillment tool may indicate revised fulfillability information for orders not specified for potential fulfillment according to the effects on a current inventory if the specified orders were fulfilled. The order fulfillment tool may also recommend orders for potential fulfillment according to user-specified order fulfillment criteria and indicate revised fulfillability information for orders not recommended for potential fulfillment. Such an order fulfillment tool may also receive user input specifying fulfillment levels for individual items of orders and update fulfillability information for other orders according to the effect of the individual fulfillment levels.

Abstract: One embodiment of the present invention provides a system that provides a context-sensitive “community link,” which enables a system or application user to easily access a community forum related to a specific system or application feature. During operation, the system provides a user with access to the system or application feature. While providing such access, the system displays a community link to the user, wherein the community link is directed to a community forum associated with the system or application feature. When the user selects the community link, the system navigates the user to the community forum associated with the system or application feature, so that the user can exchange information with other users about the system or application feature.

Abstract: Systems and methods provide quantity availability information for inventory items via a user interface. The user customizes a quantity available definition, from which the system calculates quantity available for various inventory items and dynamically updates the calculation as a result of changes to inventory classes making up the definition. Using access points within inventory tracking software, the system displays quantity available information to the user via various display formats.

Abstract: A system that generates a unique identifier that employs a public key of a cryptographic key pair as a contribution to a name for an attribute associated with a schema. Additionally, a hash over the relevant entity name, version, and culture can be employed to automatically produce the remaining portion of the unique identifier. The innovation can ensure that the unique identifiers used by a schema are mathematically related to a public key in a way that can not be spoofed by malicious agents. To this end, unique identifiers can be computed at installation time by combining the n-bytes of the public key (or a hash, e.g., SHA1, of the public key) with the first n-bytes of another entity-specific hash (e.g., SHA1) computed with respect to specific attributes.

Abstract: A system and/or methodology that enables schema packaging, distribution and availability. Aspects of the invention employ signing technology to facilitate secure definition of a schema package. The system and/or methodology can also include the schema package as a resource in a client-side assembly thereby guaranteeing that exactly the same infrastructure used to discover the assembly will be leverageable in discovery of the schema package(s). Other aspects can include the schema package as a satellite assemble or as a separate file. In these scenarios, the invention can facilitate constructing and distributing the schema package and information necessary to enable the client to interact with the store with regard to uninstalled schemas.

Abstract: Systems and methodologies that facilitate evolving a data model via a combination of an explicit logical model definition, logical model changes, functional units, an explicit/implicit physical model and physical model changes, to derive a data model transformation. Such an arrangement can provide for a rich set of transformations, which can be automatically applied to a data model instantiation. The subject invention enables leveraging a common set of code, by defining the set of transformations across an arbitrary data model.

Abstract: Systems and methodologies that facilitate data handling among participants with mismatched schema sets of an extensible data model, via employing a versioning component. The versioning component can identify and separate the mismatched and matched data, and direct the mismatched portion to a bit bucket component. The bit bucket component can further persistently store the mismatched data, to enable interaction among participants with mismatched data types. The data can be re-integrated to ensure that round trip data is available to the next participant.

Abstract: The subject invention provides a system and/or a method that facilitates manipulating data associated to a data storage system, wherein the data storage system has at least one of a characteristic and a constraint associated to a data model. The data model can represent the data storage system such that the data storage system is a database-based file system. A data manipulation component can manipulate data associated to the data model and enforces at least one of the constraint and the characteristic to ensure integrity of such system. In addition, an API component can be invoked to provide the manipulation of data within the data storage system.

Abstract: The subject invention provides a system and/or a method that facilitates mapping a data base model to a database object. A type storage system can utilize a storage mapping of a file storage data model. The mapping can describe the database object created based at least in part upon a schema and how instances of the type described in the schema are stored and/or accessed. Furthermore, a query can be provided to find at least one of an item, a document, and/or a contact that satisfy at least one criterion. The type storage system can receive data, wherein the data is at least one of a schema, a data model, a type, a query, and query criteria via an interface to provide the storing and querying. Additionally, the type storage system can generate a view that exposes at least one instance of the type.

Abstract: The subject invention provides a system and/or a method that facilitates adapting at least two disparate file systems. A file system adapter can provide uniformity and/or seamless integration between a first file system and a second file system. The file system adapter can employ a file-backed item that is enriched by a file to provide at least one of a property to an item and a file stream associated with the item. The file-backed item can allow a manipulation by at least one of an API for the first file system and an API for the second file system.