Aggregator enhancement: Sources filtered by taxonomy criteria

[MaudeFJ]

User story

Signe Laval would like to import (using an aggregator) certain events from the La Vitrine source in Artsdata. The events in question would be a filtered subset of the La Vitrine events, the ones that feature Lavallois artists. In other words the La Vitrine aggregator from Artsdata would only include events with Lavallois artists performing.

Your 'La Vitrine' aggregator would only include events that meet this criteria: -performed by "lavallois artist" The Signe Laval CMS would be the source of the latest list of Lavallois artists (people and organizations) via these 2 taxonomies used in people/orgs: Orgs: Ville de l'organisation People: Lieu de travail NOTE: the names of the taxonomies are subject to change. These taxonomies are used to identify which people/Organizations in the Signe Laval CMS are Lavallois. So this information would have to be available to identify which events to import from Artsdata.

Could we automate entry of lavallois artist event's that are in arts data in my cms ? Like if Adam Jonhson as an event at la place des arts it can enter straight up in brouillon in my cms !

[troughc]

@MaudeFJ does this capture what you want? Signe Laval would like to import (using an aggregator) certain events from the La Vitrine source in Artsdata. The events in question would be a filtered subset of the La Vitrine events, the ones that feature Lavallois artists. In other words the La Vitrine aggregator from Artsdata would only include events with Lavallois artists performing.

Your 'La Vitrine' aggregator would only include events that meet this criteria:

• performed by "lavallois artist"

Signe Laval would provide the list of Lavallois artists (people and organizations).

[MaudeFJ]

Yes ! But Ideally we would not have to provide a list of lavallois artist, because this info would be embed with the people and organization already in arts data since i'm already putting it in the cms !

[troughc]

But Ideally we would not have to provide a list of lavallois artist, because this info would be embed with the people and organization already in arts data since i'm already putting it in the cms ! Yes, that is what I meant. The Signe Laval data includes the taxonomy that identifies a lavallois.

Thanks for the user story.

[troughc]

@MaudeFJ please take a look at the first comment again to see if it makes sense. if yes, just give me a thumbs up. :)

[troughc]

@sahalali let's discuss this and what it would entail in terms of development.

[MaudeFJ]

Yes well explain About the taxonomie Orgs: Ville de l'organisation People: Lieu de travail I will change lieu de travail for Ville de résidence because some artists were confuse

[sahalali]

If I understand correctly, the aggregator should be able to configure a source (a workflow) to import only events "performed by" a set of people with matching property 'Lieu de travail' value or organization with matching property 'Ville de l'organisation' value in the CMS.

Design: Step 1: Fetch all people and organizations that match a given condition in the configuration file (now called the mapping file). The aggregator should be able to fetch a list of people and organizations from the CMS. Step 2: Iterate events fetched from CMS as of today and skip those events that do not match the condition (in this case "performed by") in the configuration file.

This will take 3 days of effort to implement and test.

[sahalali]

@troughc Please check the estimate and prioritize.