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
{{ message }}
This repository has been archived by the owner on Dec 16, 2022. It is now read-only.
...so that I can parallelize the harvest / registry-mgr execution steps, and run a separate tool / function to crawl the registry and tag collections / products with their appropriate ancestry.
Additional Details
Acceptance Criteria
Given an ingested bundle that did NOT use the harvest <bundle> config, and instead ingested each product individually When I perform some new registry-mgr / harvest / etc. function to tag the ancestors / families of the products (bundles -> collections -> products) Then I expect to be able to query for a product and get its ancestor collection and bundle. in other words, get the same result as if I ran harvest with the <bundle> config enabled.
Engineering Details
The text was updated successfully, but these errors were encountered:
Motivation
...so that I can parallelize the harvest / registry-mgr execution steps, and run a separate tool / function to crawl the registry and tag collections / products with their appropriate ancestry.
Additional Details
Acceptance Criteria
Given an ingested bundle that did NOT use the harvest
<bundle>
config, and instead ingested each product individuallyWhen I perform some new registry-mgr / harvest / etc. function to tag the ancestors / families of the products (bundles -> collections -> products)
Then I expect to be able to query for a product and get its ancestor collection and bundle. in other words, get the same result as if I ran harvest with the
<bundle>
config enabled.Engineering Details
The text was updated successfully, but these errors were encountered: