Importing entities search sections

[troughc]

In all workspaces except Events (people, places, orgs), there are 3 sections when importing an entity, i.e. users can import an entity from Artsdata or from another footlight listing
(In Events, we do not include "Import from Footlight" because users are only allowed to import events from Artsdata.)

However, we push these entities to Artsdata from Footlight on a schedule. Notice in the screenshot above:

• entities in Artsdata have a disambiguating description to name the source (if it's a datafeed source) or whatever the disambiguating description is (if the source is a minted Artsdata entity).
• Entities in "Import from Footlight" have no label/description so the user doesn't know where exactly what listing come from.
• Also, the entities in "Import from Footlight" are duplicated in "Import from Artsdata" (where the source is named and the blue link is labeled 'datafeed' rather than 'Artsdata')

According to Gregory, the plan is to eventually be able to eliminate the 'datafeed' sources from the dropdown - when the core data updates to include all enriching information from datafeeds. However, for now, some users want access to those datafeed versions of events (aka Signe Laval)

I want to improve this both short term and long term.

In the short term:

• stop displaying the section 'import from Footlight' and make sure we export data from Footlight to Artsdata often so that users have access to all datafeeds in the Artsdata section.

In the long term

• In preparation for long term, add a description to Import from Footlight entities naming where they are coming from.
• only display entities in "Import from Footlight" that have been modified by a user after being imported from Artsdata (if they are not modified, they would be identical to what is available in Artsdata)
• Decide if we should display events that are manually created in another footlight listing in the list.

To discuss further.

cc @AbhishekPAnil

[devnandan-cc]

Import Entities Search Section.

Current Objective : To import an entity from Artsdata or from another Footlight.

Objective of the proposed improvement : To import an entity from Artsdata or from another Footlight without duplication, which occurs when entities are pushed from Footlight to Artsdata.

When the core data updates to include all enriching information from datafeeds, the architecture can be modified to make Import from Footlight section to contain only the events from another Footlight and Import from Artsdata will have entities from core graph.

But the time frame that occurs till the completion of this process has to be handled with a short term approach where the Imports from Footlight section has to be removed and Import From Artsdata will be preserved to display both the Artsdata entities and entities from Footlight exported to Artsdata.

This includes a potential risk of a Footlight entity created after the last export being missing in Artsdata until the next run.
This is an accepted trade-off of the short-term approach.

Taking things into consideration, the short-term approach implementation plan is,

1. The switch case to fetch FootLight Source in the API is removed, returns an empty array for Footlight source.

2. The Footlight section creates a gap where recently created Footlight entities aren't yet visible in Artsdata search.
   This can be made less impactful with increasing export schedule frequency.

@suhail-aliyar Please read the implementation and confirm.