Helium Music Manager User Forum

[Mikael Stalvik]

But, wouldn't that require much more than just an additional tag field?

To get it useful, a filed would need to be added, additions is need to be made to the tag editor, it needs to be added to the advanced search and also probably somewhere into the custom view, so that you can track which releases that you are missing. Isn't that correct?

Personally, I use the part of series tag field (which is available in the custom view) to track missing releases.
I collect for example react cd's which are labled in the way you describe, as well as other "series" such as rave mission, rave now, trancemaster, gemini project etc.

[bassiliin]

To get it useful, a filed would need to be added, additions is need to be made to the tag editor, it needs to be added to the advanced search and also probably somewhere into the custom view, so that you can track which releases that you are missing. Isn't that correct?

yep, that's correct.

I collect for example react cd's which are labled in the way you describe, as well as other "series" such as rave mission, rave now, trancemaster, gemini project etc.

part of 'series' is completely different thing. though, they also come out under certain recordlabels, and they have catalog# , but between 'Rave Mission 3' and 'Rave Mission 4' can be 5, 17, or maybe even 153 other releases that come out under same recordlabel. (i.e. if 'Rave Mission 3' has catalog# EMI-125-CD5, then 'Rave Mission 4' can be like EMI-139-CD5, and between them can be one Madonna's album (EMI-126-CD5), some other compilation like Techno Traxx 9 (EMI-127-CD5), etc...

catalog# is based on recordlabel (mostly generated from Record Label, release type (LP,CD,CD5",CD3",12",7",etc) and release number and their appearance can vary by recordlabels and even within a recordlabel (see post #3)), not on artist or compilation names.