Tango.info recorded performance code
------------- D R A F T -----------
tango.info recording code (TIRC)
RENAME TO tango.info primary recording TIPR? primary audio TIPA? recorded audio TIRA? audio code TIAC? master code/media code TIMC?
See also International Standard Recording Code (ISRC)
Purpose
Easy reference to enrich TINTed data with matrice numbers, 78rpm numbers, composers, authors, lyrics, whether composition is in public domain, recording location etc. where these values are the same for different TINTs.
The reference should be short to be typed quickly and consume few space in display.
The schema should
- be unused by other identifiers in tango.info.
- have a short regex representation
- be easy to type
- be independent of case, i.e. upper or lower case letter shall have no meaning.
- be independent of work title or performer names
Example
1944-11-23 Palomita blanca Troilo
- http://www.tango.info/tracks/AnibaTroil/1944-11-23/work.palomita_blanca
- alphanumeric 44328a
- http://www.tango.info/44328a (future link)
- numeric 4432801
Object coverage
Audio recording having the genre: tango, vals, milonga or another genre if the audio exists on a 78rpm or other vinyl and shellac along with audio from the aforementioned genres. LPs are only considered if there is at least 50% tango, vals, milonga content.
The definition of a recording is similar to "recordings" as defined by ISRC.
- http://wiki.tango.info/mul/International_Standard_Recording_Code ISRC
- http://www.ifpi.org/content/section_resources/isrc_handbook.html#Heading337
Speed changes, remasterization etc create a new recording.
The primary coverage shall be of recordings from the 19th century that are not derived from other recordings, e.g. matrices.
The current definition in tango.info of a recording is "Each recording entry corresponds to a group of tracks that have the same title, orchestra, vocalist(s) and recording date (or no recording date). "
The listing http://eng.tango.info/recordings shows recordings with at least 8 CD tracks.
Tracks belonging to one primary recording could among other things differ in speed, and artefacts.
Structure
Alphanumeric
- YYDDDL, regex: [0-9]{5}[a-z]{1}, 5 numbers, one letter
- YY two digit year of audio creation
- DDD
- YY001 - YY366 recordings from 19th century with known dates and up to 26 recordings on that day. DDD shall be the ISO day number within that year (001 -366)
- YY367 - YY999 recordings
- YY367 - YY499 from 19th century
- YY370 - YY378 from days that had more than 26 recordings
- YY380 - YY388 known year but unknown date
- ? year + month known
- ? only year known
- YY367 - YY499 from 19th century
- 99901 - 99989 unknown year
- known decade
- unknown decade
- YY500-YY950 from 20th century
- L a letter a-z assigned by tango.info starting with "a" running alphabetically.
Numeric
- YYDDDNN
- YY as in alphanumeric
- DDD as in alphanumeric
- NN convert the letter to number, a = 01 ... z=26
ISRC mode
- CC-RRR-YY-NNNNN
- CC = ISO 3166-2 alpha 2 country code - use code from private range "XT"
- RRR = some own made identifier
- YY as in TIRC
- NNNNN - use DDD and NN from Numeric variant
TIN mode
- use a TIN range to store the 7 digit numeric code
Optional prefix
use ti prefix, better for string search, e.g. google
- http://www.google.com/search?q=44328h several false hits
- http://www.google.com/search?q=ti44328h no hit
Days with most recordings
based in current tango.info tracks table
- http://www.tango.info/recordings/1981-03-07 17 (q)
- http://www.tango.info/recordings/1985-12-26 21 (u)
- http://www.tango.info/recordings/1989-06-26 17 (q)
- http://www.tango.info/recordings/1996-01-19 14 (n)
Maintenance
Publication
The codes should be made public in different places, to minimize dependence on t.i once the codes are derived. It should be listed in the wiki, but also somewhere else. (github.com ?)
Registration
Primarily codes in the ranges YY001L-YY366L will be assigned.
Date, performers, work title is needed. There can be different takes on one day, if such data is available it can be used to create
Changes
Dates may be "found" to be wrong, e.g. 44328a "found" to be recorded one day later, needing new code 44329e. Old code should be kept end get a link to the new one.
Spelling updates can take place. They should be recorded with timestamp.
Changes in artists - policy needed. E.g. There is http://www.tango.info/recordings/1929-07-11/work.sos_una_fiera one instrumental, one with vocal. Adding vocal to non-vocal or removing all vocal from vocal and altering the vocal can all be corrections or indeed be discovery of a new recording.
ToDo
Is the scheme [0-9]{5}[a-z]{1} used by other code system and could lead to confusion, e.g. matrice numbers?
Feedback
....