Preserve an artifact staged status when copied / transferred across projects

[ehsanmok]

Use case

There's the immediate feature as the title describes and there a general use case of including model / artifact --name in plx models stage when there're multiple models with many versions where two models with different names can have the same version (there shouldn't be a restriction on version names between different models) and when one wants to change the status of a single one via

plx models stage -p PROJECT -n MODEL -ver rc0 -to=production

where -n I mean the artifact name (i.e. the name used in plx model register --artifact)

Alternatives

is to plx models stage again but is not possible in the global model registry where there're multiple models since plx models stage doesn't have --name corresponding to the model / artifact name.

[ehsanmok]

For the record, per many discussions, it turns out that version in FQN has a more general semantic unlike the as expected tag-like version like v1.0 and in my case, I need to append the artifact name to the version. The semantically agreed upon name:version like python:v3.10 doesn't work and one needs to leak the name to version to be like name:name-version where name is any artifact name.

So this issue can be closed.