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
Is your feature request related to a problem? Please describe.
Currently the knowledge-graph service maintains metadata (currently, only English-language names) for equipment (appliances, utensils, vessels) that are searchable, and it uses a directory of text files stored in source control to manage that.
Describe the solution you'd like
Relocate management of equipment-related data from the knowledge-graph service into this one. The knowledge-graph should query this service to lookup the relevant data as-needed and with a timeout expiry, similar to the way that product data is loaded from cache when possible.
This will require creation of database tables to store the equipment detail records.
Describe alternatives you've considered
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Currently the
knowledge-graph
service maintains metadata (currently, only English-language names) for equipment (appliances, utensils, vessels) that are searchable, and it uses a directory of text files stored in source control to manage that.There are some benefits to that; having history and source control is nice. However: we currently provide a management user interface for product-related data using
flask-admin
, and that'd seem the logical place to manage equipment-related data too.Describe the solution you'd like
Relocate management of equipment-related data from the
knowledge-graph
service into this one. Theknowledge-graph
should query this service to lookup the relevant data as-needed and with a timeout expiry, similar to the way that product data is loaded from cache when possible.This will require creation of database tables to store the equipment detail records.
Describe alternatives you've considered
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered: