When looking for ways to improve time management while scheduling the most effective music log, it’s often best to get down to the basics. This is especially true when developing and or refining your music-scheduling database. The best practices include asking the following questions: The first is whether the database was initially cloned from another station with the same format. Secondly whether the database transferred hands from another program director or third whether the database was created from scratch. These three different scenarios will make a huge difference in troubleshooting or modifying the structure of your station’s music library. You’d be surprised at the number of programmers and consultants who refuse to pay this type of close attention to detail or simply don’t realized the importance of every song’s individual attribute and how these small pieces are part of the bigger picture… a precisely generated music log.
Getting back to the basics can often mean going through the database library with fresh eyes to determine if there are any errors or redundancies. This is especially true if you’re working with a cloned database, or a database that you didn’t create yourself. Songs may have been incorrectly coded with specific characteristic rule codes and important descriptive settings. A database is only as good as the accuracy of the information held within it, so basic data verification is of paramount importance. No two people will describe the basic five attributes of a song in the same manner. For more information about database maintenance contact Earl Boston Inc.