Music Charting pages

Funny story, I just finished talking with my music director about how to do charting through our site as well.
I also just finished writing a module to extend the station_playlist module, allowing playlists to denote whether a track is "new" or not, and hope to continue extending that module's functionality, at least until CCK 6.x-3.x is widely adopted and used by station.

This is my big project right now, I'll update this with what I've got as I progress.

http://github.com/timplunkett/Station-Playlist-Extender

Full CMJ charting is my final goal.
"New" implies that its in our rotation.
Genre was my next step.
And if you use views, you can sort by Node: Post date.

tim.plunkett, why do you have the views boolean views handler? it looks like you're just duplicating the one that views ships. am i missing something?

the one thing i've wanted to do for a while is if the catalog is enabled have a catalog number field that if you put in the catalog number it auto fills the artist/album/label fields. this would make the reporting for logged albums much easier.

I added another display option, 'New' or ''.
I gave up on figuring out how to extend a handler, so I just copied that one.

i think there's a bug in the current playlist views code. trying to add a relationship from a station_playlist_track based view to the playlist node results in the following error:
user warning: Unknown column 'station_playlist_track.iid' in 'field list' query: SELECT station_playlist_track.iid AS iid, station_playlist_track.album AS station_playlist_track_album, station_playlist_track.artist AS station_playlist_track_artist, station_playlist_track.title AS station_playlist_track_title FROM station_playlist_track station_playlist_track INNER JOIN node node_station_playlist_track ON station_playlist_track.nid = node_station_playlist_track.nid LIMIT 0, 10 in /Users/amorton/Sites/d6/sites/all/modules/views/includes/view.inc on line 731.

oh right i'm remembering this now. views won't join tables on a composite key (nid/delta in this case) so i had started to add a new column to the table that was a serial value just for use as the primary key for view's purposes.

i also wanted to drop a link to #181883: Playlist Statistics which was some old code i'd done for kpsu for a similar purpose.

tim.plunkett, for the views bool handler you should really look at making the true/false value configurable and submitting it back as a patch. i've struggled with that several times so i'm sure it would be useful for others as well.

re: #6
yes, that would be cool. except WKDU doesn't use the catalog number the same way you do, so not immediately helpful.
the idea i had was that if you've already entered the artist, restrict the album autocomplete to albums by that artist, and vice versa

re: #8-9
so, that's an error due to code that's a WIP? are you on top of that or should i try and figure it out?

re: #10
that is a fantastic idea. i will look into that, we'll see how i do.

Oops, forgot to mention the code I added to my template.php file:

function THEMENAME_station_playlist_track_form($form) {
  $header = array('', t('Artist'), t('Title'), t('Album'), t('Label'), t('Link'), t('New track'), t('Weight'));

  $rows = array();
  foreach (element_children($form) as $key) {
    $row = array();
    $row[] = '';
    $row[] = drupal_render($form[$key]['artist']);
    $row[] = drupal_render($form[$key]['title']);
    $row[] = drupal_render($form[$key]['album']);
    $row[] = drupal_render($form[$key]['label']);
    $row[] = drupal_render($form[$key]['link']);
    $row[] = drupal_render($form[$key]['newtrack']);
    $form[$key]['weight']['#attributes']['class'] = 'track-weight';
    $row[] = drupal_render($form[$key]['weight']);
    $rows[] = array('data' => $row, 'class' => 'draggable');
  }

  $output = '';
  if (count($rows)) {
    drupal_add_tabledrag('station-playlist-tracks', 'order', 'sibling', 'track-weight');
    $output .= theme('table', $header, $rows, array('id' => 'station-playlist-tracks'));
  }

  return $output . drupal_render($form);
}

That should do the trick. Obviously replace THEMENAME with your... theme's name.

Well, maybe.
Its just after midnight for me, so I won't be up for testing it out more until tomorrow.
At which time I will also try out your code and see if I can get a view working nicely.

Regarding #15 refreshingapathy See attached patch to the module... there are 3 easy edits if i remember correctly

The station playlist as of Dev 6.x uses
$form['tracks_wrapper']['tracks'][$weight]

where the GIT code uses the form_alter as
$form['tracks'][$weight]

There was also a modification to line 17
$blanks= 0;

inserting a from_alter version into templates.php makes the checkboxes appear below the track listings. For some reason, a drupal expert could explain, you must edit the station/playlist/station_playlist.modue starting at line 345

function theme_station_playlist_track_form($form) {
  // To have the drag and drop not totally wack out the formatting we need
  // the first column in the table with no form element.
  $header = array('', 'New', t('Artist'), t('Title'), t('Album'), t('Label'), t('Link'), t('Weight'), '');
  $rows = array();
  foreach (element_children($form['tracks']) as $key) {
    $form['tracks'][$key]['weight']['#attributes']['class'] = 'track-weight';
    $row = array(
      '',
      drupal_render($form['tracks'][$key]['newtrack']),
      drupal_render($form['tracks'][$key]['artist']),
      drupal_render($form['tracks'][$key]['title']),
      drupal_render($form['tracks'][$key]['album']),
      drupal_render($form['tracks'][$key]['label']),
      drupal_render($form['tracks'][$key]['link']),
      drupal_render($form['tracks'][$key]['weight']),
      drupal_render($form['tracks'][$key]['remove']),
    );
    $rows[] = array('data' => $row, 'class' => 'draggable');
  }

  $output = '';
  if (count($rows)) {
    drupal_add_tabledrag('station-playlist-tracks-table', 'order', 'sibling', 'track-weight');
    $output .= theme('table', $header, $rows, array('id' => 'station-playlist-tracks-table'));
  }

  return $output . drupal_render($form);
}

you may notice the station-playlist-tracks-table reference as being the correct reference to use based off the station_playlist.module this is why the module does not work correctly with Station Dev 6.x

Granted this is not upgrade safe I hope to see this in the Drupal 6 version soon

how's the project? It is just such a module I need on my website

Here is a charts module I started working on. The date range is not not currently used although "last 7 day" and label popularity are functional.....

access it by the URL http://host/reports

Enjoy!

  $header = array('Artist', 'Title', 'Rotation', 'Link');
  $rows = array();

  $sql = 'SELECT artist, title, label, link FROM {station_playlist_track} WHERE label = "Indie" ORDER BY artist';
  $res = db_query($sql);
  while ($row = db_fetch_array($res)) {
    $rows[] = $row;
  }

  print theme('table', $header, $rows);