Import events from Artsdata

[troughc]

Provide the Admin with the ability to import event(s) from Artsdata (not on a schedule - this is a one-off task).

User Story

As an admin of Footlight CMS, I sometimes need to import specific events (usually a short list of 1 to 12 events) from Artsdata that are not automatically loading into CMS as scheduled. I may be getting pressure from the event organizer, or the event may be starting in a couple days so I need to load the events immediately. However the events have data quality issues and may not have an Artsdata identifier (not minted) in Artsdata. Examples of data quality issues can be missing location, invalid dates, events with multiple locations on the same date, or some other validation error. Despite the errors, I still want to load as much of the event data (image, description, etc.) as possible from Artsdata so I can minimize my manual data entry.

https://www.figma.com/design/DBnSSMT9Etfm6guDKKSp8O/Culture-Creates---Footlight-Calendar?node-id=11301-80507&t=5ZAcVfIgsnjDKX36-1

Tasks

Preview Give feedback

1. Create Regression test for import events from Artsdata #1482
   +0
   
2. Import events from Artsdata: backend support #1527
   feature +1
   
3. Import events from Artsdata: frontend #1528
   +0
   

[sahalali]

Backend estimate : 16 Hrs
Add an API to fetch Artsdata entities from the CMS.
Implement support for creating an event using the Artsdata ID, and ensure that this Artsdata ID is not associated with any existing CMS event to avoid duplications.

@AbhishekPAnil Assigning to you for Frontens estimation.

[AbhishekPAnil]

Frontend estimates : 27 H

1. Add button to show dropdown options. - 0.5
2. Add the dropdown to show "Import from events" - 0.5
3. Add the modal to show import events with the fields - 5
4. Api integration to get the options for "Filter By" - 4
5. Api integration to get the "Event titles" - 4
6. Add api integration to import events - 5
7. Show the loading animation - 2
8. Show the completed animation when the import is complete - 2
9. Add routing to see the imported events - 1
10. Add the buttons for "Back to all events" and "See imported events" - 0.5
11. Testing.1-2

[troughc]

After @saumier adds the user story, @sahalali will create to sub-issues to separate BE work from FE work. We will start with BE work in iteration 2025.1.

[saumier]

@troughc Please take a look at the user story I added to check that it reflects the need. Thx.

[troughc]

@saumier story looks good. @sahalali please feel free to go ahead and create the sub issues.