Ticket #540 (Closed: fixed)

Browsing a station's files is different than using a search mechanism, because frequently a user may not know the search terms to look for. A browsing mechanism should therefore harness the power of the metadata the system collects, and allow users several powerful methods to choose files and playlists to work with. The model and mechanism for file browsing would be similar to how iTunes handles its browsing, but with extensions for information relevant to radio broadcasting. A screenshot of iTunes is enclosed. Two separate browsing window would allow users to search for either music or reports; only one browsing window could be open at a time. ADDITIONAL INFORMATION: In the browsing interface, five fields would be displayed as columns, with the default choice set to "all" in for all columns. When "all" is selected, all values in a field are displayed in the columns, as well as in the individual file list below. Selecting a value limits the files displayed in both the columns to the right as well as in the file list below, according to the value the user selects. For example, if a user selects the 'Date' field for 'January 5, 2005', only files and categories with that date value would be displayed. Selecting an item from the 'program' column would limit the choices further, displaying only files from the chosen program on Jan. 5, 2005. There will be two browsing windows, each showing fields relevant to their content type; the "music browse" window would use the 'BPM', 'Genre', 'Artist', 'Album' and 'Rating' columns. The "report browse" window would be oriented to news and talk shows, and would use the 'Coverage' (Date/Time as default, but with option to choose 'Coverage.Geographic' or 'Coverage.Entity' as well in a pulldown), 'Program', 'Subject Keywords', 'Type', 'Creator' and 'Rating' columns.