Re: [arr] songs database
My responses inline. --- In arrahmanfans@yahoogroups.com, Indmov Buff wrote: /* This may be a very silly question - can we add tags to each entry? For eg , names of singers etc are sometimes spelt in different ways.In order to cover all the variations, should we add tags? */ Yes can. Perhaps have it comma separated or have a additional column. /* Also , would it help to add the Raaga of each song. I am sure there are songs which have more than one raaga. presumably they are separated by a comma? */ Ragas can be comma separated as of now. /* And how do we want to export this database to the group? Is the only solution to host it external to the group? or could we somehow attach it to the group? Sorry about the stupid questions. */ The idea is to develope a page/application like Roshan did which would help us search all the details we need. The page or application would demand bit of thinking to do. But, as a first step we would need the data to be represented in some format which the guys the working on. Once the song details are complete, we ca start working on the application. Changing or adding data to the database is not a difficult task anyways. /* Could we also add a column for the musicians who worked on each album? and sound engineer as well. Try and capture all the data on the cd perhaps? but this might be going overboard. No harm adding a column I guess. Should Genre have a subdivision to say what the song is predominantly about? patriotic, mother, wedding song etc? */ Yes definitely. We can add a column as sound engineer. Please feel free to add columns with related info. Target is to have all the details on CD. But its a tough target to think of right now. To get started we can first start with song list with a few basic details. As said earlier, rest of the details can be added later on as they come. Thank you for your suggestions Thanks for this Roshan. Great start. I think before people start entering data > into this, we should decide on whether more columns/data are required and > agree > on it collectively? Just a suggestion. > > > > > From: Roshan > To: arrahmanfans@yahoogroups.com > Sent: Tue, 24 August, 2010 0:48:33 > Subject: [arr] songs database > > > Thank you everyone who took the time to compile the list for the db. > > > i have just created a form to collect the data directly to MySQL. so that > exporting it to any db would be easier. > > http://sandbox.roshanravi.com/arrdb/use/ARRahmanDatabase/form1.html > > i will be adding in teh album names from the excel file we have when i get a > chance, but if you want to add something by yourself, please feel free.. > > > > it is just using a form generator. the only goal is to collect the data. > > > these are the updated fields for Album. yet to do the songs db section. > > > Film Or Album Language Dubbed Year of Movie Release Year of Audio Release > Genre > Audio Company Actors director Movie Genre Awards Won for music Awards > Nominated > for music AWards won for movie awards nominated for movie Other notes > > > > -- > --- > http://roshanravi.com > http://ramblingsoul.com > http://cssheaven.org >
Re: [arr] songs database
Hi Gops, If we do have most of the information, then please share the same in any format. A scalable design is possible, but i am afraid it can be bit complicated for us to start enetering the data with it. We can come up with a ER diagram for the same, but it can be diffcult for us enter the data to it. IMO, as a first step if we have the details of songs as a excel sheet prepared by murugan, then we can easily import the same into a scalable DB design ( I can help on that ). Importing the data from the basic excel to a complicated database design cn be performed easily thro ETL tools and bit of querying and data massaging. Regards, S.V.Nagaraj --- In arrahmanfans@yahoogroups.com, Gopal Srinivasan wrote: > > Thanks to everyone that agreed to participate. The enthusiasm to get things > rolling is encouraging. However, I would caution against adhoc development. > Between ourselves, we have 90%-95% of the data we need. So, that need not be > the focus. In my view, the focus needs to be on designing a database that is > robust and extensible in design. It should allow for backend storage and > front end ingestion and retrieval of data. Extensibility is particularly > important because there may be views of data that we don't conceive now but > will be come apparent in future. A relational database schema seems like the > best approach to take. Let me illustrate that with an example - in some > cases you have credits for musicians for a song and in many cases only for > an entire album. This is true for awards too. The only way this can be > handled is through relational databases with well thought-through > entity-relationships. I would therefore request that let our initial focus > be on defining what kind of information are we seeking to archive and then > design the database before getting down to implementation. Populating it > with data is a relatively trivial task. Suggestions welcome. > > On Mon, Aug 23, 2010 at 19:48, Roshan wrote: > > > > > > > Thank you everyone who took the time to compile the list for the db. > > > > > > i have just created a form to collect the data directly to MySQL. so that > > exporting it to any db would be easier. > > > > http://sandbox.roshanravi.com/arrdb/use/ARRahmanDatabase/form1.html > > > > i will be adding in teh album names from the excel file we have when i get > > a chance, but if you want to add something by yourself, please feel free.. > > > > > > it is just using a form generator. the only goal is to collect the data. > > > > > > these are the updated fields for Album. yet to do the songs db section. > > > > *Film Or Album* *Language**Dubbed**Year of Movie Release* *Year of Audio > > Release**Genre**Audio Company* *Actors**director **Movie Genre**Awards Won > > for music* *Awards Nominated for music**AWards won for movie**awards > > nominated for movie* *Other notes* > > > > > > -- > > --- > > http://roshanravi.com > > http://ramblingsoul.com > > http://cssheaven.org > > > > > > >
Re: [arr] songs database
Thanks for your input. but we are not there yet. hosting, applications etc will come only at a later stage if we decide to provide such a thing. this first step is to get the data in one place and later we can decide whether we want a searchable db application or facebook application etc. On Tue, Aug 24, 2010 at 9:49 PM, userind wrote: > > > My suggestion. > > Decide on the best Hosting Platform before starting to design the whole > applicationFor example, if the application is going to be deployed on a > cloud hosting platform like the Google App Engine, the typical DB ER design > becomes irrelevant. Also bear in mind the hosting providers restrictions, > like DB restritions based on the package/solutions offered. > > -- --- http://roshanravi.com http://ramblingsoul.com http://cssheaven.org
Re: [arr] songs database
I agree, Gopal. The idea of having an excel sheet was to get all the columns (fields) in place. Then we can have it normalize it further if required and convert it into a db. Warm Regards ~~~ Vinayak http://www.flickr.com/photos/rightplacerighttime/ On Tue, Aug 24, 2010 at 7:55 PM, Gopal Srinivasan wrote: > > > Thanks to everyone that agreed to participate. The enthusiasm to get things > rolling is encouraging. However, I would caution against adhoc development. > Between ourselves, we have 90%-95% of the data we need. So, that need not be > the focus. In my view, the focus needs to be on designing a database that is > robust and extensible in design. It should allow for backend storage and > front end ingestion and retrieval of data. Extensibility is particularly > important because there may be views of data that we don't conceive now but > will be come apparent in future. A relational database schema seems like the > best approach to take. Let me illustrate that with an example - in some > cases you have credits for musicians for a song and in many cases only for > an entire album. This is true for awards too. The only way this can be > handled is through relational databases with well thought-through > entity-relationships. I would therefore request that let our initial focus > be on defining what kind of information are we seeking to archive and then > design the database before getting down to implementation. Populating it > with data is a relatively trivial task. Suggestions welcome. > > On Mon, Aug 23, 2010 at 19:48, Roshan wrote: > >> >> >> Thank you everyone who took the time to compile the list for the db. >> >> >> i have just created a form to collect the data directly to MySQL. so that >> exporting it to any db would be easier. >> >> http://sandbox.roshanravi.com/arrdb/use/ARRahmanDatabase/form1.html >> >> i will be adding in teh album names from the excel file we have when i get >> a chance, but if you want to add something by yourself, please feel free.. >> >> >> it is just using a form generator. the only goal is to collect the data. >> >> >> these are the updated fields for Album. yet to do the songs db section. >> >> *Film Or Album* *Language**Dubbed**Year of Movie Release* *Year of Audio >> Release**Genre**Audio Company* *Actors**director **Movie Genre**Awards >> Won for music* *Awards Nominated for music**AWards won for movie**awards >> nominated for movie* *Other notes* >> >> >> -- >> --- >> http://roshanravi.com >> http://ramblingsoul.com >> http://cssheaven.org >> >> > >
Re: [arr] songs database
My suggestion. Decide on the best Hosting Platform before starting to design the whole applicationFor example, if the application is going to be deployed on a cloud hosting platform like the Google App Engine, the typical DB ER design becomes irrelevant. Also bear in mind the hosting providers restrictions, like DB restritions based on the package/solutions offered.
Re: [arr] songs database
thanks gops I agree. we need to decide on types of information and fields before even putting them in a db. and we will start using the fields from Vinayak's format as a start. and we can add the columns later. On Tue, Aug 24, 2010 at 7:55 PM, Gopal Srinivasan wrote: > > > Thanks to everyone that agreed to participate. The enthusiasm to get things > rolling is encouraging. However, I would caution against adhoc development. > Between ourselves, we have 90%-95% of the data we need. So, that need not be > the focus. In my view, the focus needs to be on designing a database that is > robust and extensible in design. It should allow for backend storage and > front end ingestion and retrieval of data. Extensibility is particularly > important because there may be views of data that we don't conceive now but > will be come apparent in future. A relational database schema seems like the > best approach to take. Let me illustrate that with an example - in some > cases you have credits for musicians for a song and in many cases only for > an entire album. This is true for awards too. The only way this can be > handled is through relational databases with well thought-through > entity-relationships. I would therefore request that let our initial focus > be on defining what kind of information are we seeking to archive and then > design the database before getting down to implementation. Populating it > with data is a relatively trivial task. Suggestions welcome. > > On Mon, Aug 23, 2010 at 19:48, Roshan wrote: > >> >> >> Thank you everyone who took the time to compile the list for the db. >> >> >> i have just created a form to collect the data directly to MySQL. so that >> exporting it to any db would be easier. >> >> http://sandbox.roshanravi.com/arrdb/use/ARRahmanDatabase/form1.html >> >> i will be adding in teh album names from the excel file we have when i get >> a chance, but if you want to add something by yourself, please feel free.. >> >> >> it is just using a form generator. the only goal is to collect the data. >> >> >> these are the updated fields for Album. yet to do the songs db section. >> >> *Film Or Album* *Language**Dubbed**Year of Movie Release* *Year of Audio >> Release**Genre**Audio Company* *Actors**director **Movie Genre**Awards >> Won for music* *Awards Nominated for music**AWards won for movie**awards >> nominated for movie* *Other notes* >> >> >> -- >> --- >> http://roshanravi.com >> http://ramblingsoul.com >> http://cssheaven.org >> >> > > -- --- http://roshanravi.com http://ramblingsoul.com http://cssheaven.org
Re: [arr] songs database
I agree fully! I think, we need to think about what we want out of this with the future in mind. More of a brain storming session to have a framework of the database we want/need. I also think that we should try and keep these e-mails separate to the group mail until a framework is finalised in order to help focus on the issues. From: Gopal Srinivasan To: arrahmanfans@yahoogroups.com Sent: Tue, 24 August, 2010 15:25:50 Subject: Re: [arr] songs database Thanks to everyone that agreed to participate. The enthusiasm to get things rolling is encouraging. However, I would caution against adhoc development. Between ourselves, we have 90%-95% of the data we need. So, that need not be the focus. In my view, the focus needs to be on designing a database that is robust and extensible in design. It should allow for backend storage and front end ingestion and retrieval of data. Extensibility is particularly important because there may be views of data that we don't conceive now but will be come apparent in future. A relational database schema seems like the best approach to take. Let me illustrate that with an example - in some cases you have credits for musicians for a song and in many cases only for an entire album. This is true for awards too. The only way this can be handled is through relational databases with well thought-through entity-relationships. I would therefore request that let our initial focus be on defining what kind of information are we seeking to archive and then design the database before getting down to implementation. Populating it with data is a relatively trivial task. Suggestions welcome. On Mon, Aug 23, 2010 at 19:48, Roshan wrote: >Thank you everyone who took the time to compile the list for the db. > > >i have just created a form to collect the data directly to MySQL. so that >exporting it to any db would be easier. > >http://sandbox.roshanravi.com/arrdb/use/ARRahmanDatabase/form1.html > >i will be adding in teh album names from the excel file we have when i get a >chance, but if you want to add something by yourself, please feel free.. > > > >it is just using a form generator. the only goal is to collect the data. > > >these are the updated fields for Album. yet to do the songs db section. > > >Film Or Album Language Dubbed Year of Movie Release Year of Audio Release >Genre >Audio Company Actors director Movie Genre Awards Won for music Awards >Nominated >for music AWards won for movie awards nominated for movie Other notes > > > >-- >--- >http://roshanravi.com >http://ramblingsoul.com >http://cssheaven.org > >
Re: [arr] songs database
Thanks to everyone that agreed to participate. The enthusiasm to get things rolling is encouraging. However, I would caution against adhoc development. Between ourselves, we have 90%-95% of the data we need. So, that need not be the focus. In my view, the focus needs to be on designing a database that is robust and extensible in design. It should allow for backend storage and front end ingestion and retrieval of data. Extensibility is particularly important because there may be views of data that we don't conceive now but will be come apparent in future. A relational database schema seems like the best approach to take. Let me illustrate that with an example - in some cases you have credits for musicians for a song and in many cases only for an entire album. This is true for awards too. The only way this can be handled is through relational databases with well thought-through entity-relationships. I would therefore request that let our initial focus be on defining what kind of information are we seeking to archive and then design the database before getting down to implementation. Populating it with data is a relatively trivial task. Suggestions welcome. On Mon, Aug 23, 2010 at 19:48, Roshan wrote: > > > Thank you everyone who took the time to compile the list for the db. > > > i have just created a form to collect the data directly to MySQL. so that > exporting it to any db would be easier. > > http://sandbox.roshanravi.com/arrdb/use/ARRahmanDatabase/form1.html > > i will be adding in teh album names from the excel file we have when i get > a chance, but if you want to add something by yourself, please feel free.. > > > it is just using a form generator. the only goal is to collect the data. > > > these are the updated fields for Album. yet to do the songs db section. > > *Film Or Album* *Language**Dubbed**Year of Movie Release* *Year of Audio > Release**Genre**Audio Company* *Actors**director **Movie Genre**Awards Won > for music* *Awards Nominated for music**AWards won for movie**awards > nominated for movie* *Other notes* > > > -- > --- > http://roshanravi.com > http://ramblingsoul.com > http://cssheaven.org > > >
Re: [arr] songs database
ok.. sorry guys. i think there is something wrong with the forms. i honestly didn't test it. i was in a rush and generated theform with phpformgen.. and assumed that it would work. Vinayak, I agree. i think the best way still is to import using csv, that way everything is refined and perfect before we actually put it in a db. I wlll redo the form though.. just in case if any of you think that it will be good and easy to do taht way.. i will add the song duration and tags as well.. lets do it. :) On Tue, Aug 24, 2010 at 2:43 PM, Indmov Buff wrote: > > > This may be a very silly question - can we add tags to each entry? For eg , > names of singers etc are sometimes spelt in different ways.In order to cover > all the variations, should we add tags? Also , would it help to add the > Raaga of each song. I am sure there are songs which have more than one > raaga. presumably they are separated by a comma? And how do we want to > export this database to the group? Is the only solution to host it external > to the group? or could we somehow attach it to the group? Sorry about the > stupid questions. Could we also add a column for the musicians who worked on > each album? and sound engineer as well. Try and capture all the data on the > cd perhaps? but this might be going overboard. No harm adding a column I > guess. Should Genre have a subdivision to say what the song is predominantly > about? patriotic, mother, wedding song etc? > Thanks for this Roshan. Great start. I think before people > start entering data into this, we should decide on whether more columns/data > are required and agree on it collectively? Just a suggestion. > > -- > *From:* Roshan > *To:* arrahmanfans@yahoogroups.com > *Sent:* Tue, 24 August, 2010 0:48:33 > *Subject:* [arr] songs database > > > > Thank you everyone who took the time to compile the list for the db. > > > i have just created a form to collect the data directly to MySQL. so that > exporting it to any db would be easier. > > http://sandbox.roshanravi.com/arrdb/use/ARRahmanDatabase/form1.html > > i will be adding in teh album names from the excel file we have when i get > a chance, but if you want to add something by yourself, please feel free.. > > > it is just using a form generator. the only goal is to collect the data. > > > these are the updated fields for Album. yet to do the songs db section. > > *Film Or Album* *Language**Dubbed**Year of Movie Release* *Year of Audio > Release**Genre**Audio Company* *Actors**director **Movie Genre**Awards Won > for music* *Awards Nominated for music**AWards won for movie**awards > nominated for movie* *Other notes* > > > -- > --- > http://roshanravi.com > http://ramblingsoul.com > http://cssheaven.org > > > > -- --- http://roshanravi.com http://ramblingsoul.com http://cssheaven.org
Re: [arr] songs database
This may be a very silly question - can we add tags to each entry? For eg , names of singers etc are sometimes spelt in different ways.In order to cover all the variations, should we add tags? Also , would it help to add the Raaga of each song. I am sure there are songs which have more than one raaga. presumably they are separated by a comma? And how do we want to export this database to the group? Is the only solution to host it external to the group? or could we somehow attach it to the group? Sorry about the stupid questions. Could we also add a column for the musicians who worked on each album? and sound engineer as well. Try and capture all the data on the cd perhaps? but this might be going overboard. No harm adding a column I guess. Should Genre have a subdivision to say what the song is predominantly about? patriotic, mother, wedding song etc? Thanks for this Roshan. Great start. I think before people start entering data into this, we should decide on whether more columns/data are required and agree on it collectively? Just a suggestion. From: Roshan To: arrahmanfans@yahoogroups.com Sent: Tue, 24 August, 2010 0:48:33 Subject: [arr] songs database Thank you everyone who took the time to compile the list for the db. i have just created a form to collect the data directly to MySQL. so that exporting it to any db would be easier. http://sandbox.roshanravi.com/arrdb/use/ARRahmanDatabase/form1.html i will be adding in teh album names from the excel file we have when i get a chance, but if you want to add something by yourself, please feel free.. it is just using a form generator. the only goal is to collect the data. these are the updated fields for Album. yet to do the songs db section. Film Or Album Language Dubbed Year of Movie Release Year of Audio Release Genre Audio Company Actors director Movie Genre Awards Won for music Awards Nominated for music AWards won for movie awards nominated for movie Other notes -- --- http://roshanravi.com http://ramblingsoul.com http://cssheaven.org
Re: [arr] songs database
Dear Guys, Great going.. I have a suggestion, make actor and actresses separate, so that any body can search which actor/actress work in which Rahman movie. ARR Rulez Rakesh --- On Mon, 8/23/10, Roshan wrote: From: Roshan Subject: [arr] songs database To: arrahmanfans@yahoogroups.com Date: Monday, August 23, 2010, 4:48 PM Thank you everyone who took the time to compile the list for the db. i have just created a form to collect the data directly to MySQL. so that exporting it to any db would be easier. http://sandbox.roshanravi.com/arrdb/use/ARRahmanDatabase/form1.html i will be adding in teh album names from the excel file we have when i get a chance, but if you want to add something by yourself, please feel free.. it is just using a form generator. the only goal is to collect the data. these are the updated fields for Album. yet to do the songs db section. Film Or Album LanguageDubbedYear of Movie Release Year of Audio ReleaseGenreAudio Company Actorsdirector Movie GenreAwards Won for music Awards Nominated for musicAWards won for movieawards nominated for movie Other notes -- --- http://roshanravi.com http://ramblingsoul.com http://cssheaven.org
[arr] songs database
Thank you everyone who took the time to compile the list for the db. i have just created a form to collect the data directly to MySQL. so that exporting it to any db would be easier. http://sandbox.roshanravi.com/arrdb/use/ARRahmanDatabase/form1.html i will be adding in teh album names from the excel file we have when i get a chance, but if you want to add something by yourself, please feel free.. it is just using a form generator. the only goal is to collect the data. these are the updated fields for Album. yet to do the songs db section. *Film Or Album**Language**Dubbed**Year of Movie Release**Year of Audio Release**Genre**Audio Company**Actors**director **Movie Genre**Awards Won for music**Awards Nominated for music**AWards won for movie**awards nominated for movie**Other notes* -- --- http://roshanravi.com http://ramblingsoul.com http://cssheaven.org
