Lineage between model and source code breaks on movement of source notebook. How to rectify it?

Maverick1
Valued Contributor II

If there is a registered model and it is linked with a notebook, then the lineage breaks if you move the notebook to a different path or even pull/upload a new version of the notebook.

This is not good because when someone doing its development/testing they usually do it in a messy way but if you need your code in production then it means that either

  1. You need to move your code and then again re-train to generate the same model and then perform its movement to higher env. so that the lineage is maintained.... or
  2. You need to keep the dev source code notebook, that too on the same path, where it had been created for dev usage.