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
Given issues addressed by @LilyAndres in #113 (comment), I propose we add a deprecated or obsolete term robot template similar to this one from OBI that'd be integrated into the workflow so that we have one single place to deprecate terms and the changes actually stick after re-running the entire build workflow.
Should be a fairly simple template with a few columns: one for the ID and another couple for obsolescence metadata e.g. from the OBI template:
The alternative would be to add the relevant obsolescence fields directly into the existing templates which would work for robot templates but not for the concentration DOSDP, so I think a new obsolete template maybe best.
The text was updated successfully, but these errors were encountered:
Hey @kaiiam thanks for your on this, I have prepared a template based on the one you share from OBI. Could you please have a look and see if this is ok? I would really appreciate it, I save the template in google drive in the following link
Given issues addressed by @LilyAndres in #113 (comment), I propose we add a
deprecated
orobsolete
term robot template similar to this one from OBI that'd be integrated into the workflow so that we have one single place to deprecate terms and the changes actually stick after re-running the entire build workflow.Should be a fairly simple template with a few columns: one for the ID and another couple for obsolescence metadata e.g. from the OBI template:
The alternative would be to add the relevant obsolescence fields directly into the existing templates which would work for robot templates but not for the concentration DOSDP, so I think a new obsolete template maybe best.
The text was updated successfully, but these errors were encountered: