Crawl centre-des-arts-juliette-lassonde?

[saumier]

@fjjulien There was an Orion JSON-LD workflow to crawl centre-des-arts-juliette-lassonde but I removed it last year.

Footlight Console crawls this same site as centredesarts-ca.

I propose we add back the schedule to crawl the JSON-LD of this website so we can compare in Artsdata.

I have restored the old workflow but have not yet set a schedule.

I'll leave the schedule for your team.

[fjjulien]

@saumier I added a schedule and I ran the workflow: https://github.com/artsdata-stewards/artsdata-orion/blob/main/.github/workflows/centredesarts-ca.yml

Comparative analysis of the two sources:

• They have different place granularity. The JSON-LD's object is at the room level; the Footlight object, at the building level.
• The JSON-LD source does not have a time zone offset.
• The JSON-LD source has better offer data.
• The Footlight source has clearly identified organizer and performer entities. The JSON-LD has nested objects but without sameAs.
• The Footlight source has additionalType.

Issue with the JSON-LD source:

• When there are more than one performance on the same page, only the latest performance has structured data. Example:
  • Event web page: https://www.centredesarts.ca/spectacle/apres-on-va-ou-michel-rivard
  • Structured data

I'm not sure how to rank each source. If I give a better rank to the Orion source, will the Artsdata pipeline still import the organizer.sameAs and performer.sameAs? This would be risky: two sources might have diverging organizer and performer values.

This is a case where we would need to rank graphs at the property level.

[fjjulien]

This issue can now be tracked in artsdata-stewards/source-logs#4

I'm closing this issue as a duplicate.