Network-based photosharing architecture

[0002] The present invention relates to electronic storage and sharing of digital images, and more particularly to an improved photosharing architecture.

[0003] Over the past several years, photosharing has become widely accepted by photo enthusiasts. Many websites currently exist that allow users to upload digital images to the site for storage on a server and for viewing by others over the Internet. To share photos, users must first register on a photosharing website, and create an image album in which to store their images. The user typically selects a theme for the image album and selects one or more images to upload to the site from their PC. The images are then uploaded to a server for storage and associated with the selected album. After creating the image album, the user may optionally rename and/or edit each photo.

[0004] Metadata, which is typically associated with an image or group or images, is typically supported by photosharing sites. This metadata is restricted in that users cannot define new metadata fields or are limited to a fixed number of “user defined” fields. Metadata support usually does not extend much beyond that defined by the Exif image file format standard. Searches are usually limited to only a subset of the limited metadata that is supported by a site.

[0005] The user may then notify others of the album using one of two methods. In the first method, the user sets preferences for the album specifying what users have permission to view the album, and personally informs each person of the web address of the album. In the second and more common method, the user types-in the e-mail addresses of each person the user wants to view the album and the photosharing site automatically sends an e-mail inviting recipients to view the album by clicking on the enclosed URL.

[0006] Although the current approach to photosharing works for its intended purpose, there are some areas where the traditional server centric photosharing falls short. Those areas include the difficulties users encounter when attempting to upload images to the site, and the cumbersome process of organizing images once on the site. Due to these difficulties, users predominantly store the majority of their images on their local PC, and upload only those images that they really wish to share with others. Because the shortcomings of current photosharing sites force users to store some of their images on their PCs and other images on the photosharing site, the usage model for web-based photosharing is unnecessarily complicated.

[0007] Another problem associated with current photosharing websites is the infrastructure cost inherit in hosting such a space intensive application on a single site. Not only do traditional photosharing sites require vast amounts of disk space to store the photos of all their users, but the owners of the websites must also incur the cost of redundant disk space that is used for backup purposes. Based on high infrastructure costs and the increasing number of users, it is believed that most photosharing sites will pass on this cost to users by transitioning from a free service to a monthly subscription fee model. Charging a fee for using photosharing websites may actually inhibit the widespread adoption of such sites.

[0008] Accordingly, what is needed is an improved photosharing architecture. The photosharing architecture should solve both storage and usability problems, and alleviate infrastructure requirements for photosharing. The present invention addresses such a need.

[0009] FIG. 1 is a block diagram illustrating a network-based photosharing system in accordance with a preferred embodiment of the present invention.

[0010] FIG. 2 is a block diagram illustrating the peer node application software.

[0011] FIG. 3 is a block diagram illustrating the contents of the central site peer server.

[0012] FIG. 4 is a diagram illustrating relationship between metadata schemas that are stored in the metadata repository and the actual metadata and images.

[0013] FIG. 5 is a flow chart illustrating a registration and installation process for a user to sign up with the network-based photosharing service.

[0014] FIG. 6A is a flow chart illustrating in further detail the synchronization process between the peer demon and the peer server (step 114 of FIG. 5).

[0015] FIG. 6B is a flow chart illustrating the handling of pending requests when a peer node comes back online and has registered with the peer server.

[0016] FIGS. 7A-D are flow charts illustrating the process of a user uploading image metadata to the peer server using the peer node software.

[0017] FIGS. 8A-C are flow charts illustrating the process of creating and managing an image album on a peer node.

[0018] The present invention is a method and system for providing a network-based photosharing service. The photosharing service includes a central photosharing site known as the peer server, and a plurality of peer nodes each containing digital images. The method and system include associating metadata with each image that is to be shared. The images are shared by uploading the metadata associated with each image from the peer nodes to the peer server, while maintaining storage of the images on the respective peer nodes. In response to the peer server receiving search criteria based on the metadata submitted from a first one of the peer nodes, the peer server returns a list of image locators for images matching the search criteria to the first peer node. The method and system further include dynamically generating on the first peer node an image album that contains at least a portion of the matching images.

[0019] According to the method and system disclosed herein, the present invention provides a network-based photosharing architecture that solves both storage and usability problems, while greatly enhancing searching capabilities.

[0020] The present invention relates to a method and system for providing a web-based, peer-to-peer photosharing service. The following description is presented to enable one of ordinary skill in the art to make and use the invention and is provided in the context of a patent application and its requirements. Various modifications to the preferred embodiments and the generic principles and features described herein will be readily apparent to those skilled in the art. Thus, the present invention is not intended to be limited to the embodiments shown but is to be accorded the widest scope consistent with the principles and features described herein.

[0021] The present invention provides an improved network photosharing service that solves storage problems encountered by photosharing service providers and also solves photo sharing usability problems encountered by users of the service. The present invention provides a web-based, peer-to-peer photosharing service in which all workstations and computers in the network store their own images and act as servers to other users on the network. A central server, known as the peer server, is provided that stores metadata about all of the images and provides users with a search capability to find images of interest.

[0022] FIG. 1 is a block diagram illustrating a peer-to-peer (P2P) photosharing system in accordance with a preferred embodiment of the present invention. According to the present invention, the system 10 includes a central photosharing website 12 that includes a peer server 14, and multiple peer nodes 16. The peer server 14 and each of the peer nodes 16 are capable of communicating with one another over a network, such as the Internet. In a preferred embodiment, users 18 may also access the central site 12 from devices or clients (not shown) that are not peer nodes 16, via the use of a standard web browser.

[0023] In a preferred embodiment, the peer nodes 16 may each represent either a website or a computer, and typically store the digital images 20 of a particular user 18. A peer node may store the images of more than one user. For example, two family members which share a home PC, but manage their images separately may maintain separate accounts with the system 10 on the shared PC The digital images 20 are stored as image files that include image data. Each image also has metadata 22 associated with it that describe and categorize the image. The metadata 22 may be associated with the images 20 by the user 18 or automatically by the peer node 16 as described below. In addition some or all of the metadata 22 may be associated with the image by a digital camera at the time of image capture. Each image 20 may also be associated with a particular type of metadata, which is a smaller representation of the image data, called a thumbnail image 24.

[0024] The present invention is in contrast to the traditional photosharing model where the user 18 would post digital images by uploading the images from his or her computer to a webserver for storage in a static album. Instead, in the present invention, the peer nodes 16 maintain storage of the actual image data and only the metadata 22 (and, in particular, the thumbnail image 24) for each image are uploaded to the peer server 14. Users 18 of the peer nodes 16 register themselves and their peer nodes 16 with the peer server 14 to become members of the service so that other users 18 can search for and view their images 20. The peer server 14 maintains a list of users 18, a list of groups to which users may belong, and peer nodes 16, and provides a search engine and a cache of the metadata for each shared image.

[0025] According to a further aspect of the present invention, users 18 may dynamically create image albums 26 for viewing the images 20 by submitting search criteria that are based on metadata 22. In FIG. 1 for example, user 18ahas shared images 20 on the central site 12 by uploading the metadata 22 to the peer server 14. User 18bmay then submit a search to the peer server 14 to view images 20, which match the search criteria.

[0026] In response, the peer server 14 returns a list of image locators (e.g., URLs) for images 20 matching the search criteria to peer node 16b. The user 18bthen selects entries on the list corresponding to the images to be contained in the album 26. In a preferred embodiment, the user 18bis shown a list of thumbnail images with some subset of metatdata which identifies the image and/or its source, rather than a list of image names. In an alternative embodiment, peer node 16bmay display the list of peer nodes 16 with matching images before retrieving any image data and/or additional metadata, and allow the user to select which peer nodes 16 to use in composing the album.

[0027] After the user 18bmakes his or her selections from the list, the peer node 16bsends requests using the image locators to retrieve the matching images as needed.

[0028] The handling of the requests depends on where the images are being retrieved from. There are three cases: 1) one or more of the selected images are stored on the requesting peer node, 2) one or more of the images are stored on a peer node that may or may not be online at the time, and may or may not have a reachable network address, and 3) the request is for thumbnail images, which are stored on both the peer server 14 and the peer nodes that shared the corresponding images.

[0029] If one or more of the matching images are stored on the requesting peer node 16b, then the images are retrieved from the requesting peer node 16bfor incorporation into the album 26. If one or more images are stored on another peer node 16 that is online and has a network address which is reachable from peer node 16b, then the image locators returned from the peer server 14 direct the peer node 16bto the other peer node 16 for retrieval of the images. In a preferred embodiment, the image locators returned by the server to the peer node 16bindicate which nodes are currently online so that the peer node 16bcan send the URL request directly to the corresponding peer nodes 16 without first sending the request to the peer server 14.

[0030] If one or more images are stored on another peer node 16 that is currently offline, or does not have a network address which is reachable from peer node 16b, the image locators are modified to route the request for the images back to the peer server 14, which in the case of a firewall, acts as a proxy for the peer node 16. After becoming a proxy, the peer server 14 routes the image requests and responses appropriately. If the album 26 that is to be generated includes thumbnail images, which are part of the metadata that is uploaded to the peer server 14, then the server 14 returns the thumbnails directly to the peer node 16b, eliminating the need to retrieve the thumbnails from other peer nodes 16.

[0031] As the peer node 16breceives the responses, the peer node 16baggregates the responses to produce a view of the album 26. In a preferred embodiment, peer node 16bcomposes one or more web pages which user 18 is able to view in a web browser. Peer node 16bmay retrieve the presentation components such as graphic art, page templates, and so on from peer server 14 as needed. Peer node 16bmay cache presentation components retrieved from the peer server 14 for future use to enhance performance.

[0032] According to the present invention, image albums 26 are not statically defined as they are traditional photosharing sites. Instead albums 26 are defined by search criteria, which are based on the metadata 22 and generated on the user's peer node in real-time using not only the user's own images 20, but also the images 20 of other peer nodes. In a preferred embodiment, the albums 26 created as a result of the searches and/or the search criteria may also be saved. They may be saved as search criteria or as the result from the initial search criteria subject to the preferences of the user. The peer-to-peer photosharing system 10 of the present invention has several advantages over traditional photosharing, including:

[0033] significantly reduced image upload time, since images 20 are stored locally,

[0034] search capability for all images in the system,

[0035] the user retains control over locally stored images,

[0036] dramatically reduced infrastructure requirements for the photosharing site, and

[0037] highly scalable infrastructure.

[0038] FIG. 2 is a block diagram illustrating the peer node 16 application software. In a preferred embodiment, a peer node 16 application software includes a peer user interface (UI) 30, a peer upload automation engine 32, a peer daemon 34, and a peer data repository 36. The peer node 16 may also include an optional firewall 38 or access the Internet through a firewall located in another device.

[0039] The peer UI 30 is a graphical user interface application that allows the user 18 to view and edit data. The data in most cases is images 20 and associated metadata, which may reside on both the peer node 16 or on remote peer nodes 16. Although the peer UI 30 may be implemented in a number of different ways, in a preferred embodiment the peer UI 30 is implemented as a web browser but alternately it may be an application specifically designed for the system 10.

[0040] According to a first aspect of the present invention, the peer daemon 34 automatically assigns metadata 22 to the images 20 prior to the metadata upload process. The peer daemon 34 makes intelligent guesses at how to fill-in the metadata values 22 using defaults specified by the metadata schemas. In addition, the peer daemon is trained over time based on the user's past behavior. The peer daemon 34 then makes use of the peer upload automation engine 32 to send the metadata 22 associated with the images to the peer server 14. The metadata facilities of the peer daemon 34 and peer upload engine 32 allow a user 18 to categorize and upload the metadata 22 for a very large number of images 20 to the peer server 14 with ease. The peer daemon 34 also allows the user 18, to make simple edits to the pictures before the images 20 are stored and the metadata 22 is uploaded (rotation for example).

[0041] The peer daemon 34 includes a background process that scans the peer node 16 computer for images 20 that are to be shared, and catalogs metadata about images 20. The peer daemon 34 uses the peer data repository 36 to store images 20 and local copies of the metadata 22. In a preferred embodiment the peer daemon 34 acts as a web server to present the peer UI 30 to the user through a web browser. The peer daemon 34 communicates with the peer server 12 as needed to retrieve presentation components as needed, thus distributing the presentation logic of the system. In a similar manner, the peer daemon 34 may also offload other work from the peer server 14 that is typically the sole responsibility of a central server or site in a traditional photosharing server. Examples of such work activities, include caching and processing of security information, receiving and routing events, acting as a peer proxy 68 for other peer nodes (see description of FIG. 3), and caching user and group account information.

[0042] FIG. 3 is a block diagram illustrating the contents of the central site peer server 14. In a preferred embodiment, the peer server 14 includes a web server application 50, a metadata repository 52, a user and group account database 54, a cache 56, and a peer proxy 68.

[0043] The web server application 50 serves pages formatted to suit the capabilities of the client device so that a standard web browser can be used to view the data returned by the web server. The metadata repository 52 is a database that stores metadata definitions and the metadata 22 uploaded from peer nodes 16 associated with specific images and groups of images 22 associated with images 20 stored on the peer nodes 16. In a preferred embodiment, the metadata definitions are specified using the W3C Resource Definition Framework (RDF) standard. In this preferred embodiment a core metadata schema/vocabulary is defined, which is associated with all images. Groups and users may specify their own metadata 22 vocabularies and may share these vocabularies with other users and groups. Users and group administrators may specify one or more vocabularies, which must be supported for images associated with the user and group accounts, respectively. The peer server 14 and peer nodes 16 enforce these metadata requirements.

[0044] The user account database 54 stores user account and corresponding contact information and preferences of each registered user 18. Groups of users may also share common policies, which may include permission settings, UI options, required and optional metadata vocabularies, subscriptions lists, event/notification policies, and caching policies.

[0045] The cache 56 is used to store the metadata 22 associated with frequently accessed images 20 to provide for quicker searches. The metadata 22 may be automatically replaced in the cache 56 with the metadata 22 from other images 20 based on the peer server's configured caching policies. The peer proxy 68 allows the peer nodes 16 behind firewalls 38 to connect with peer server 14. Once this connection is established other peer nodes 16 may contact the associated peer node 16 behind a firewall 38 by connecting to the peer proxy which will route requests to the peer node behind the firewall and will route responses to the associated node making the request.

[0046] The peer server 14 further includes a search engine 58, a peer directory 60, an event/notification engine 62, a caching engine 64, and presentation logic and resources 66. The search engine 58 takes requests received by various peer nodes 16 and searches through the metadata 22 stored in the metadata repository 52. The search engine 58 also has the capability of offloading searches by passing the search criteria to one or more of the peer nodes 16 to search the metadata 22 stored on the peer node(s)16. In a preferred embodiment, the peer site offloads searches to peer nodes 16 with large amounts of metadata 22. An example of such a peer node 16, is a peer node 16 which is also a traditional centralized photosharing site.

[0047] The peer directory 60 maintains a list of active peer nodes 16 and associates the peer nodes 16 with registered users 18 from the user account database 54. The notification engine 62 is responsible for notifying peer nodes 16 when predefined events occur. Examples of predefined events include other peer nodes 16 becoming active, particular images 20 being posted on the peer server 14, or a request being filled. The caching engine 64 interfaces with the cache 56 and is responsible for determining what data to cache, where to cache it, and how long to hold the data.

[0048] The presentation logic 66 composes the user interface for user interaction with the peer site. The presentation 66 logic also provides templates and presentation resources (e.g., icons, graphics) used by the peer nodes in composing user interface elements. The presentation logic 66 adapts the presentation based on the capabilities of the requesting device and user 18 preferences.

[0049] The peer server 14 may also provide the peer nodes 16 access to external service providers (not shown), which may include print fulfillment providers, or services that burn image albums 26 on CDs or prints real album pages, for instance.

[0050] FIG. 4 is a diagram illustrating metadata definitions 80, which are stored in the metadata repository 52. According to the present invention, the system 10 provides a vocabulary library 82 for storage and management of metadata schemas 84 or vocabularies. In a preferred embodiment, the vocabulary library 82 includes a universal schema, shared schemas, and private schemas, which may be defined using RDF and XML. All images 20 in the system 10 are required to have associated with them metadata 22 specified by the universal schema. Users 18 and groups may define their own schemas, which may include the universal schema and may borrow from other vocabularies as RDF and XML allow.

[0051] As an example, assume that an image 86 of a family with mountains in the background has been added to the system 10 by a user 18a. User 18ahas defined a private schema 88 that includes the universal schema, borrows from a shared schema defined for family metadata, and adds additional metadata for the user 18a′s private use. User 18bhas discovered image 86, perhaps through a search using fields in the universal schema. Seeing the mountains in the picture and being an avid fan of nature photography user 18bcreates nature metadata 90 to associate with image 86 using a shared schema defined for nature photographs. User 18bhas uploaded this metadata 90 for the image to the peer server 14. Other users constructing searches built using one or more of the vocabularies (universal, family, user 18a′s private extensions, and nature) will be able to find image 86 if the search criteria match. The schema definition 84 is not limited by the system 10. Further, there is no theoretical limit to the number of separate instances of metadata 22 which could be provided and associated with images 20. Note that it is user 18a′s option to share the private schema extensions and the private metadata. User 18amay send the private schema specification to the peer server 14 allowing others to construct searches using the private vocabulary. The peer server 14 will require user 18a′s peer node to perform the actual search if the actual metadata has not been stored on the peer server 14.

[0052] In operation, the user 18 first installs peer software on his or her computer to create a peer node 16 and signs-up for the service. The user 18 may share images 20 that are local on the user's peer node 16 with the photosharing site 12 by uploading the image metadata 22, thus synchronizing the peer node 16 and the peer server 14. To view the data, the user 18 may select predefined albums 26 to view for which he has the necessary permissions or user 18 may submit a search, which results in the creation of dynamic image albums 26 that display the images 20 matching the search criteria. These process steps will now be explained in further detail with reference to FIGS. 5-8.

[0053] FIG. 5 is a flow chart illustrating an installation and registration process. The process begins with an Internet user 18 visiting the peer server website is in step 100. The user 18 clicks on a new user button, and is directed to a page for signing up for the peer-to-peer service in step 102. The user 18 enters the required signup information on a sign-up page in step 104. In response, the user 18 obtains a unique peer ID that will be used to identify the user peer node 16 in step 106.

[0054] After becoming a registered user 18, the user 18 downloads the peer node application software 16 in step 108. After downloading the peer node software 16, the user 18 installs the peer node software 16 and invokes the peer daemon 34 in step 110. The user 18 is then given the opportunity to specify images 20 and associated metadata 22 that is to be shared using the system 10 in step 112. The peer daemon 34 automates as much of the process of providing metadata 22 as is possible by providing default values for the required data in the required schemas for the user 18. For a first-time user in a preferred embodiment, the only required data is the data specified in the universal schema. The user is given the opportunity to override any of the automatically supplied values.

[0055] The peer daemon 34 then synchronizes with the peer server 14 and uploads the metadata 22 in step 114. After the image metadata 22 has been uploaded, the user 18 may invite others registered users 18 to visit the site in step 116. The user 18 may invite non-registered users by providing their email addresses. The non-registered users will be sent emails inviting them to register with the peer server 14 after which they may view the user's 18 images.

[0056] FIG. 6A is a flow chart illustrating in further detail the synchronization process between the peer daemon 34 and the peer server 14 as described in step 114 of FIG. 5. This process occurs when the peer node 16 is initiated and when initiated by user 18 additions, deletions, and changes while online. FIG. 6 describes this process in terms of peer node initiation. After the peer node 16 has been initiated, the peer daemon 34 registers with the peer server 14 in step 200. After registration, the peer upload engine 32 sends the peer server 14 a change list in step 202 specifying the metadata for images 20 the user 18 wishes to share on the photosharing site 12 as well as those that the user 18 wishes to delete or has modified. The peer server 14 then updates the metadata repository 52 to reflect which images 20 have been added, modified, and which have been deleted in step 204.

[0057] The system 10 allows requests to be made for images 20 on peer nodes 16 that are offline at the time the request is made. FIG. 6B is a flow chart illustrating the handling of pending requests when a peer node comes back online and has registered with the peer server. When the peer node 16 comes online, the peer node 16 sends a request to the peer server 14 to get any pending requests for images that are stored on the peer node 16 in step 208. Each request for an image includes a URL indicating where to send the response. Once the pending requests are received by the peer node 16, the peer node 16 processes each pending request. The response must be handled differently depending on whether the requesting peer node (requester) is currently online or not. In a preferred embodiment this decision is handled at the peer server in step 210.

[0058] If the requestor is online in step 210, the peer node 16 sends the response to the requestor as indicated by the URL in the request in step 212. If the requester is not online, then since the peer server 14 tracks the peer nodes 16 that are online, the peer server 14 substitutes the requestor's URL in the request with one of its own prior to sending the pending request to the peer node 16 during step 208. When the peer node 16 subsequently processes the request, the response is sent from the peer node 16 to the peer server 14, as indicated by the URL in the request, where it is cached in step 214. When the requestor comes back online in step 216, the requester then requests the cached response from the peer server 14 in step 218. The peer server 14 then routes the cached response to the requester in step 220.

[0059] Note that the processes illustrated in FIG. 6A and FIG. 6B may be executed on separate threads by the peer node 16, so that the user 18 of peer node 16 may interact with the peer node 16 immediately upon peer node initiation without having to wait for synchronization to complete.

[0060] FIGS. 7A-D are a flow charts illustrating the process of a user 18 uploading image metadata 22 to the peer server 14 using the peer node software. The user 18 first must choose whether to specify metadata 22 for an image group in step 302, to specify metadata 22 for a batch of images not in a group in step 304, or to specify metadata 22 for images 20 individually in steps 302 and 304. Note these choices are not mutually exclusive. That is, an image 20 may be part of any image group and thus have group metadata 22 associated with it. The same image may also have metadata 22 associated with it alone apart from other images 20 in the group.

[0061] FIG. 7B illustrates the process of providing metadata for an image group. The user 18 first selects images 20 that are to be associated with the group in step 310. The user 18 then selects which metadata vocabularies to use in step 312. The vocabularies are retrieved from the peer server's 14 vocabulary respository 82 and/or from private vocabularies stored on the peer node 16 only. The user 18 may use the vocabularies as is or combine elements of them to create a new vocabulary. The user 18 may accept the default values provided by the system or override them in step 314. The peer node 16 then sends the data to the peer server 14 as metadata 22 associated with a new image group in step 316.

[0062] FIG. 7C illustrates the process of providing metadata for images in batch mode. This differs from group metadata in that once the metadata 22 is provided, it is associated with each image 20 separately. The images 20 are not part of an image group with respect to this metadata. It is simply a convenient way to enter metadata for a set of images that share the same vocabularies and many of the same values. The user 18 may follow-up this process by modifying selected data items for each image 20 where the data should vary among images. The user 18 first selects images 20 that are to be associated with the metadata 22 in step 322. The user 18 then selects which metadata vocabularies to use in step 324. The vocabularies are retrieved from the peer server's 14 vocabulary library 82 and/or from private vocabularies stored on the peer node 16 only. The user 18 may use the vocabularies as is or combine elements of them to create a new vocabulary. The user 18 may accept the default values provided by the system or override them in step 326. The peer node 16 then creates separate metadata and associates it with each separate image 20 in step 328. Finally, the peer node 16 sends the metadata 22 for each image 20 to the peer server 14 in step 330.

[0063] FIG. 7D illustrates the process of providing metadata for an individual image. This process is a special case of batch mode processing where the number of images to process is one. The user first selects the image 20 that is to be associated with metadata 22 in step 342. The user 18 then selects which metadata vocabularies to use in step 344. The vocabularies are retrieved from the peer server's 14 vocabulary library 82 and/or from private vocabularies stored on the peer node 16 only. The user 18 may use the vocabularies as is or combine elements of them to create a new vocabulary. The user 18 may accept the default values provided by the system 10 or override them in step 346. The peer node 16 then creates metadata 22 and associates it with the selected image 20 in step 348. Finally, the peer node 16 sends the metadata 22 for the image 20 to the peer server 14 in step 350.

[0064] FIGS. 8A-C are flow charts illustrating the process of creating a dynamic image album on a peer node 16. FIG. 8A illustrates the basic choices available to a user 18 for managing albums. A user 18 may choose to create an album 26 in step 402. If the user 18 chooses to create an album 26, the user 18 is prompted to enter certain required information such as the album's 26 name. Once an album 26 exists, the user 18 may edit the contents of the album in step 404, edit access rights to the album 26 in step 406, edit the presentation attributes of the album 26 in step 408, or edit other album attributes (not shown). In a preferred embodiment, access rights management in step 412 is preformed by managing access control lists (ACLs), but may take other forms such as the model supported by the Java Authentication and Activiation Services framework.

[0065] FIG. 8B illustrates the process of managing the content of an album 26. The user 18 chooses images for the album 26 by selecting one or more albums previously defined in step 420. They may be albums 26 owned by the user 18 or shared with the user. As an alternative or in addition to choosing images from existing albums 26, the user 18 in step 420 may construct a search. The user 18 then selects images 20 from the selected albums and/or searches to be contained in the album 26, and the selected images 20 are placed in the editing card for the album 26 in step 422. The user 18 may delete images 20 from the editing cart of the album 26 in step 424, and may specify the order of the images 20 in the display by modifying the order of the images 20 in the editing cart of the album 26 in step 426. The user 18 may choose to repeat this process in step 428, until finished in step 430.

[0066] FIG. 8C illustrates the process of managing the presentation attributes of the album. The user 18 selects from a list of predefined presentation styles in step 440. The user 18 may then either preview the album 26 in the selected style in step 444 or modify style elements of the selected style in step 442. The user may repeatedly navigate through steps 440, 442, and 444 as needed until the user 18 is satisfied with the presentation of album 26. The user 18 then saves the presentation attributes for the album 26 in step 446 (and may save them as a new named style for later use, or to share with others), and finishes management of the presentation of album 26 in step 448.

[0067] A peer-to-peer photosharing service has been disclosed in which peer nodes maintain storage of actual image data, while uploading metadata corresponding to the images to a peer server for searching by other peer nodes. The present invention has been described in accordance with the embodiments shown, and one of ordinary skill in the art will readily recognize that there could be variations to the embodiments, and any variations would be within the spirit and scope of the present invention. Accordingly, many modifications may be made by one of ordinary skill in the art without departing from the spirit and scope of the appended claims.