Concert search should take place on LLL

[lwholey]

http://api.eventful.com/ provides what looks like a great resource. Our application key is gr2xkHcHxTF3BQNk.

[lwholey]

John, you may have already started this, but here's an initial outline for the plan to implement this feature (doesn't need to be accomplished in this order):

• UI
  • for concert search inputs (for example: dates, city, type of music, etc.) Perhaps we start with the basics here and then get fancier like having the user enter a band name and then LLL (w/ eventful) finds similar concerts.
  • for concert search outputs
  • for allowing user to request Spotify tracks (based on concert search outputs)
  • for displaying concert search outputs along with Spotify tracks
• Interface with eventful API - I think I'll take crack at this one (unless you've already started it). Do you want to work on the UI stuff?

[lwholey]

Here's an example usage of the eventful API

http://api.evdb.com/rest/events/search?app_key=gr2xkHcHxTF3BQNk&user=lwrunner1&password=eventfulnerd1&keywords=books&location=San+Diego&date=Future

Our user name is lwrunner1 Our password is eventfulnerd1 Our key is gr2xkHcHxTF3BQNk

[lwholey]

Here's another example of using the eventful API

http://api.evdb.com/rest/events/search?app_key=gr2xkHcHxTF3BQNk&user=lwrunner1&password=eventfulnerd1&keywords=regatta bar&location=Boston ( it doesn't seem to have a problem with the space between 'regatta' and 'bar', but if it does, we can likely replace the space with %20 )

See http://api.eventful.com/docs/events/search for more info In the search, we will likely want to include (there may be other fields that we want): keywords (possibly use this for type of music, venue, etc.) location date &category=music sort_order

http://api.eventful.com/tools/tutorials/search has some good shortcuts (for example 'q' is 'keywords')

John, I had mentioned above that I could work on the code for the API. I think I'm going to stop here though, because the code will be so closely tied to the UI - I'm not sure what code I would write now. Let me know if I can help though.

[johnwilde]

Not sure if you've seen this:

http://api.eventful.com/libs

It looks like there is already a ruby gem for interfacing with the API.

On Sun, Aug 28, 2011 at 6:27 PM, lwholey reply@reply.github.com wrote:

Here's another example of using the eventful API

http://api.evdb.com/rest/events/search?app_key=gr2xkHcHxTF3BQNk&user=lwrunner1&password=eventfulnerd1&keywords=regatta bar&location=Boston ( it doesn't seem to have a problem with the space between 'regatta' and 'bar', but if it does, we can likely replace the space with %20 )

See http://api.eventful.com/docs/events/search for more info In the search, we will likely want to include (there may be other fields that we want): keywords (possibly use this for type of music, venue, etc.) location date &category=music sort_order

http://api.eventful.com/tools/tutorials/search has some good shortcuts (for example 'q' is 'keywords')

John, I had mentioned above that I could work on the code for the API.  I think I'm going to stop here though, because the code will be so closely tied to the UI - I'm not sure what code I would write now.  Let me know if I can help though.

Reply to this email directly or view it on GitHub: https://github.com/lwholey/concert/issues/8#issuecomment-1926616

[lwholey]

Cool, run with it.

On Mon, Aug 29, 2011 at 12:55 PM, johnwilde < reply@reply.github.com>wrote:

Not sure if you've seen this:

http://api.eventful.com/libs

It looks like there is already a ruby gem for interfacing with the API.

On Sun, Aug 28, 2011 at 6:27 PM, lwholey reply@reply.github.com wrote:

Here's another example of using the eventful API

http://api.evdb.com/rest/events/search?app_key=gr2xkHcHxTF3BQNk&user=lwrunner1&password=eventfulnerd1&keywords=regattabar&location=Boston ( it doesn't seem to have a problem with the space between 'regatta' and 'bar', but if it does, we can likely replace the space with %20 )

See http://api.eventful.com/docs/events/search for more info In the search, we will likely want to include (there may be other fields that we want): keywords (possibly use this for type of music, venue, etc.) location date &category=music sort_order

http://api.eventful.com/tools/tutorials/search has some good shortcuts (for example 'q' is 'keywords')

John, I had mentioned above that I could work on the code for the API. I think I'm going to stop here though, because the code will be so closely tied to the UI - I'm not sure what code I would write now. Let me know if I can help though.

Reply to this email directly or view it on GitHub: https://github.com/lwholey/concert/issues/8#issuecomment-1926616

Reply to this email directly or view it on GitHub: https://github.com/lwholey/concert/issues/8#issuecomment-1933460

[lwholey]

Using "Title" often produces difficult to parse text. For example, "Grammy nominated trumpeter Fabio Morgera & friends,live"

[lwholey]

Date/time in Events found needs cleaned up. For example, 2011-11-18 15:00:00 -0500 (make the date clearer, convert military time to AM/PM, and shift time by -0500?)

[lwholey]

Clicking "More Details" in "Events found" should open a new tab or a new window (and not leave LLL)

[lwholey]

(done) Put a "?" next to "City", "Dates", and "Keywords" to provide instructions (and example) of what should be put in these fields.

[lwholey]

(done) If a band is listed more than once in Events found (more than one show), we currently show N/A in the track info. It might be better to replace this with the same track info. Here's an example of what is currently like The Bad Plus Lithium The Bad Plus N/A

We could replace this with The Bad Plus Lithium The Bad Plus Lithium

[lwholey]

Get additional pages from eventful