BeJazz late 2024 concert dates seem to be from 2023

[MarkJaroski]

Fairsocial.ch received this note from BeJazz:

Guten Tag

Für Ihre Event-Agenda Mobilisons.ch haben Sie offenbar die Konzerte auf unserer Website bejazz.ch gegrabbed, bilden diese allerdings an falschen Daten ab.
Dies ist für ein Zufalls-Publikum, welches sich eventuell auf Ihre Seite verirrt, äusserst verwirrend.
Daher bitte ich Sie freundlich, diese Einträge zu löschen und künftig keine Daten mehr von unserer Website abzuziehen.

Beste Grüsse,
****************, BeJazz

When I went to examine the situation I noticed that there are dates listed in November 2024 which are really from 2023.

In any case, I'll reach out and try to talk with him to see if we can come to some kind of understanding. Maybe the best thing would be to purge their events for now from both projects.

[jakopako]

Let me know how it goes. Would be nice to add those events again to concertcloud and mobilisons :)

[MarkJaroski]

I agree. So far they have not responded to my email.

[jakopako]

@MarkJaroski would you be able to filter the BeJazz events within the script that copies concertcloud events to mobilison? I'd like to readd the venue to concertcloud, since I am pretty confident that the year bug has been fixed.
And I guess no one will notice that the events are reappearing on concertcloud since they don't know the website :D

[MarkJaroski]

They made it pretty clear that their objection was towards the act of scraping.

However, it doesn't matter because the filter is already there. It filters on the URL not the venue name, because they present at multiple venues.

[jakopako]

Hmm ok, in that case I guess it would be impolite to scrape their website against their will. It bugs me a bit that we could easily include this data correctly but are not allowed to do so. But ok, I'll leave it as is for now.

[MarkJaroski]

Well, we can try reaching out again.

…

On Tue, 18 Jun 2024 at 23:17, jakopako ***@***.***> wrote: Hmm ok, in that case I guess it would be impolite to scrape their website against their will. It bugs me a bit that we could easily include this data correctly but are not allowed to do so. But ok, I'll leave it as is for now. — Reply to this email directly, view it on GitHub <#323 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAATLBTI322KXFRCIU4PRLLZICPWVAVCNFSM6AAAAABCJCRWOWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZWHE4TCMBRHA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[jakopako]

I'll try my luck :D