This is the documentation on all the theme override functions in Discogs 6.x.

This is the handbook page for the 6.x version of Discogs.

The module creates a new content (node) type, called "Discography." That content type has fields for artist, label, catalog number, format, country, date, and album credits. In addition, it can contain multiple tracks (which reside in their own database table in a many-to-one relationship). Tracks have fields for position, title, artist, duration, notes, and lyrics.

In addition to creating this content type, this module also can pull in discography data from www.discogs.com. You can search for artist, album, or label data, returning a checklist of albums, which can then be imported into Drupal as discography nodes.

In order to use the Discography Framework with other API's besides Discogs.com, or other entities besides the Release Node, you will need to develop your own module that plugs in to the Discography Framework. This project is designed to make it as easy as possible to do so; all you need to do is to implement a small number of hooks.

This section describes the various parts of the framework, their purposes, and the modules that implement them.

Discography Entities and Fields

Within Drupal, discography information is saved inside an entity type. Usually, that entity is a node type, but it could be a custom entity type, or a system of related node types (like Pushtape Discography), and it can have different kinds of fields.

The Discography Framework provides one field, and two node types:

• Track Field: This is a field that holds information about a single track. You can add this field to any content type (such as an audio node). In addition to the multiple built-in formatters and widgets, the field is fully themeable using a template.

  Both the Release Node and Track Node modules are dependent upon the Track Field module.

• Track Node: This is provided for sites that focus on tracks, rather than albums or releases. It is essentially a node wrapper for a single instance of a Track Field. Of course, site administrators can also add whatever fields they want through the Fields UI, just like any other node type.
• Release Node: This node type handles information for a single discography release. It is probably the most important part of the framework, from the user's perspective.
  

This is the online documentation for the Discogs project:
https://drupal.org/project/discogs

Documentation is split into 6.x and 7.x versions, since they are very different.

The 7.x version is now called the Discography Framework. The "discogs" name is being used here solely for historical reasons.