Fashion Lab

From Zanecorpwiki

The social wardrobe?

Contents 1 Buckshot Overview 2 Things to Do 3 Future 4 Notes

Buckshot Overview

• Post pictures of outfits.
• Organize into Galleries. Galleries can contain galleries.
• Galleries and individual picks can be: Public, Friends of Friends, Friends, Trusted Friends, Private. Permissions can only get more restrictive.^{[notes 1]}
• Mark favorites, self, friends, and public.
• Full semantic tagging.
• Images, galleries, comments, and users can be tagged.
• Tagged images, galleries, and comments are automatically orchestrated into virtual galleries.
  • Design wise, virtual galleries are a type of gallery. The interface between the two is very similar.
  • The comments are not explicitly tagged, but "inherit" the tag of the gallery which the user was viewing when the comment was made.
• A photo can only ever in one gallery. (But multiple photos of the same thing can be in separate galleries.)
• For each user, there are two special galleries: 'outfits' and 'items'. All other images or galleries are organized under these.
• When a user signs up, they are asked whether they want "only physical galleries", "only virtual galleries", or both, if they do custom setup. Only one (best strictly virtual?) if they use 'automatic' setup. The choice can be changed at any time and only effects interface, not actual data layout.^{[notes 2]}
• "Thing to Do." Page of stuff to do. Comes with pre-populated defaults and link to "ideas"--which are things to do which can be added to your list of things to do. Each user can manage their own list though.
• Images and galleries can be tagged with 'to do tags' from the "Things to Do" list.
• Each user's home page has the following sections:
  • favorites
  • galleries
  • virtual galleries
  • things to do
• Each section can be made Public through Private
• There are essentially three interface types page: user view, gallery view, and image view. (Items and outfits are captured as images.) Each interface has navigation and controls. All "things" on the site which are accessible are navigable.^{[notes 3]}

Things to Do

• "Outfits I want to improve."
• "Outfits I want to bite." (imitate?)
• "Items I want to replace."
• "Items I want to use more."
• "Items I want to share."
• "Items I want to set free."^{[notes 4]}

Future

Currently only a single permission 'view and comment' permission. Groups are also limited and pre-defined. There's the self, the manual group friends, and the dynamic groups friends of friends and trusted friends. This is compatible with our standard authorization model (need link), but some new features in this area might be appreciated.

• Manually managed groups or clubs?
• Separate the view and comment permissions.^{[notes 5]}
• Allow write/manage access.

Fashion wiki?

Killer: turn browsing into guided browsing. Analyze user and promote links in sets. E.g., the favorites section on a page will highlight stuff that is not only favorite, but which the system thinks you'll especially like. E.g. (x2... sigh), if you have 100 "celebrity faves", it could try to figure out through trusted friends and comparing your taste preferences against semantic tags to determine which ones of the 100 outfits you're likely to like the most.

Next step: spot trend setters and the leading edge. Who are the people that consistently "get there" before everyone else. $$$

• excellent how-to on tying ties; just wish it had a few more styles

Notes

1. ↑ The problem with liberalizing restrictions centers on navigation. What's the expectation when a "Public" image is in a "Private" gallery? It's technically solvable, but the expectation isn't clear. This leads to the conclusion that the restriction reduces confusion, frustration, and most importantly errors the confusion can lead to. Meaning, whatever model we adopt would seem idiomatic, and not understanding the idiom, the user may make choices which unintentionally lead to information being published in a way that wasn't intended. "Doing what the customer intends" is much more important than maximal freedom to "do whatever".
2. ↑ Since virtual and real galleries are orthogonal, there should be no need to reorganize the underlying data when the interaction preferences are changed. In other words, the change is just in the UI. If physical galleries are active, then you see them and can navigate them. Virtual galleries ignore physical galleries so the navigation on that side is independent.
3. ↑ The point being that while we will have search functionality, you browse to anything which you can see. We want to make exploration and connections happen.
4. ↑ Items for sale or trade. This one will require a sub-system tie in so isn't a pure tag based implementation.
5. ↑ I would think most useful to express letting one group view and a sub-group comment. How to deal with allowing groups to comment but not view? Okay technically, but should warn user since the intent is not clear and they're probably confused.