Venue List Suggestion

[Charles Profitt]

I would like to offer an alternate suggestion to a search function for venues. If possible venues could have a relationship with the 'LoCo' or user who enters the events. The initial drop down of venues could be limited to these venues with an option to search all venues.

[Daniel Holbach (dholbach)]

Nice idea, but this needs some thinking about how to implement it.

[Laura Czajkowski (czajkowski)]

I'm not 100% sold on this idea, I think it could become very messy. With multiple venues being added due to mis spelling or case sensative adding of an event.

I'd rather add a free text area for the event and a link to a map

[Daniel Holbach (dholbach)]

Does the proposed solution to bug 571645 fix this?

[Laura Czajkowski (czajkowski)]

I think the solution in bug 571645 solves this and the bug can be closed.

[Charles Profitt (cprofitt)]

#571645 is a duplicate of this bug. Normal bugcontrol procedures would have had it marked as such.

Though it should be noted that the entry of a new venue and the selection of a venue by a LoCo adding an event are two different uses. The solution should easily be able to effect both uses though.

[Charles Profitt (cprofitt)]

I did not respond sooner because forwarding of LP email became borked w/o my knowledge.

To implement this I think the following could be entered with a venue.

Country
State
LoCo

If this is a relational database and some locations are 'shared' by loco teams then it would be easy enough to just have each venue have a relationship established when a venue is first used by a team. Then the list of venues could be exposed by having the default view being 'previously used' venues and if desired that could be unchecked.

It is also possible to include check boxes for 'My country only' or 'My state only' if that data is stored in the database.

Is this database relational?

[Charles Profitt (cprofitt)]

I believe the function that needs to be worked on is the following:

def grouped_venue_list(self):

from /loco_directory/events/forms.py under the class TeamEventForm(BaseEventForm):

-----

If there is an option to restrict the displayed venues to the LoCo's country then the list will not grow over-whelming large.

[Daniel Holbach (dholbach)]

Now that we have proper contintents and countries, we could show venues whose country matches the countries of teams.

[Charles Profitt (cprofitt)]

Daniel:

While that may work for Estonia, Latvia, Ireland and other small countries I think we may need to use another 'key' with larger countries like Canada, Russia and the United States.

For example:

Barnes and Noble - North America - United States would have multiple entries

Barned and Noble - North America - United States - Rochester would have multiple entries too.

example
http://maps.google.com/maps?hl=en&um=1&ie=UTF-8&q=barnes+and+nobles+rochester+mn&fb=1&gl=us&hq=barnes+and+nobles&hnear=Rochester,+MN&view=text&ei=1OAxTLqFN4KjnQfAnrnUAw&sa=X&oi=local_group&ct=more-results&resnum=1&ved=0CCAQtQMwAA

http://maps.google.com/maps?hl=en&um=1&ie=UTF-8&q=barnes+and+nobles+rochester+ny&fb=1&gl=us&hq=barnes+and+nobles&hnear=Rochester,+NY&view=text&ei=OeExTPmtF8H_nQeI6LneAw&sa=X&oi=local_group&ct=more-results&resnum=4&ved=0CDcQtQMwAw

I think country is the easiest to implement, hence the suggestion, but I think building a foreign key with each LoCo that has previously scheduled an event using the location could be beneficial as well. Perhaps allowing options when an event is being created:

1. filter by selected country
2. filter by my country (automatically pulled from the LoCo)
3. filter by events used by my LoCo

[Ronnie (ronnie.vd.c)]

I think we should also check - when a user adds a new event - which venues are close, and show a list of these venues. The user can then click one of these venues, or continues creating a new one.

There is a new branch now, which automatic get the coordinates of the given address, so from the new version on, the new venues should all have a longitude and latitude.

[Chris Johnston (cjohnston)]

There is currently a fix committed on a branch that puts "previously used venues" at the top of the venue list when adding a new event. How does this sound?

[Charles Profitt (cprofitt)]

Sounds like a way to solve the issue. Thanks.