Lecture Post: Databases

This product enables users to find and compile the best quality videos of live performances from their favorite  artists. The company functions in cooperation with video sites such as YouTube and Vimeo to bring consumers the very best in live music recordings and presents them in an organized playlist.

This music application would require a database to store and organize data concerning finances, user demographics (for marketing purposes,) music and producer profile information, etc. A database would be helpful, as opposed to a file sharing system, so that everybody involved could have access to the same, non-redundant data. 
Examples of organization for the database include files such as live videos, blogs, music videos, interviews, with numerically sorted records of each piece of media, and field names for each such as artist, venue, time, producer/director, video quality, format, etc. This hierarchical organization in the database would not only help those running and organizing the site to easily store and retrieve the required pieces of data, it would also allow the company to keep valid and accurate records of all the media they own and distribute.
It would be important for this company to well-maintain their database, to ensure users and workers are working with the most up to date pieces of information available and no space in the database is wasted. When working from multiple locations like this company would, we would need to keep our data concerning finances, media, user demographics and preferences, etc. condensed yet up to date. Labels would need to keep artist profiles up to date, improving video quality availability would push to continuously update videos, and many other examples. It would also be important to run checks on the data through the database to ensure there are no redundancies, logical errors or formatting errors in the data.