Abstract: Various systems and methods are provided that allow reviewers to properly and timely label communications and easily view such communications. Certain systems and methods organize one or more communications in a tile layout so that reviewers can properly and timely label communications. A reviewer can hover over any of the communications to view more details regarding the communication and/or label the communication. For example, while the cursor is placed over the displayed communication, the reviewer can provide a command, such as a key command. Once the command is provided, the displayed communication is labeled with a label associated with the command.

Abstract: Various systems and methods are provided that allow reviewers to properly and timely label communications and easily view such communications. Certain systems and methods organize one or more communications in a tile layout so that reviewers can properly and timely label communications. A reviewer can hover over any of the communications to view more details regarding the communication and/or label the communication. For example, while the cursor is placed over the displayed communication, the reviewer can provide a command, such as a key command. Once the command is provided, the displayed communication is labeled with a label associated with the command.

Abstract: Various systems and methods are provided that allow reviewers to properly and timely label communications and easily view such communications. Certain systems and methods organize one or more communications in a tile layout so that reviewers can properly and timely label communications. A reviewer can hover over any of the communications to view more details regarding the communication and/or label the communication. For example, while the cursor is placed over the displayed communication, the reviewer can provide a command, such as a key command. Once the command is provided, the displayed communication is labeled with a label associated with the command.

Abstract: Various systems and methods are provided that allow reviewers to properly and timely label communications and easily view such communications. Certain systems and methods organize one or more communications in a tile layout so that reviewers can properly and timely label communications. A reviewer can hover over any of the communications to view more details regarding the communication and/or label the communication. For example, while the cursor is placed over the displayed communication, the reviewer can provide a command, such as a key command. Once the command is provided, the displayed communication is labeled with a label associated with the command.

Abstract: Various systems and methods are provided that allow reviewers to quickly save, identify, retrieve, and share communications. For example, systems and methods described herein may allow a reviewer to store at least a portion of a communication, called a snippet, in a postboard. For example, a reviewer can highlight a portion of the content of a communication. Once the portion is highlighted, the reviewer can select a snippet command, which stores the highlighted portion in the postboard. Each snippet stored in a postboard includes at least a portion of the content that was highlighted and a link to the communication from which the snippet originates.

Abstract: In some example embodiments, a system comprises a communication module to receive a request, over a network at a server machine, for an interface, from a client machine, and an interface generation module configured to generate the interface at the server machine, The interface is generated from a template and comprises a first interface element in a first position on the interface and a visibility status associated with the first position. The visibility status causes the first interface element to be hidden, The interface generation module can also receive a request for an update to the interface from the client machine and communicate the update to the client machine. The update causes a copy of the engine on the client machine to update the interface based on the template by displaying the first interface element based on a change of the visibility status.

Abstract: Various systems and methods are provided that allow reviewers to properly and timely label communications and easily view such communications. Certain systems and methods organize one or more communications in a tile layout so that reviewers can properly and timely label communications. A reviewer can hover over any of the communications to view more details regarding the communication and/or label the communication. For example, while the cursor is placed over the displayed communication, the reviewer can provide a command, such as a key command. Once the command is provided, the displayed communication is labeled with a label associated with the command.

Abstract: Methods and systems to consistently generate web content are described. The system receives a request, at a server machine, for an interface, from a client machine and generates the interface. The interface includes a plurality of view components that includes a first view component. The system generates the first view component by utilizing a data binding engine that executes on the server machine to apply at least one interface element to a first position on the interface based on a presentation template and first view component information. The first view component is updated on the client machine utilizing a data binding engine that executes on the client machine to apply the at least one interface element to the first position on the interface based on the presentation template and the first view component information. The interface element is visibly displayed at the client machine.

Abstract: Various systems and methods are provided that allow reviewers to quickly save, identify, retrieve, and share communications. For example, systems and methods described herein may allow a reviewer to store at least a portion of a communication, called a snippet, in a postboard. For example, a reviewer can highlight a portion of the content of a communication. Once the portion is highlighted, the reviewer can select a snippet command, which stores the highlighted portion in the postboard. Each snippet stored in a postboard includes at least a portion of the content that was highlighted and a link to the communication from which the snippet originates.

Abstract: Various systems and methods are provided that allow reviewers to quickly save, identify, retrieve, and share communications. For example, systems and methods described herein may allow a reviewer to store at least a portion of a communication, called a snippet, in a postboard. For example, a reviewer can highlight a portion of the content of a communication. Once the portion is highlighted, the reviewer can select a snippet command, which stores the highlighted portion in the postboard. Each snippet stored in a postboard includes at least a portion of the content that was highlighted and a link to the communication from which the snippet originates.

Abstract: Various systems and methods are provided that allow reviewers to properly and timely label communications and easily view such communications. Certain systems and methods organize one or more communications in a tile layout so that reviewers can properly and timely label communications. A reviewer can hover over any of the communications to view more details regarding the communication and/or label the communication. For example, while the cursor is placed over the displayed communication, the reviewer can provide a command, such as a key command. Once the command is provided, the displayed communication is labeled with a label associated with the command.

Abstract: Methods and systems to consistently generate web content are described. The system receives a request, at a server machine, for an interface, from a client machine and generates the interface. The interface includes a plurality of view components that includes a first view component. The system generates the first view component by utilizing a data binding engine that executes on the server machine to apply at least one interface element to a first position on the interface based on a presentation template and first view component information. The first view component is updated on the client machine utilizing a data binding engine that executes on the client machine to apply the at least one interface element to the first position on the interface based on the presentation template and the first view component information. The interface element is visibly displayed at the client machine.

Abstract: A system and method for automated layout of collaboratively selected images within a compilation for printing, viewing, etc. The images may be drawn from any number of albums owned by various users, and have associated rankings reflecting the users' behavior regarding the images (e.g., viewing, printing, recommending). Some number of images is selected for the compilation (e.g., the highest ranked images) and the images are arranged into chapters that correspond to the albums in which they are located. Within each chapter, images are ordered by time and grouped into clusters of related images (e.g., close in time, same event, same subject). Page templates are used to determine how many images to place on a page, and may be designed or redesigned so that the prominence (e.g., size) of each image corresponds to its ranking. The chapters, pages and/or images may be augmented with titles or captions.

Abstract: A system and method for automated layout of collaboratively selected images within a compilation for printing, viewing, etc. The images may be drawn from any number of albums owned by various users, and have associated rankings reflecting the users' behavior regarding the images (e.g., viewing, printing, recommending). Some number of images is selected for the compilation (e.g., the highest ranked images) and the images are arranged into chapters that correspond to the albums in which they are located. Within each chapter, images are ordered by time and grouped into clusters of related images (e.g., close in time, same event, same subject). Page templates are used to determine how many images to place on a page, and may be designed or redesigned so that the prominence (e.g., size) of each image corresponds to its ranking. The chapters, pages and/or images may be augmented with titles or captions.

Abstract: A system and method for sharing images and collaborating in the selection of images likely to be interest to a user. Images (e.g., photos) are shared within a community of users, by allowing user to access any unrestricted community image, recommend an image to another user, assemble compilations of any images the user can access, etc. Various metrics regarding user activity are tracked, such as how often an image was viewed, downloaded, recommended, included in a compilation, printed, edited, etc. The metric values may be normalized, and then weighted and combined to produce, for each image, a ranking or rating personalized to an individual user. Ratings of images for a user may be used to order them for electronic presentation, assemble a set of images for an electronic compilation (e.g., an online album) or physical compilation (e.g., a photo book, a yearbook) or for some other purpose.

Abstract: A system and method for sharing images and collaborating in the selection of images likely to be interest to a user. Images (e.g., photos) are shared within a community of users, by allowing user to access any unrestricted community image, recommend an image to another user, assemble compilations of any images the user can access, etc. Various metrics regarding user activity are tracked, such as how often an image was viewed, downloaded, recommended, included in a compilation, printed, edited, etc. The metric values may be normalized, and then weighted and combined to produce, for each image, a ranking or rating personalized to an individual user. Ratings of images for a user may be used to order them for electronic presentation, assemble a set of images for an electronic compilation (e.g., an online album) or physical compilation (e.g., a photo book, a yearbook) or for some other purpose.

Abstract: A system and method for sharing images and collaborating in the selection of images likely to be interest to a user. Images (e.g., photos) are shared within a community of users, by allowing user to access any unrestricted community image, recommend an image to another user, assemble compilations of any images the user can access, etc. Various metrics regarding user activity are tracked, such as how often an image was viewed, downloaded, recommended, included in a compilation, printed, edited, etc. The metric values may be normalized, and then weighted and combined to produce, for each image, a ranking or rating personalized to an individual user. Ratings of images for a user may be used to order them for electronic presentation, assemble a set of images for an electronic compilation (e.g., an online album) or physical compilation (e.g., a photo book, a yearbook) or for some other purpose.

Abstract: A system and method for communicating a side effect of a data request, from a data server and through one or more caches, inline with a response to the request. Instead of sending a separate notification of the side effect (e.g., instructions to invalidate data cached in one or more caches), the notification is included in the response. As the response traverses caches on its way to the requestor, each cache applies the side effect with the proper timing. Thus, data invalidation may be performed prior to caching data included in the request and/or forwarding the response toward the requester. A final cache configured to serve the response to the requestor may remove the side effect notification before serving the response.

Abstract: A system and method for communicating a side effect of a data request, from a data server and through one or more caches, inline with a response to the request. Instead of sending a separate notification of the side effect (e.g., instructions to invalidate data cached in one or more caches), the notification is included in the response. As the response traverses caches on its way to the requestor, each cache applies the side effect with the proper timing. Thus, data invalidation may be performed prior to caching data included in the request and/or forwarding the response toward the requester. A final cache configured to serve the response to the requestor may remove the side effect notification before serving the response.