Venue List Suggestion

Bug #539512 reported by Charles Profitt
This bug affects 2 people
Affects Status Importance Assigned to Milestone
LoCo Team Portal
Fix Released
Martin Owens

Bug Description

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.

Related branches

Revision history for this message
Daniel Holbach (dholbach) wrote :

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

Changed in loco-directory:
importance: Undecided → Wishlist
status: New → Triaged
tags: added: needs-decision schema-change ui
Revision history for this message
Laura Czajkowski (czajkowski) wrote :

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

Revision history for this message
Daniel Holbach (dholbach) wrote :

Does the proposed solution to bug 571645 fix this?

Changed in loco-directory:
status: Triaged → Incomplete
Revision history for this message
Laura Czajkowski (czajkowski) wrote :

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

Revision history for this message
Charles Profitt (cprofitt) wrote :

#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.

Revision history for this message
Charles Profitt (cprofitt) wrote :

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.


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?

Changed in loco-directory:
status: Incomplete → Confirmed
Revision history for this message
Charles Profitt (cprofitt) wrote :

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

def grouped_venue_list(self):

from /loco_directory/events/ 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.

Revision history for this message
Daniel Holbach (dholbach) wrote :

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

Revision history for this message
Charles Profitt (cprofitt) wrote :


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.


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

Revision history for this message
Ronnie (ronnie.vd.c) wrote :

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.

Revision history for this message
Chris Johnston (cjohnston) wrote :

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?

Revision history for this message
Charles Profitt (cprofitt) wrote :

Sounds like a way to solve the issue. Thanks.

Changed in loco-directory:
assignee: nobody → Martin Owens (doctormo)
milestone: none → 0.3.3
status: Confirmed → Fix Committed
tags: removed: needs-decision
Changed in loco-directory:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Related blueprints