Describe the reason for these changes and the problem that they solve
Since the introduction of openculinary/backend#35, we now have a normalized relational database where we can manage product and nutritional metadata.
This removes the need for (complicated) processing and generation of product metadata from the knowledge graph; instead the service can consume the flattened product metadata in a read-only fashion.
This code was useful to bootstrap and create an initial set of product metadata; the bet placed by this set of changes is that the data is currently 'good enough' -- even though it has plenty of duplicates, flaws, and rough edges -- that migration to manual curation of the metadata will result in better outcomes than trying to proceed by further fine-tuning the automated metadata discovery algorithms.
Briefly summarize the changes
Remove product metadata generation and write operations
Prefer to read static fields from metadata on-disk (e.g. product.id) than determine them dynamically
How have the changes been tested?
Local development testing
List any issues that this change relates to
Progresses openculinary/backend#34.
Describe the reason for these changes and the problem that they solve
Since the introduction of openculinary/backend#35, we now have a normalized relational database where we can manage product and nutritional metadata.
This removes the need for (complicated) processing and generation of product metadata from the knowledge graph; instead the service can consume the flattened product metadata in a read-only fashion.
This code was useful to bootstrap and create an initial set of product metadata; the bet placed by this set of changes is that the data is currently 'good enough' -- even though it has plenty of duplicates, flaws, and rough edges -- that migration to manual curation of the metadata will result in better outcomes than trying to proceed by further fine-tuning the automated metadata discovery algorithms.
Briefly summarize the changes
product.id) than determine them dynamicallyHow have the changes been tested?
List any issues that this change relates to Progresses openculinary/backend#34.