sahalali
commented
1 month ago @saumier let's update the SPARQL query for this source and add the footlight place URI to the location (https://api.footlight.io/places/663b8d6f0796c300645e2ab9). Example: { name": { "fr": "Example Event" }, location": { "Place": "https://api.footlight.io/places/663b8d6f0796c300645e2ab9" }, }
So that, the aggregator can identify the location in the response as location in the footlights CMS.
User Story
As an admin of the Signé Laval website, I review and publish events from the city of Laval coming from Données Quebec data dump. The events in the Données Quebec data dump are often missing a place. This prevents the event from getting loaded into Footlight CMS. I would like the events to load into Footlight CMS so I can fix the location and other info during my review so I can then publish the event.
Proposed solution
In the data pipeline that loads the event data dump from Données Quebec, the events missing a location should have the following location Placeholder added.
https://cms.footlight.io/dashboard/63457978637093005071a053/places/663b8d6f0796c300645e2ab9
https://api.footlight.io/places/663b8d6f0796c300645e2ab9
The challenge is to allow the event to pass through Artsdata and into CMS, but WITOUT minting the place with a K-number.
OTHERWISE a new sparql to load place data using an external URI can be created (and used for all loads from a source without needing to create place K-numbers)
Test Case
Pick an event in the Données Quebec event data dump that is missing a place. Load the data from Données Quebec, and check in Artsdata if the Placeholder was added. Then load into Footlight CMS in staging and check that the event loaded.