While the Node Hierarchy module is really helping me define Tracks for my Albums, I really wish I could change around the fields for Album more.

Also, why is there a log number, and what use is it when each entry has a node id?

Comments

drewish’s picture

what sort of track info are you storing?

out station had sequential log numbers labeled on each album and the albums were ordered by number. since we had 14,000 albums at that point relabeling them wasn't a possibility. the node ids aren't sequential or specifiable so i added the log number field.

tim.plunkett’s picture

This is what I am going to be putting together using CCK fields. Also, if done this way, accessing the information from the database might be more standardized, i.e. from one table instead of content_type_station_album and station_catalog.

FOR ALBUM:
Artist
Album
Date (put in library)
Genre
Year
Format (CD, LP, 7")
Various Artist?
Live at WKDU?
Digitized?
In Storage?
Description

FOR TRACK:
Number
Title
Length
Lyrics
FCC Clean?

drewish’s picture

I'm interested in the possibility of adding track but I don't think it makes sense to add them as separate nodes. Those should either be a custom CCK field or done in a non-CCK manner.

drewish’s picture

The rest of it seems like excellent candidates for CCK fields. I'd rather take the performance hit rather than force everyone into having all those fields.

tim.plunkett’s picture

Tracks as nodes is not necessarily the desired result, merely my current workaround.
I'm just not sure how to go about adding any functionality.

drewish’s picture

Well you could either steal some code from the station_playlist.module for putting a table of fields into a node or look at writing a CCK field.

drewish’s picture

Title: Maybe use CCK more? » Add tracks to albums
refreshingapathy’s picture

I am in unbelievably strong support of this idea.