Tango.info http interface: Difference between revisions
Jump to navigation
Jump to search
m (→Implemented) |
m (→Implemented) |
||
| Line 8: | Line 8: | ||
* person by [[tango.info person code]] | * person by [[tango.info person code]] | ||
** http://www.tango.info/JuanaDarie | ** http://www.tango.info/JuanaDarie | ||
* couple by tango.info couple code | * couple by [[tango.info couple code]] | ||
** http://www.tango.info/JavieRodri-y-GeralRojas | ** http://www.tango.info/JavieRodri-y-GeralRojas | ||
* video by youtube ID | * video by youtube ID | ||
Revision as of 2010-02-11T01:48:27
Implemented
- person by IPI
- person by tango.info person code
- couple by tango.info couple code
- video by youtube ID
- album by TIN
- track by TINT
- work by az name
- recordings, artist, az name
- recordings, artist, part of work name
- tracks, artist, az name
- tracks, artist, part of work name
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?