Jump to a different year? Take your pick! ☸ 2000 ☸ 2001 ☸ 2002 ☸ 2003 ☸ 2004 ☸ 2005 ☸ 2006 ☸ 2007 ☸ 2008 ☸ 2009 ☸ 2010 ☸ 2011 ☸ 2012 ☸ 2013 ☸ 2014 ☸ 2015 ☸ 2016 ☸ 2017 ☸ 2018 ☸ 2019 ☸ 2020 ☸ 2021 ☸ 2022 ☸ 2023 ☸ 2024 ☸

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

--- audiodb:gat [2016/02/07 13:27] – [Detail Tags] randolo
+++ audiodb:gat [2020/06/14 23:54] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
-====== Guidelines for Audio Tagging (GAT), version 2.3 ======
+====== Guidelines for Audio Tagging (GAT), version 2.5 ======
 The goal of this document is to provide a logically consistent framework for tagging both commercial and noncommercial audio recordings in a relatively simple fashion (hah! fitting both needs together is a somewhat complex task that will require resolution of competing needs and exceptions!). This system grew out of frustration with the incompleteness/inconsistency of standard tagging systems (see [[http://wiki.hydrogenaudio.org/index.php?title=Tags|Hydrogen Audio]]'s terrific primer page for additional background).
@@ Line 20: / Line 20: @@
 ==== Basic Tags ====
-[[gat#artist|ARTIST]] <html>&#9830;</html> [[gat#artistsort|ARTISTSORT]] <html>&#9830;</html> [[gat#album_artist|ALBUM ARTIST]] <html>&#9830;</html> [[gat#album|ALBUM]] <html>&#9830;</html> [[gat#status|STATUS]] <html>&#9830;</html> [[gat#event|EVENT]] <html>&#9830;</html> [[gat#venue|VENUE]] <html>&#9830;</html> [[gat#city|CITY]] <html>&#9830;</html> [[gat#state|STATE]] <html>&#9830;</html> [[gat#st|ST]] <html>&#9830;</html> [[gat#country|COUNTRY]] <html>&#9830;</html> [[gat#ccode|CCODE]]
+[[gat#artist|ARTIST]] <html>&#9830;</html> [[gat#artistsort|ARTISTSORT]] <html>&#9830;</html> [[gat#abbr|ABBR]] <html>&#9830;</html> [[gat#album_artist|ALBUM ARTIST]] <html>&#9830;</html> [[gat#album|ALBUM]] <html>&#9830;</html> [[gat#status|STATUS]] <html>&#9830;</html> [[gat#event|EVENT]] <html>&#9830;</html> [[gat#venue|VENUE]] <html>&#9830;</html> [[gat#city|CITY]] <html>&#9830;</html> [[gat#state|STATE]] <html>&#9830;</html> [[gat#st|ST]] <html>&#9830;</html> [[gat#country|COUNTRY]] <html>&#9830;</html> [[gat#ccode|CCODE]]
 [[gat#basic_tag_definitions|jump to Basic Tag Definitions]]
 ==== Date Tags ====
 [[gat#date_gig|DATE GIG]] <html>&#9830;</html> [[gat#date_release|DATE RELEASE]] <html>&#9830;</html> [[gat#date_reprint|DATE REPRINT]] <html>&#9830;</html> [[gat#date_tagged|DATE TAGGED]] <html>&#9830;</html> [[gat#date_purchased|DATE PURCHASED]] <html>&#9830;</html> [[gat#date_long|DATE LONG]]
@@ Line 58: / Line 57: @@
 If this seems weird to you, it's because you're not thinking like a librarian/archivist.
 </WRAP>
+  ; [ABBR] : Originally this field contained the etree-compliant band/artist abbreviation. Although it's use is no longer necessary with the demise of 8+3 filenaming, brevity is still helpful for readability. After all, would you rather look at a folder with tracknames like "Florence and the Machine 2015-10-21 U.C. Berkeley Greek Theatre t01.flac" or "F+tm_2015-10-21_Greek_t01.flac"? The problem here is that it's **impossible** to standardize things to guarantee short readable filenames -- there are just too many possibilities for artist and venue names. So compromise is necessary. Relax. Take a deep breath. Name things how you like. Don't freak out if I think your carefully curated and shared files should be named differently...they're mine now, right? Feel free to retag and rename mine as you see fit for yourself. Now exhale. See? Easy, wasn't it?
   ; [ALBUM ARTIST] : This tag is typically used for collections that contain tracks by multiple artists; my preference is to use '_Various Artists_' in this field, then to fill ARTIST as appropriate on a track-by-track basis. More info on the use and reasoning behind this approach is given in the [[http://wiki.hydrogenaudio.org/index.php?title=Foobar2000:Encouraged_Tag_Standards#ALBUM_ARTIST|foobar wiki]].
@@ Line 88: / Line 89: @@
   ; [COUNTRY] : Full name of country, native (romanized) spelling preferred if location is a non-English speaking locale.
-  ; CCODE : [[http://en.wikipedia.org/wiki/ISO_3166-1_alpha-3|ISO-3166-1 alpha-2 three-letter country codes]] such as _USA_ and _DEU_. For CRM, use this field to indicate the release country for a particular media item.
+  ; CCODE : [[http://en.wikipedia.org/wiki/ISO_3166-1_alpha-3|ISO-3166-1 alpha-2 three-letter country codes]] such as _USA_ and _DEU_. For CRM, this field can be used to indicate the release country for a particular media item (eg., to differentiate between US and British releases of the same album).
 ==== Date Tag Definitions ====
@@ Line 108: / Line 109: @@
 ==== Detail Tag Definitions ====
-  ; PERFORMER : An alphabetized list where each entry is in the form
+  ; PERFORMER : Ideally, this is an alpha-ordered list where each entry is in the form
-  "name: instrument[, instrument2[,instrument3...]];<CR>"
+  "name: instrument[, instrument2[,instrument3...]];"
-  eg., "Jerry Garcia: guitar, vox;
+  eg.,
+   "Jerry Garcia: guitar, vox;
     John Kahn: bass;
     Ron Tutt: drums."
-The final list element ends with a period instead of semicolon+<CR>. This field may be modified on a per-track basis. The field may also include conductors, choir-masters and any other contributors deemed worthy of note by the tagger, where the job function appears as an "instrument". This mode of usage obviates the need for specialized but little-used tags such as CONDUCTOR, LYRICIST, REMIXER and so on.
+The final list element should terminate with a period instead of a semicolon. This field may be modified on a per-track basis. The field may also include conductors, choir-masters and any other contributors deemed worthy of note by the tagger, where the job function appears as an "instrument". This mode of usage obviates the need for specialized but little-used tags such as CONDUCTOR, LYRICIST, REMIXER and so on.
-<WRAP important>While the preceding layout is designed for ease of readability, it doesn't make for ease of entry.\\
+<WRAP important>When viewed in a JSON editor, this sort of list will automatically be decomposed into it's individual elements. But as a raw tag, things are not so readabile, as each list element follows the next without whitespace (a newline would be terrific!), and asking for the list to be alpha-ordered doesn't make for ease of entry.\\
-Far better would be an unordered array {[name1, instrument1],[name2, intrument2],...} where alphabetization and consolidation of multiple entries is performed by the software rather than the user.\\
+Far better would be an unordered array {[name1, instrument1],[name2, intrument2],...} where alphabetization and output-formatting of multi-element entries is performed by the software rather than the user.\\
-However, sorting a list of names in a manner that catches all of the weirdness allowed in English usage has stymied many a programmer. If anyone knows how to program Foobar 2000 to accomplish this task, please let me know!
+Unfortunately, sorting a list of names in a manner that catches all of the weirdness allowed in English usage has stymied many a programmer. If anyone knows how to program Foobar 2000 to accomplish this task, please let me know!
 </WRAP>
+Also, as of v2.4, this field _may_ include markdown formatting (most likely initial bullets: "* "), but such visual markup is **NOT** required.
+As of v2.5, use of markdown formatting is discouraged -- a tag is considered raw content, not formatted data.
   ; CREDITS : Free-form field giving the name (and possibly email address) of one or more persons involved in recording, transferring, encoding and sharing of this recording. New references/comments should appear on new lines. Samples follow.
   Recorded by Jean Lerond <lerond@gmail.com>
   Transfered by Randy Vogel <randy@funfolks.net> on 2012-03-14
-  Tagged by Randy Vogel <randy@funfolks.net> on 2012-03-16
+  Tagged by [Randy Vogel] on 2012-03-16
 I realize that the example uses some of the date fields -- I think this makes the credits more useful and readable -- don't you?
+Note also the use of markdown reflink style in the third example. In order for that link to be valid, the REFLINK field **MUST** include the link target, as shown in the next preview box
+  [Randy Vogel]: mailto:randy@funfolks.net
-  ; URL : An un-ordered array of markdown formatted reference lines that include a URL formatted as shown:
+  ; URL : An un-ordered array of markdown formatted internet reference lines.
+These can be formatted inline:
   [URL handle](URL)
+Or by reference, using a subsequent entry in the REFLINK field:
+  %URL% contains [URL handle]
+  %REFLINK% contains [URL handle]: URL
+Choice to use either style is left to the tagger. The goal here is for ease of readability.
 Any or all of the following URLs may be included: official artist/performer, record label/publisher, copyright/legal, download/torrent source, lyrics page, et cetera; each may include optional explanatory text comments.\\
 \\
@@ Line 137: / Line 148: @@
 Note that like many other resources on the Internet, MuscBrainz is imperfect, and the album used as an example does not appear to connect properly to Pharoah the individual, only to his eponymous quartet. Foobar 2000 can find these links semiautomagically via the optional [musicbrainz plugin](http://www.hydrogenaud.io/forums/index.php?showtopic=70623) component. I have nothing against including pointers to other resources, such as pages from [AllMusic](http://www.allmusic.com/album/karma-mw0000200235) or [Discogs](http://www.discogs.com/Pharoah-Sanders-Karma/release/873261) that offer the first release of Pharoah's classic tune, recorded on Valentine's Day in 1969 -- the point is simply to direct the interested reader to further information regarding this listening matter.\\
 \\
-For live shows, I like to reference to the eTree database, particularly for shows and sources. For example:
+For live shows, I prefer references to the eTree database, particularly for shows and sources. For example:
   * eTree showID, for shows, such as that for [The Absolutely Unofficial Blue Jeans Bash](http://db.etree.org/lookup_show.php?shows_key=391656).
   * eTree shnID, for individual recordings, such as [Jim Cooper's recording of the Grateful Dead on Feb 13, 1970](http://db.etree.org/shn/123814).
-In practice, I commonly just use 'eTree showID' or 'eTree shnID' rather than the more detailed handles given in the previous examples.
+In practice, however, I commonly just use 'eTree showID' or 'eTree shnID' rather than the more detailed handles given in the two previous examples, hence:
+  [eTree showID](http://db.etree.org/lookup_show.php?shows_key=391656).
+  [eTree shnID](http://db.etree.org/shn/123814).
+  ; REFLINK : This field is used to store longer URLs in order to maintain readability by using reference link style in the CREDITS and URL fields rather than inline link style. Usage examples have been provided above.
   ; SRCCHAIN : Master recording details, usage varies by CRM/NCO Status.\\
@@ Line 161: / Line 176: @@
   ; [NOTES] : Optional free-form field for any other comments or information about the recording. COMMENT should map to this field (NOTES was chosen over COMMENT for brevity).
-  ; TAGSYS : The string 'GATvN.M = where N.M version number of this tagging system -- 2.2 at present! (used to provide backwards compatibility in foobar string coding - ie., to let the software to know to process v1 tags differently than v2).
+  ; TAGSYS : The string 'GATvN.M = where N.M version number of this tagging system -- **GATv2.5** at present! This field is used to provide backwards compatibility in foobar string coding - ie., to let the software to know to process v1 tags differently than v2.
   ; ISO639-2 : 'eng' unless you are tagging in another language, in which case that [[http://en.wikipedia.org/wiki/ISO_639-2|ISO code]] goes here instead. The goofy fieldname arises because that's the ISO standard reference number for these codes.

Jump to a different year? Take your pick! ☸ 2000 ☸ 2001 ☸ 2002 ☸ 2003 ☸ 2004 ☸ 2005 ☸ 2006 ☸ 2007 ☸ 2008 ☸ 2009 ☸ 2010 ☸ 2011 ☸ 2012 ☸ 2013 ☸ 2014 ☸ 2015 ☸ 2016 ☸ 2017 ☸ 2018 ☸ 2019 ☸ 2020 ☸ 2021 ☸ 2022 ☸ 2023 ☸ 2024 ☸

RandoloWiki

User Tools

Site Tools

Differences

Page Tools