Event type taxonomy mapping to Artsdata Event types

[saumier]

As an admin of the CMS, when I create a taxonomy, I want to be able to map "sameAs" each concept to another vocabulary. Specifically, I want to map my event types to Artsdata event types. This is important for me because I want to contribute to Artsdata and without a mapping to Artsdata Event Types the events cannot be reused on sites like LaVitrine that want Artsdata event types.

In the interim, @tammy-culture can create an excel sheet that maps CMS concept IDs to Artsdata event type URIs so we can load the mapping directly into Artsdata from the Github repo artsdata-planet-culture-mauricie

[saumier]

@troughc I documented this user story for Tammy. For a sense of priority please speak with her ;-)

[troughc]

This feature is not priortized because we have a workaround to deal with onboarding new clients. Aiming to do in 2024, timing TBD. In the meantime, let's get our high-level analysis done. cc @tammy-culture @saumier

Requirements to achieve this feature:

What design is needed?

Taxonomies would need to be updated - each taxonomy (and it's concepts) needs a "section" for mapping. In the section:

1. User needs to be able to create a mapping from a selected source (website's) related taxonomy (with it's concepts) to the CMS calendar's current taxonomy's concepts. (the taxonomy the user is looking at)
2. User needs to be able to create same type of mapping from the CMS calendar to Artsdata concepts
3. User needs to be able to map multiple concepts to multiple or single concept and vice versa. Needs this flexibility to decide how to map.
4. User needs to be able to add concepts to their own taxonomy as needed.
5. Anything else?

What backend work is required?

@sahalali please help answer this question. After you are done, please assign to me. @tammy-culture will provide the spreadsheet separately for Mauricie to the DEV team (for onboarding the client)

[sahalali]

@troughc What I understand from this is, that mapping between Artsdata concepts and Footlight concepts needs to be done. Correct me if I am wrong

I like this idea so that in the future we can filter events by a common taxonomy across calendars.

Here are the backend changes required.

1. Add support to persist sameAs (should be a list) for concepts. (UI change will be required to let the user enter this info).
2. Update eventListing, eventDetails, placeListing,placeDetails. GET APIs for all entities to include sameAs value in their responses.
3. Footlight aggregator: Add support to updateTaxonomies by CSV files (for bulk update).

Estimation: 16 H

[saumier]

@sahalali Thanks for the estimate. Looks good. There may also be some API changes to include concept sameAs in the Organization and Person entities.

@troughc I am assigning back to you for the Figma part of this feature. It will be needed for the front-end estimate.

[troughc]

Update: Aiming to design the feature in FIGMA in February. At the same time, we can add the button for loading a default taxonomy.