More fine tuning of tag and variable categorization

variables/tags_advanced.rst

@@ -111,10 +111,6 @@ If you enable "Use track relationships" in the Option settings, you get these ex
 
    - the concert master for the associated release or recording, where <type> is "*concertmaster*"
 
-**producer**
-
-   The names of the producers for the associated release or recording.
-
 **releasedate**
 
    Explicit tag for the release date (*since Picard 2.9*). This tag exists for specific use in scripts and plugins, but is not filled by default. In most cases it is recommended to use the ``date`` tag instead for compatibility with existing software.
@@ -135,6 +131,10 @@ If you enable "Use track relationships" in the Option settings, you get these ex
 
       $copymerge(composer, writer)
 
+.. note::
+
+   Some tags such as **performer** are available as both track and release level relationships, and the values may be different depending on which relationship options are enabled.
+
 
 .. _genre_settings:
 

variables/tags_basic.rst

@@ -204,7 +204,7 @@ These tags will be provided based on the information from the MusicBrainz databa
 Tags Not Provided from MusicBrainz Data
 ---------------------------------------
 
-These tags are not able to be populated by stock Picard, however they may be used and populated by certain plugins.
+These tags are not able to be populated by stock Picard, however they may be used and populated by certain plugins or scripts.
 
 **acoustid_fingerprint**
 
@@ -262,6 +262,10 @@ These tags are not able to be populated by stock Picard, however they may be use
 
    The original name of the audio file.
 
+**producer**
+
+   The names of the producers for the associated release or recording.
+
 **showmovement**
 
    The work and movement of the track.
@@ -278,7 +282,7 @@ These tags are not able to be populated by stock Picard, however they may be use
 iTunes-Specific Tags
 --------------------
 
-These tags are only available in iTunes files and are not able to be populated by stock Picard, however they may be used and populated by certain plugins.
+These tags are only available in iTunes files and are not able to be populated by stock Picard, however they may be used and populated by certain plugins or scripts.
 
 **gapless**
 

variables/variables_advanced.rst

@@ -42,6 +42,29 @@ Some variables provide the :index:`MusicBrainz Identifier (MBID) <identifier; mu
    Variables will not be created if there was no value retrieved for the variable from the MusicBrainz database.
 
 
+Release Relationship Variables
+------------------------------
+
+If you enable tagging with :doc:`Use release relationships </config/options_metadata>`, you get these extra variables:
+
+**_release_series**
+
+   A multi-value variable containing the series titles associated with the release. (*since Picard 2.9*)
+
+**_release_seriesid**
+
+   A multi-value variable containing the series MBIDs associated with the release. (*since Picard 2.9*)
+
+**_release_seriescomment**
+
+   A multi-value variable containing the series disambiguation comments associated with the release. (*since Picard 2.9*)
+
+**_release_seriesnumber**
+
+   A multi-value variable containing the series numbers associated with the release. (*since Picard 2.9*)
+
+
+
 Track Relationship Variables
 ----------------------------
 
@@ -79,16 +102,6 @@ If you enable tagging with :doc:`Use track relationships </config/options_metada
 
    The disambiguation comment associated with the work. (*since Picard 2.7*)
 
-**_writersort**
-
-   The sort names of the writers for the work. (*since Picard 2.9*)
-
-
-Track or Release Relationship Variables
----------------------------------------
-
-If you enable tagging with :doc:`Use track relationships </config/options_metadata>` or :doc:`Use release relationships </config/options_metadata>`, you get these extra variables:
-
 **_work_series**
 
    A multi-value variable containing the series titles associated with the work. (*since Picard 2.9*)
@@ -104,3 +117,7 @@ If you enable tagging with :doc:`Use track relationships </config/options_metada
 **_work_seriesnumber**
 
    A multi-value variable containing the series numbers associated with the work. (*since Picard 2.9*)
+
+**_writersort**
+
+   The sort names of the writers for the work. (*since Picard 2.9*)

variables/variables_basic.rst

@@ -73,22 +73,6 @@ Some variables provide the :index:`MusicBrainz Identifier (MBID) <identifier; mu
 
    The date of the earliest recording for a track in the format YYYY-MM-DD. (*Since Picard 2.6*)
 
-**_release_series**
-
-   A multi-value variable containing the series titles associated with the release. (*since Picard 2.9*)
-
-**_release_seriesid**
-
-   A multi-value variable containing the series MBIDs associated with the release. (*since Picard 2.9*)
-
-**_release_seriescomment**
-
-   A multi-value variable containing the series disambiguation comments associated with the release. (*since Picard 2.9*)
-
-**_release_seriesnumber**
-
-   A multi-value variable containing the series numbers associated with the release. (*since Picard 2.9*)
-
 **_releaseannotation**
 
    The annotation comment for the release. (*since Picard 2.6*)