requirementsFans
#Software requirements - Fan view
The fan wants to listen to music, watch music clips,...
Anyway Metalcon should be beginner-friendly, meaning when a new user enters the site, he already finds some information, can be defaults or data collected by Metalcon earlier. (e.g. via like button)
In addition a fan may be interested to keep the bands he subscribed to in other social networks before. By connecting accounts of other services with Metalcon, it could be able to recreate the subscriptions to bands that also connected their profile of this specific service.
Some users may like it to connect their metalcon profile to other services, e.g. last-fm scrobblers to show other users their recent played tracks or all-time favourites.
Metalcon should bring users together. Fans should be able to find other fans with similiar preferences.
##Information retrieval When a user comes to Metalcon, he wants to get relevant information about his social surroundings. User may want to control the relenvance mechanism parameters used.
By social surroundings we mean:
- friends (friends of friends)
- records
- bands subscribed to
- venues (visited, matching music, friends visiting, local, bands)
- City (Region) the user lives in or is otherwise interested in
- genre? (explicit / implicit)
By Information we mean distinguish formats and types of information:
type of information There is information automatically supplied by Metalcon, but the user can configure it to his likes.
- a friend adds a person to his friend list (?)
- a friend likes/subscribes to a band
- a friend visits a venue
- a band is going to play at a venue
- a venue addes a band to their line up
- new record of favourite bands are released
- concert of favourite bands
- concerts in own geographical location
- which friends go to a concert
- Reviews of records
- ... many more which all come done to entity of an entity in our metalcon social graph (BFS 2).
formats
- text
- photos
- music (embedded player)
- videos (embedded player)
- links
- any semantic markup...
The interface should support the user by detecting the specific type of information given.
For the user it is very important that he doesn't get too much information from entities and people he is not really interested in. Therefore we need a good measure of relevance.
The user may want to actively look for (new) music (and other content like friends, venues,...) as well as getting recommendations based on his preferences.
The user should be able to express himself and be able to provide information he wants to share with others. In addition to that, this data could be used to aggregate new recommendations.
- concert history
- record collection (!)
- photos (of concerts / festivals) including metadata
- thoughts
- parties / disco evening
- played instruments
- music preferences
- venues he likes/visited
- home address
- age
- philosophy
User wants to be able to find other people, bands, venues. They may want to filter by different criteria such as age, gender, taste of music, address, aso.
Users want to be able to purchase merchandise from favorite bands. Includes tickets, CDs, Shirts, MP3s, aso.
Maybe the users would like to be entertained by the platform in a way that makes using it feel like playing a game. There could for example be some statistics which can be compared among users, making them aim for a high score. Score could be earned by delivering (selfmade) content or certain social activities. (If you need other concrete examples of what could be done, ask Rene! He seems to be very creative in these matters)