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
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 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= 1OAxTLqFN4KjnQf AnrnUAw& sa=X&oi= local_group& ct=more- results& resnum= 1&ved=0CCAQtQMw AA
http://
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=0CDcQtQMw Aw
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