search

culturecreates / artsdata-planet-spektrix

0 stars 0 forks source link

Import all clients in our report (about 30) #5

Closed saumier closed 4 weeks ago

saumier commented 1 month ago

CAPACOA would like us to go ahead and load all 30 clients listed in the table of our report. Please load PostalAddress from the second Spektrix API and also extra properties: images, additionalType (genres) and presenter (PresentedBy, PresenterName) and performers.

Clients with images: 17 Clients with genres: 6 Clients with PresentedBy: 2 Clients with PresenterName: 1 Clients with performers: 1

dev-aravind commented 1 month ago

@saumier All the clients are now imported and are present in Artsdata. Please review this and let me know if you need any changes.

saumier commented 1 month ago

@dev-aravind The data loaded into Artsdata has issues across all clients. The events should only have a single startdate/endDate, and the locations seem to be merged with multiple locations in different parts of Canada (each place has multiple names), and the addresses also seem to be merged with multiple postal addresses (each postal address has multiple provinces and street addresses etc. It looks like entities are using the same URI resulting in properties from different clients getting merged.

For example: https://spektrix.com/place/201AGBHDRLQHNHPHKKMPKLGPMDRDTDMVL is the same URI for places across Canada such as Capitol Theatre, Edward Johnson Building, Gateway Theatre, Kay Meek Arts Centre and 10 more.

Another: http://www.spektrix.com/3801ASGTBTNRHGNPMLKSSVHJGBQVLLHNM is an event with the same URI across multiple clients.

dev-aravind commented 1 month ago

@saumier This was caused because Spektrix uses the same IDs for different entities across calendars.

For example the event https://system.spektrix.com/gatewaytheatre/api/v3/events/9001AGHDBMPJDRPSRMKLRCJGBJJMTQGDH in gatewaytheatre and https://system.spektrix.com/centaurtheatre/api/v3/events/9001AGHDBMPJDRPSRMKLRCJGBJJMTQGDH in centaurtheatre have the same id, but they are different events.

I have solved this temporarily by adding the source name to the URIs of events and places. Please review this and let me know what you think. Thanks.

saumier commented 4 weeks ago

@dev-aravind Yes. Adding the client id to each of the URIs for places and events is a good approach. Doing this consistently across all of Spektrix clients is a good way to create a "name space" and ensure that the URIs are unique across all their clients.