-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New doublon in arts data- but old one not.. #85
Comments
@MaudeFJ Initially I wasn't sure why the person 'catelier' decided to add the Place from Artsdata rather than use the one that is already in Footlight. But after some tests (see below) I think it's because they didn't include the hyphens (-). We are working on improving the search algorithm in Footlight so that this doesn't happen. Here are my findings. When i typed the whole name (with hyphens) in the event form Location field (in the Events workspace), I saw this: HOWEVER, when I typed the the whole name without hyphens, this happened. As a side note, the reason there are two instances for this place (one in Footlight, one in Artsdata) because the one you and I created in Footlight is not linked to the one in Artsdata. Once they are linked, I believe you would only see one. |
Regarding Also, some feature that would be nice to have in the future is like an avertissement when creating a doublon like " Hey the thing your creating is oddly similar to this" |
Humm i see. Thanks ! |
@MaudeFJ @troughc I opened an issue to relink the good place in CMS to Artsdata. I also noticed that the place in Artsdata has a different postal code than the place in CMS. H7L 1M9 (laval.ca data) versus H7L 1M7 (CMS). In Google it looks like H7L 1M9 is closer to the entrance of the parc so I will keep that one. |
I'm wondering why.. ?
Also, some feature that would be nice to have in the future is like an avertissement when creating a doublon like " Hey the thing your creating is oddly similar to this"
The text was updated successfully, but these errors were encountered: