You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We intend to avoid providing the same_as functionality in the existing API by removing all duplicates as described here: #5845
This functionality is currently provided by the recorder service in the concepts-pipeline repository. We should create a new service and ES index in the catalogue-pipeline repository intended to replace the existing service.
We will need a mechanism to keep the ES index up to date with the latest changes in the catalogue pipeline but this could be a regular batch load rather than an event based approach.
This may also be an opportunity to use the Serverless Elasticsearch offering to provide our ES index.
The scope of this ticket is to reproduce only existing functionality and not yet expose additional concept relationships present in the graph database.
The text was updated successfully, but these errors were encountered:
Moving towards replacing the existing concepts-pipeline we need a service that does the job of loading catalogue-pipeline identified concepts into an elasticsearch index in a way that supports re-implementing API responses like this: https://api.wellcomecollection.org/catalogue/v2/concepts/vk6nj4mt
We intend to avoid providing the
same_as
functionality in the existing API by removing all duplicates as described here: #5845This functionality is currently provided by the
recorder
service in the concepts-pipeline repository. We should create a new service and ES index in the catalogue-pipeline repository intended to replace the existing service.We will need a mechanism to keep the ES index up to date with the latest changes in the catalogue pipeline but this could be a regular batch load rather than an event based approach.
This may also be an opportunity to use the Serverless Elasticsearch offering to provide our ES index.
The scope of this ticket is to reproduce only existing functionality and not yet expose additional concept relationships present in the graph database.
The text was updated successfully, but these errors were encountered: