Tango.info http interface

Implemented

• tango.info search
  • e.g. http://www.tango.info/?q=Canaro (person)
  • e.g. http://www.tango.info/?q=Berlin (city)

• person by IPI
  • http://www.tango.info/ipi.00005008929
• video youtube ID
  • http://www.tango.info/youtube.XJDowJI0-7s
• album by TIN
  • http://www.tango.info/00724353068523
• track by TINT
  • http://www.tango.info/00724353068523-1-1
  • http://www.tango.info/00724353068523/1/1

• recordings, artist, a-z work name
  • http://www.tango.info/recordings/RodolBiagi/work.racing_club
• recordings, artist, part of work name
  • http://www.tango.info/recordings/CayetDisar/?work_name_contains=bel
• tracks, artist, a-z work name
  • http://www.tango.info/tracks/RodolBiagi/work.racing_club
• tracks, artist, part of work name
  • http://www.tango.info/tracks/CayetDisar/?work_name_contains=bel

Planned

• Disc e.g. http://www.tango.info/08427328020459-1

Requested

• http://www.tango.info/?q=8021750809226 and http://www.tango.info/08427328020459 - "no results"/not found page, offer Google & Amazon
• special search for TINT-, TINT\ and TINT/ e.g.
  • http://www.tango.info/?q=08427328020688-1-7
  • http://www.tango.info/?q=08427328020688\1\7 - needs consideration of "\" standards conformance
  • http://www.tango.info/?q=08427328020688%5C1%5C7
  • note: this is a special, non-standard search because TINsDsT specifies a pattern rather than a literal string. Hence the design should consider carefully the risk of false matches due to a literal string being misinterpreted as a pattern. Perhaps sufficient to avoid this sufficiently is a pattern definition allowing just digits and separators e.g. regex [0-9]{12,14}[\/-][0-9]+[\/-][0-9]+

Review needed

• http://www.tango.info/08427328020688\1\7 - back slash standard conform?

See also

• identifiers