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
COSMOS already creates templates. We need the LRM process to be aligned with the automation that exists in COSMOS, either by switching to use the automation, or by updating it to include the LRM processes.
We currently have templates being created through workflow status updates for the collections on COSMOS but are only using them to track the collections indexed, not directly using those templates to create the configs we're using and eventually merging to staging after merging webapp_config_generation.
Implementation Considerations
Analysis of the current workflow process and requirements.
Updates (if any) to the COSMOS automation.
need to meet with Carson about how to ensure control over templates
Deliverable
Incorporating the COSMOS template creation fully into the curation workflow process.
Dependencies
depends on
The text was updated successfully, but these errors were encountered:
Description
COSMOS already creates templates. We need the LRM process to be aligned with the automation that exists in COSMOS, either by switching to use the automation, or by updating it to include the LRM processes.
We currently have templates being created through workflow status updates for the collections on COSMOS but are only using them to track the collections indexed, not directly using those templates to create the configs we're using and eventually merging to staging after merging webapp_config_generation.
Implementation Considerations
Deliverable
Incorporating the COSMOS template creation fully into the curation workflow process.
Dependencies
depends on
The text was updated successfully, but these errors were encountered: