WO2019148133A2

WO2019148133A2 - System and method for duplicating items from a website and tracking original content source

Info

Publication number: WO2019148133A2
Application number: PCT/US2019/015470
Authority: WO
Inventors: Alexandra SHADROW; Akshay KOLTE
Original assignee: Unitiques, Llc
Priority date: 2018-01-26
Filing date: 2019-01-28
Publication date: 2019-08-01
Also published as: WO2019148133A3

Abstract

Exemplary embodiments described herein include software and/or hardware solutions to permit users to duplicate content on a website or application and/or to improve associating desired attributes to a user for improved recommendations and/or search results based upon user actions.

Description

System and Method for Duplicating Items from a Website and Tracking Original Content

Source

PRIORITY

[0001] This application claims priority to U.S. Application Number 62/622,487, filed January 26, 2018, which is incorporated by reference in its entirety into this application.

BACKGROUND

[0002] The internet and world wide web is a large source of available information, including text, images, video streams, audio streams, and combinations thereof. Information routinely is reused and repeated for various purposes. Presently when a user wants to share information they find on the internet, they can use the social media sharing tools such as like, or retweet. These options conventionally create an embedded link that can be put in an email or posted on a user’s webpage or feed. The embedded link permits another user to click and traverse the internet to the original website that provided the information. However, the source or origin of the information is always clear - the link directs any new user to the original content.

[0003] Given the large amounts of available information on the internet, finding relevant information based on the specific preferences of a user can be difficult. Internet search preferences may remember links that a user may have previously selected and elevate those same links in the results list presented when the same search is conducted. However, there is little input provided from the user on preselecting desired results, or in learning based on other activities of the user and/or in making correlations among related activities. SUMMARY

[0004] Exemplary embodiments described herein include a system and method for a user to efficiently, such as through a single action, to create a copy of a website or portion thereof and/or pull specific information from a page or application and recreate a copy on their own page within the system. The system and method may include connections between the original information and the copied information to track origin, limit duplication, or for other reasons.

[0005] Exemplary embodiments described herein include a system and method for providing a user relevant search results and/or to provide information to a user customized for a specific and individual user. Exemplary embodiments may update the criteria for assessing the relevance of a searching attribute based on the action of the specific and individual user, and/or on other users having similar preferences.

FIGURES

[0006] FIG. 1 illustrates an exemplary diagram of an embodiment of a client-server network environment to implement embodiments described herein.

[0007] FIG. 2A illustrates an exemplary system architecture for entering a new item into the system.

[0008] FIG. 2B illustrates an exemplary system architecture for duplicating an item already present in the system.

[0009] FIG. 2C illustrates an exemplary system architecture for the consumption of a duplicated item. [0010] FIG. 2D illustrates an exemplary system process that may occur in the back end when an outfit is duplicated.

[0011] FIG. 3 is an exemplary system architecture for recording and parsing attribute scores for a user.

[0012] FIG. 4 illustrates an exemplary user interface for entering items into the system.

[0013] FIG. 5 illustrates an exemplary user interface for viewing items within the system.

[0014] FIGS. 6A-6C illustrate exemplary user interfaces for adding items to an outfit to define a separate sellable unit.

DETAILED DESCRIPTION

[0015] In the following description of preferred embodiments, reference is made to the accompanying drawings which form a part hereof, and in which it is shown by way of illustration specific embodiments in which the invention can be practiced. It is to be understood that other embodiments can be used and structural changes can be made without departing from the scope of the embodiments of this invention.

[0016] Exemplary embodiments described herein may include computer implemented systems that allow users to add, browse and consume items to/from the system. The items may refer to any physical item or digital content like photography, artwork, videos, computer generated artwork, other information or data, and any combination thereof.

[0017] FIG. 1 illustrates an exemplary diagram of an embodiment of a client-server network environment to implement embodiments described herein. The network 1002 is used to connect multiple devices of one or more users. The devices may connect directly to the network 1002 or through a modem 1020. The devices may include, for example, mobile devices, such as smart phones 1014, tablets 1012, laptop 1016, or other portable devices 1010 and generally non- mobile devices, such as desk top computers 518. The network 1002 connects the devices to servers 1005 that provide information to and from the devices from databases 1006.

[0018] An application resident on a client device, such as devices 1010, 1012, 1014, or 1016, or executed through a browser such as run on devices 514, 516, or 518, communicates over the network 1002 with the one or more servers 1005 in communication with one or more databases 1005. This client device-server system is configured to enable a user of the client devices to perform the methods described herein. For example, the user may search the internet for information, view images and/or text, enter information, retrieve information, select or identify information, and copy the information to another display of the application, and combinations thereof. The client devices may have a downloadable application running resident on the device and communicating across the network, or may execute an application through a browser scripted to run one or more programs that interact over the network.

[0019] An exemplary server 1005 receives one or more pieces of user information, such as text, images, audio, video, and combinations thereof. The server may keep a profile of the one or more pieces of data or information. One or more modules may be stored as non-transitory machine executable code on memory coupled to the network. The code may be executed by a processor to perform the functions of the module. Exemplary modules may also be any combination of hardware or software to perform the described functions. [0020] A module, such as a client application on the mobile client device or server applet resident on the server and run on a client browser, may be configured to receive one or more pieces of information. The module may communicate over the network, such as the internet, to the server, which stores the information in a database. One or more modules may be configured to receive an input from another user separate from the posting user. The input indicates the user’s desire to copy information from the posting user and repost the information on another page of the application corresponding to the user such that a duplicate portion of information is posted on two separate pages, the posting user’s page and the user’s page. Exemplary embodiments permit the input to be a single action, such as a single click, swipe, gesture, or other input. One or more modules may then use the information to perform the algorithms described herein. The server applet works with a browser application resident on the client device and serves one or more web pages to the client device with the resident browser.

[0021] In an exemplary embodiment of a duplication feature, a member of the system may select an item for duplication. The duplication action results in that item, including any combination of text, video, image, audio, or other data set, being added to the profile of the member taking the action just as if that member had uploaded the information themselves. Items that are duplicated in this was may or may not be identified as duplicated. Duplicating items improves visibility, proves a greater chance for members to come across items, and increases the chances for the item to be seen by others on the system.

[0022] The action of duplication is unique from the“Share” action as seen on websites like Poshmark, Facebook or Tradesy, because, unlike sharing, duplicating does not generate an embedded link i.e. a duplicated item does not create a link back to the member’s profile that originally added the item. Any viewer to the next user’s page of a duplicated item is viewing all of the details of the item and consuming the information directly with the member that duplicated the item and not sent back to the original post. The duplication action in the same way is different than“Retweeting” as seen on Twitter or“Pinning” as seen on Pinterest. Unlike these features, the duplication action of the exemplary embodiments described herein does not generate an embedded link back to the original member’s profile.

[0023] The internet is a large deposit of information. The information may include information about things, provide sources for purchasing things, or the internet may permit the direct purchase of things. Most posted information includes an image, text description, and if it is for sale, then sizes, sku or identification numbers, and purchase abilities.

[0024] In an exemplary embodiment of a marketplace, exemplary embodiments of the system and method permits its members to buy and sell items (specifically clothes, shoes, accessories, home decor, electronics, and more) as well as outfits (a collection of various items). Members of the marketplace can browse, search and buy items added by other members. They may conduct their transactions online or offline (in-person). While the marketplace may be hosted on the cloud, members may access it from any device that is connected to the internet including personal computers, tablets or mobile devices. Members use the system to add (termed as upload) items. Items uploaded are added to the member’s profile and are subsequently visible to other members. Members may also create outfits by combining together items that they have uploaded themselves as well as items uploaded by other members. Created outfits are also visible on member profiles and can be purchased. Such a purchase results in the individual purchase of items within the outfit. The outfit purchase may be priced lower than the combined price of the contained items. [0025] In an exemplary embodiment of the marketplace, a member of the system may select an item for duplication. The duplication action results in that item or outfit being added to the profile of the member taking the action just as if that member had uploaded the item or created the outfit themselves. Items or outfits that are duplicated in this was may or may not be identified as duplicated. Duplicating items improves visibility, provides a greater chance for members to come across items and outfits they like, and increases the chances for the item or outfit to be sold.

[0026] If an item or outfit is sold from the profile of a member that has duplicated it, exemplary embodiments may create a link or identifier between the duplicated post and the original post such that both the member who originally added the item and the member that duplicated the item may be compensated.

[0027] Exemplary embodiments may limit the times a member may duplicate an item.

For example, the same member may not be able to duplicate an item more than once. The duplication action may not be timeline based. Therefore, duplicating an item may or may not cause an item to be posted to a feed.

[0028] The system can work on any mobile handheld device or computer including smart phones (such as, but not limited to, Apple iPhones, Android based devices, Windows Mobile devices, and Blackberrys), personal computers, television accessories (e.g. Apple TV), and tablets (e.g. The Apple iPad).

[0029] FIG. 2A illustrates an exemplary system architecture for entering a new item into the system. As shown at step 202, a user adds an item to the system. When a user adds an item to the system, the system presents the user with a user interface through the application and the user enters in the information associated with the item as described herein. The user interface may include one or more templates to prompt specific types of information and/or accommodate different types of data, such as images, video, audio, text, and combinations thereof. The information may include an image, text, audio files, video files, single or multiple description attributes, and combinations thereof. At step 204, the item and its associated information are saved into a database in communication with the user interface. The system assigns an item ID for the item, and saves the user ID with the item. At step 206, the item is also identified as having an owner, or other indicator that it is an original entry and not duplicated.

[0030] FIG. 2B illustrates an exemplary system architecture for duplicating an item already present in the system. As illustrated, when an item is duplicated, the item and its associated information is duplicated in the database. The item retains the same item ID and is given the user ID associated with the new user that duplicated the item. The item is also indicated as being a duplicate and not the original posting. As shown at step 208, a second user, separate than the original poster of an item indicates the desire to duplication the item. The user may indicate the intent by entering an input into the system. The input may be a single gesture entry, such as a click on a user interface item or performing a gesture or other input relative to the item and/or display item associated with the item. For example, when an item is displayed on a user’s page, it may include a display item, such as a button or icon indicating a desire to duplicate an item. The second user may click on the icon. Other gestures are also contemplated such as touching the item or gesturing relative to the item, such as swiping in a given direction over or on the display of the item. Once a user input is detected, at step 210, the system is configured obtain the item ID and user ID of the original poster. At step 212, the system is configured to copy the item information into the database and associate the item with the user that duplicated the items. In exemplary embodiments, the system may track that the item is duplicated by indicating an item type within the database. The system may also track the original user that posted the item, such as adding the user ID of the original poster to the database entry of the reposter.

[0031] In an exemplary embodiment, the indication that the user is not the original or owner of the item may be used to impose limitations on the system. For example, the ability to repost from a reposted item, and/or the number of times an item may be reposted, or other limitation may be imposed. In an exemplary embodiment for product purchases, the tracking of the repost and original post may be used to split compensation for the item, and/or inform the original owner of the purchase so that the transaction can be consummated and item sent. For example, if a product is duplicated by a user, and the item is purchased from the second user, the original user may be notified so that the transaction can be completed through the original user, and a commission may be paid to the user that duplicated and reposted the item. For e.g. Let us say, User A adds Item 1 to their profile for sale and User B duplicates the item. Now, if User C views the item from User B’s profile and purchases it, both User A and User B are compensated for this action and/or User A is compensated and informed of the transaction to complete the transaction and ship the item. The amount and format of the compensation may vary from system to system.

[0032] In an exemplary embodiment, an item may be consumed and tracked to the original poster. For example, when an item is purchased from a user’s profile, the system can retrieve the user ID of the profile that sold the item. The system can also determine whether the user ID is the original owner or poster or whether the user ID is a duplicator. If the user ID is associated with the original owner, then the transaction proceeds, the user ID is credited the purchase amount, and the user associated with the user ID can ship the product. If the user ID is not associated with the original owner, then the system can look up the original owner of the item. The system can use the item ID to look up the item and check the owner attribute to determine who the owner of the item actually is. Once the owner is identified, the original owner may be compensated and the transaction completed. The original owner may be informed of purchase details such as shipping address to finalize the transaction. The system may also compensate the user associated with the user ID of the profile where the product was actually purchased from, thereby permitting a split to occur between the original poster and the duplicator.

[0033] FIG. 2C illustrates an exemplary system architecture for the consumption of a duplicated item. Consumption may be any engagement with the duplicated item by a third party, not the original poster or the duplicator. For example, a consumption may include clicking on the item, playing the item (such as if it is a video or audio file), purchasing the item, or other interaction with the item. At step 216, the item is consumed. Consumption may be through the originally posted page, or through the page of the user that has duplicated the item, and not through the original post of the item. At step 218, it is determined that the item is consumed and is associated with a profile. If it is consumed through a profile, then the user identification of the profile owner is retrieved at step 220. At step 224, the system also retrieves the profile status of whether the user is an owner or duplicator. If the profile is the owner of the item, then at step 228, the user that originally posted the item is paid the value for the item and the item is given to the purchaser. If the identifications from step 224 indicates the profile from the poster is not the owner but a duplicator, then at step 226, the identification of the original owner is retrieved. The system then performs step 228 and provides the user that originally posted the item their payment for the value of the item and the item is given to the purchase. However, with the inclusion of a duplicator, the system may optionally also determine an amount to be provided to the duplicator and update their account with the value associated with the resale.

[0034] In an exemplary embodiment, duplicating an item that has already been duplicated may be achieved. However, the system, during the look up of the original poster will focus on the user that was actually able to sell the item and the original poster or owner of the item.

Therefore, even if a user duplicates an item from another user that duplicated the item, the system may be configured to compensate and inform only the first and last user of the duplication chain. For example if User A added the item, then User B duplicates, and User C duplicates it from User B’s profile, it is effectively the same as if User C duplicated the item from User A’s profile. If the item was consumed on User C’s profile, no reward is given to User B. The reward is limited to the user that originally added the item and the user from whose profile the item was consumed. In exemplary embodiments, the duplication chain may be tracked to provide compensation, accolades or other benefit to intervening duplicators.

[0035] In an exemplary embodiment, the system may be configured to define attributes scores. An attribute score may be used to improve search results. FIG. 3 is an exemplary system architecture for recording and parsing attribute scores for a user. Scores may be determined and/or updated based on different actions of the user, such as when they initiate the system and enter information directly to the system, when they search and responds to search results, when they generally interact with the system, when they consume an item, any of their behavior in response to actions through the system, and combinations thereof. [0036] In an exemplary embodiment, a user creates a profile and/or registers with embodiments described herein. Once in the system, the user may engage with the system in a number of ways. In an exemplary embodiment, whenever the user engages or upon certain actions and/or engagement, the system may be configured to define and/or update one or more attribute scores associated with one or more parameters of the system.

[0037] As seen in FIG. 3, at step 302 a user registers with the system and/or navigates to a profile template that permits a user to enter in preferences of the user. For the example of an item of clothing, at step 304, the user is prompted to enter, through a user interface preferred attributes. For example, the user may be requested to enter in preferred brands, styles, sizes, colors, etc. At step 306, the user entered information regarding attributes is entered and stored in the database. At step 308, a preference score is calculated and assigned to each attribute. The score may be assigned in any linear or non-linear scale for e.g. a linear scale between 0 and 100 or logarithmic scale between 0 and 1. For each selection, a user may be assigned a pre- determined base score. In an exemplary embodiment, user defined preferences are given a static preference score. Until the user interacts with the system more fully, the attribute score may be assigned the preference score.

[0038] In an exemplary embodiment, a user interacts with the system and performs actions on the system, which may update one or more attributes scores associated with the user and one or more attributes. Depending on the action, the system is configured to pull attributes associated with the actions. For example, at step 310, a user may consume an item. If a user consumes an item, the user may purchase an item, may click on an item, may search for an item, etc. At step 312, the system is configured to retrieve one or more attributes of the consumed item. At step 314, the system is configured to calculate a base score depending on the action performed, i.e. the type of consumption. In an exemplary embodiment, the system may assign an action score based on the action performed. For example, when a user purchases a product, the attributes associated with the product can be given a higher action score, than when a user clicks on a product, which may have its own relatively high action score but not as high as a purchase. Consumption information may also be considered in determining the action score. For example, the amount of time the user looks at a given product may improve the action score for the attributes of that product. Determination of an action score can be based on the value of the action performed, the amount of time a user performs the action (such as looks at an item), whether a user clicks on an item, whether a user shares the item, whether a user duplicates the item, whether an item is returned in a search, whether an attribute is part of a search string, etc.

At step 316, the system is configured to update an attribute score based on the action score and/or preference score. In an exemplary embodiment, the user may search the system based on an attribute at step 318. The system may be configured to calculate a search score based on the action performed at step 320. At step 322, an attribute score may be updated based on any combination of the preference score, action score, or search score. Such actions and/or searches are configured to raise an attribute value of an item that is regularly associated with an item consumed by the user to indicate a correlation with an interest in the item by the user.

[0039] In an exemplary embodiment, a user interacts with the system and performs a function, the system may recognize correlations between attributes with the given user or among other users. The system may be configured to recognize these correlations and update an attribute score accordingly. Therefore, when a user searches for Brand A, the system may recognize a correlation to Brand B, and be able to define a preference score for Brand B based on the action of search for Brand A. For example, at step 328, related attributes may be determined by the system and a correlation score determined based on the relationship. At step 330 the attribute score may be updated according to the correlation score and any combination of the preference score, action score, and search score. In an exemplary embodiment, other related attributes may have their associated attribute score redetermined based on the correlation to another attribute. When a related attribute is updated that is not directly associated with a consumed item, the attribute score may be updated in a weighted fashion, such that an update based on consumption of an item have an attribute will affect the attribute to a greater extent than any correlated attribute correlated to the attribute of the consumed item, but not directly consumed itself. Referring to FIG. 3, the system may find correlated attributes at step 328 and update an attribute score of the correlated attribute on a weighted scale for the correlated attribute at step 330.

[0040] Other events may also be used for updating an attribute score. For example, at step 324, the system may review the attribute score for a given attribute and a time lapse since the attribute was the basis or included in an item consumed by the user. The amount of time since the last consumption (i.e. part of an item that was viewed, searched, clicked, purchased, duplicated, etc.) the attribute score may be redetermined at step 326 to account for an apparent reduction in interest in the attribute.

[0041] In an exemplary embodiment, the user’s search and resulting actions may define one or more attribute scores for a user. The user may search on specific terms, and then observe or click through different search results. The system may define attribute scores based on the search terms provided, the actions of the user based on the results, and combinations thereof. In an exemplary embodiment, the search terms entered by the user are compared to a keyword database. The matching keyword combinations may be linked to attributes. For e.g. the search term“Boots” may be linked with category“Boots”. The entry may also include a weight and score. Each attribute’s preference score is then re-calculated based on the weighted average as explained herein. The keywords, their associated weights and scores as well as the attributes linked to them may be subject to change over time based on a machine learning algorithm or manual update by the user and/or system administrator.

[0042] In an exemplary embodiment, each action is associated with a weight and score. The resultant attribute score for each attribute is calculated by taking the weighted average of the current score of the attribute. For e.g. the action of entering a preference for an item during the initial system set up may be given a static preference score of 0.6 and a weight of 100%. The action of viewing an item may be assigned a score of 0.8 with a weight of 75%. If the user originally entered in Brand A as a preferred Brand, it was assigned a preference score of 0.6. If the user views an item with Brand A, Style B and Color C then each attribute’s new score will be calculated by taking a weighted average of their existing score and the new score based on the weight specified. For example, with respect to Brand A, it would be the 0.8 weighted by 75% for viewing the product with the 0.6 at 25% weight for having originally entered the product. The resulting score is then .75 for brand A. The attribute’s preference score is therefore equal to the score associated with the action times the weighting factor plus the previous score for the attribute times its weighting score, where the weighting score for the previous score is the remainder of the weight defined by the action weighting. In numerical expression, if W is the weighting factor between 0 and 1 for a given action, and S is the score for a given action and AO is the attribute score originally or previously assigned the attribute, the new attribute score (AS) assigned to an attribute after any action is: AS = S*W + AO*(l-W). [0043] As another example calculation of a preference score using a logarithmic scale: if the user picks Brand A, they may be assigned a base score of 0.6 (an initial predefined preference score). Once the attribute score is assigned, the system searches the database for any co-related attributes or combination of attributes and their pre-calculated score and weight. For e.g. if a user has picked Brand A and Brand B, the system will search the database for a combination of Brand A and Brand B and find a co-related attribute like Style C with a score of 0.5 with a weight of 60%. The scores associated with each attribute can then be updated by taking the weighted average of the existing attribute score and the new score (update scores based on system correlations between items as determined by this user and/or other users). For e.g. if the current score for Style C was 0.2 then the new score will be 0.2 * 40% + 0.5 * 60%

= 0.38. The scores and weights assigned to co-related attributes may be calculated by a machine learning algorithm. The score may also decay over time if it does not result in an action. For e.g. if a user picked Brand A but does not take any action on items with Brand A, the score for Brand A may reduce over time using any linear or non-linear decay formula. Therefore, example embodiments of the system may be configured to update attribute scores based on the action and/or inaction of a user regarding the attribute or related attributes. Similarly, associated scores and weights assigned to attributes may change over time.

[0044] In an exemplary embodiment, the system may compare and update attribute scores whenever an action is performed to trigger an attribute score determination. For example, a user may initially register with the system and directly enter in information that defines one or more preference scores for an attribute. The user then conducts a search some time later, where the search is an action defined to determine one or more search scores for one or more attributes.

The search may define or be used to determine a new attribute score for one or more attributes. The system may compare the attribute scores for the same attribute to determine an updated attribute score. The system may average the scores, may weight a score, or some combination thereof. The system may weight a score based on the way the score was obtain, based on the time since the score was obtained, or combinations thereof. They system may also determine co- relationships between other attributes. If two attributes have a strong correlation for a preference, then the preference score of the first attribute may be increased when the preference score of the second attribute is high for that user or profile.

[0045] Exemplary embodiments described herein may be used in an application for the sale of personal items from one user to another user on the system. The system may therefore be configured to present one or more user interfaces to a user. The user interfaces may be configured to request and receive information that is provided to or from a user and

communicated through the user interface to a database and/or server according to embodiments described herein. The system may thereafter act on the information and return information back to the user. In an exemplary embodiment, the system may be configured to permit different users to create an individual profile specific to a user. The system may be configured to permit a first user to post items for sale by providing different attributes for the item for sale. The system may be configured to permit a second user to search for items for sale. The system may be configured to search for items use and/or update attribute scores for use in searching based on actions of the second user and/or other users. The system may be configured to permit the second user to duplicate an item for sale that was originally posted or duplicated by the user.

The system may be configured to permit a third user to purchase the item from the first or second user. The system may permit any user to define a single item for sale or may define a sellable unit including multiple items. Exemplary embodiments may be used to define items or sellable units within a category.

[0046] Exemplary embodiments may permit a user to create a profile. The system may present to the user a user interface configured on one or more templates for entering information. Exemplary user information may include a log in, password, name, address, payment

information, sizes, and combinations thereof. According to embodiments described herein, the user interface may also prompt the user to enter in preferences associated with attributes of items. For clothing, preferred attributes may include any combination of garment types, materials, brands, sizes, measurements, price ranges, etc. The system may be configured to receive the user profile information through the user interface and communicate the information to a remote location and store the information for the user profile in a database. The system may be configured to determine attribute scores based on one or more entered profile information. Once a user creates a profile, they may be considered a member of the application.

[0047] Exemplary embodiments may permit a member to add items to the system and/or associate items to a profile. ETsers of the system can add items to their own profile. As shown in Figure 1, below, a user can add images and other details to their item and then click the upload button. The user may add details including but not limited to name, category, price, size, color, location, style, brand, description. Once the item has been added into the system it is available on the profile of the user that added it. The item is associated with the user’s id. The purpose of adding the item may vary from system to system. For e.g. the user may add the item for sale, or for downloading, viewing, sharing or other forms of digital and non-digital consumption. [0048] As illustrated in FIG. 4, a user may enter information into the system through one or more user interfaces. The user interface may include a template having one or more data entry locations. Data entry may be through text box entry, drop down selection, radio button selection, other selection, image or other digital recognition input (such as taking a picture of an item, label, tag, description, scanning a QR code or SKU number, etc.). The system may therefore be configured to present the user with a data entry template configured with respect to the item to upload to request desired information relevant to the item. Once uploaded, the system extracts information from the template and saves the information in relevant fields within a system database. The system can save a user identification associated with the user that uploaded the information to track an origin of information. In an exemplary embodiment, the system may be configured to receive an item image 41, item details 42, and permit the user to submit the item for posting through an upload indicator 43.

[0049] Exemplary embodiments may also permit a user to search for items uploaded to the system. Users of the system can search for items that have been added to the system. Their search can be based on various attributes including but not limited to name, category, price, size, color, location, style, brand, description. Users can also search for items that are related to other items they see. For example, if a user is looking at a jacket they can search for items that go with the jacket like pants, or bags. Searches may be conducted through one or more input areas on a user interface. For example, a user may enter text into a text box and the system may search various attributes of its system to find items corresponding to the entered text. The user may also be presented with a template that may be used to narrow search criteria, such as through one or more text entries, one or more drop downs, one or more selection features, to narrow results. Supplemental search features may be presented based on the category of the items returned in the search or based on an input of the user. For example, if the user is looking for a bag, the system may permit the user to narrow the search by selecting for pre-identified subdivisions of the bag category, such as based on strap length (hand held or shoulder), number of straps (one or two), purpose of bag (for carrying small items, computer, books, etc.).

[0050] Exemplary embodiments may include features for searching and viewing other user profiles. Users can search for and view other user’s profiles. They can also follow or connect to the other user’s profile if they choose to. When viewing profiles, the user may see the other user’s information like name, profile photo, bio, location, university, geographic location, etc. They can also see the items listed on the other user’s profile. These items may include items that the other user has added themselves or items that the other user has duplicated according to embodiments described herein. The system may or may not indicate which items have been added and which ones have been duplicated.

[0051] Exemplary embodiments permit the system to provide recommendations of items to a user. The recommendations may occur during or after a search request, upon logging into the system, such as at an opening page, or at any time, such as through a separate or dedicated portion of the user interface for recommending items. In an exemplary embodiment, the system collects information about a user’s activity on the system. The activity includes viewing items, clicking on items, sharing items, duplicating items, searching, logging in, adding items and more. Information collected during these activities includes attributes of the items like the category, style, color, brand, size, the time of the day, location, type of device the user is using, and more. Users may also be specifically asked information about their demographic information, including, for example, styles they like, their size, brands they prefer

etc. Exemplary embodiments may provide user recommendations based on user specific activities and inputs. Exemplary embodiments may provide user recommendations based on other user inputs and activities. For example, the system may compare the activities across multiple users and determine that if a user prefers Brand A over Brand B, they probably also like Style C. Therefore, the system may provide recommendations based on associations made by the specific user and/or by different users of the system.

[0052] In an exemplary embodiment, information and activities observed about a user may be recorded and parsed according to embodiments described herein. Based on the results of the parsing, a certain score is allocated to the attribute values in the system. For e.g. Color Yellow may have score 0.8 while Color Black may have score 0.2. Similarly, Morning Time might have a score of 0.1 while Evening Time may have score 0.9.

[0053] In an exemplary embodiment, the system may be configured to finds items and outfits that match the attribute values with the highest score. These items are then recommended to the user through a feed at specific times that maximizes the user’s chances of seeing the item and taking an action.

[0054] Exemplary embodiments may also identify a match between users of the system based on the similarity of the attribute scores. ETsers may also be recommended other user’s profiles in their feed so as to maximize the chances of the user viewing the recommended profile and connecting with it.

[0055] In an exemplary embodiment, the system is configured to permit a user to duplicate another user’s items. The system may display an item to a user, including, for example, the item image 52, item description 53, as displayed on a screen of a mobile device 51. The system may permit the user to buy 54 the item or duplicate 55 the item. When a user comes across an item, they may choose to duplicate the item. As shown in FIG. 5, the user can perform this action by simply clicking on a specific button (i.e. the“Relove” button on FIG. 5). As illustrated, the specific button is displayed on the item detail page. The single clicks may be configured to perform the function of duplicating the item to the user’s own page. Once the item has been duplicated, it is added to the user’s profile as if the item was added by them

directly. Other users will then be able to see this item on the user’s profile. It is not necessary for the system to indicate on the user’s profile whether item was added directly or duplicated.

[0056] In exemplary embodiments, a user may build or create outfits or combinations of products from individual items found on the system. Users can build outfits as a group of items that fit well together and/or can be consumed together. FIGS. 6A-6C illustrate an exemplary configuration in which a user can create outfits. The system is configured to display a user interface on a mobile device 61 for adding items and creating an outfit that may be sold as a unit or as individual items. The outfits can be made up of items that have been added by the user themselves or that they have duplicated from other users’ profiles, or items uploaded by other users. Outfits can also be listed on User’s profiles along with items. If an outfit is consumed, the users are compensated in the same way as if the items were all consumed individually. The amount and format of the compensation may vary from system to system.

[0057] Users’ may create copies of other user’s outfits and edit them. For example, User B may copy User A’s outfit containing Items 1 and 2. User B may then add Item 3 to it or replace Item 1 with Item 4. This outfit may be saved as a new outfit and added to User B’s profile. The original outfit created my User A will not be affected by this action. [0058] In exemplary embodiments, a user’s outfit combination may be duplicated by other users. Outfits created by a user are added on their profile and may appear in their feed. Other users may choose to duplicate the entire outfit. This action will then add the outfit to the other user’s profile similar to if they had duplicated a single item.

[0059] FIG. 2D illustrates an exemplary system process that may occur in the back end when an outfit is duplicated. The system may be configured to receive an input from a user to indicate the intent to duplicate an outfit, at step 232. At step 234, the system can retrieve the item identifications for each of the items combined in the outfit. At step 236, each item pulled may look through and duplicated similar to that of FIG. 2B. When an item is reviewed by the system, the system can determine if the item is an original poster or a duplicator, at step 238. If the item is from the originally posted owner, the system may move to the next item. At step 240, the system may be configured to identify the items duplicated as being part of an outfit.

Therefore, the duplicator may be able to repost a replica of the original post to the next user’s profile.

[0060] In an exemplary embodiment, the items in the duplicated outfit are appropriately connected to the user that is duplicating the item. For example, if User A created an outfit containing Item 1, Item 2, Item 3, Item 4 and Item 5, and Item 1 and Item 2 were originally added by User A, Item 3 was added by User B, and Item 4 and Item 5 were added by User C, if User B duplicates the outfit of User A, the system automatically recognizes that Item 3 was originally added by User B. Therefore, if the outfit is consumed from User 2’s profile, User A & User B will be rewarded for the purchase of Item 1 and Item 2, User B and User C will be rewarded for Item 4 and 5. However, only User B may be rewarded for Item 3. [0061] In an exemplary embodiment, an outfit may be automatically updated. For example, if items within an outfit get individually consumed or are no longer available for whatever reason, the system may replace the item with another item that has the best match of attributes as the original item. In case such an item is not available, the system may simply gray out the unavailable item but still leave it within the outfit. As mentioned above, any user may choose to make a copy of the outfit and replace the unavailable item with one of their own.

[0062] In an exemplary embodiment, an outfit may still remain consumable as long as there is a single item within the outfit that is still available to be consumed individually. In an exemplary embodiment, if all the items within an outfit are no longer available, the outfit will no longer be visible on users’ profiles.

[0063] Although the present disclosure and its advantages have been described in detail, it should be understood that various changes, substitutions and alterations can be made herein without departing from the technology of the disclosure as defined by the appended claims. Moreover, the scope of the present application is not intended to be limited to the particular configurations of the process, machine, manufacture, composition of matter, means, methods and steps described in the specification. As one of ordinary skill in the art will readily appreciate from the disclosure, processes, machines, manufacture, compositions of matter, means, methods, or steps, presently existing or later to be developed that perform substantially the same function or achieve substantially the same result as the corresponding configurations described herein may be utilized according to the present disclosure. Accordingly, the appended claims are intended to include within their scope such processes, machines, manufacture, compositions of matter, means, methods, or steps. [0064] Those of skill would further appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the disclosure herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

[0065] The various illustrative logical blocks, modules, and circuits described in connection with the disclosure herein may be implemented or performed with a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0066] The steps of a method or algorithm described in connection with the disclosure may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in RAM, flash memory, ROM, EPROM, EEPROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium. In addition and/or the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal. In the alternative, the processor and the storage medium may reside as discrete components in a user terminal.

[0067] In one or more exemplary designs, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a general purpose or special purpose computer. By way of example, and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store specified program code means in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk and disc, as used herein, includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer- readable media.

[0068] The description of the disclosure is provided to enable any person skilled in the art to make or use the disclosure. Various modifications to the disclosure will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other variations without departing from the spirit or scope of the disclosure. Thus, the disclosure is not intended to be limited to the examples and designs described herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

[0069] Although several embodiments have been described in detail for purposes of illustration, various modifications may be made without departing from the scope and spirit of the present disclosure. Accordingly, the disclosure is not to be limited by the examples presented herein, but is envisioned as encompassing the scope described in the appended claims and the full range of equivalents of the appended claims.

Claims

Claims:

1. A system, comprising:

one or more processors;

memory;

machine readable instructions stored in memory that when executed by the one or more processors is configured to:

receive an input from a user to indicate an intent to duplicate information on a

website or application;

copying the information;

storing the information in a database;

associating the information with the user that indicated the intent to duplicate.

2. The system of claim 1, wherein the machine readable instructions are additionally

configured to store a user identification of the user that indicated the intent to duplicate.

3. The system of claim 1, wherein the machine readable instructions are additionally

configured to store a user identification of a user that originally posted the information.

4. The system of claim 1, wherein the system is configured to permit an action to be

performed regarding the information.

5. The system of claim 4, wherein the action considers the user identification of the user that indicated the intent to duplicate and the user identification of the user that originally posted the information.

6. A method, comprising:

displaying information in an electronic format through a display user interface; receiving an indication from a user to duplicate the information;

copying the information;

redisplaying the information on a page associated with the user.

7. A system, comprising:

one or more processors;

memory;

receive an action from a user;

generate an attribute score based on the action from the user;

return items to display based on the attribute score.

8. The system of claim 7, wherein the machine readable instructions are further configured to update the attribute score based on another action from the user.

9. The system of claim 8, wherein the action from the user comprises entering preferences into the system.

10. The system of claim 8, wherein the another action comprises, searching, viewing,

selecting, purchasing, duplicating, and combinations thereof.

11. The system of claim 8, wherein attribute score is updated based on a lapse of time from a previous action from the user.

12. The system of claim 8 wherein the system is further configured to receive an input from a user to duplicate information from a page on the system and the system copies the information to another page associated with the user.

13. A method, comprising:

displaying a user interface to a user on an electronic display;

receiving an action from the user through the user interface;

generating an attribute score based on the action from the user;

returning items to display through the user interface based on the attribute score.

14. The method of claim 13 further comprising receiving a second action from the user and updating the attribute score based on the second action.