Discussion: New action called `copy`
We've been talking to the FabCity people about integrating git and vf, specifically using git activity on design information stored in git to trigger vf activity. We've never done a git software use case either.
This brought up a potential new action, which would support things like fork, clone, branch. Basically it is a copy that creates a new resource, which is otherwise unchanged in content from the old resource. I can see potential uses for other electronic resources too, you might just want to copy a document or whatever, not stored in git.
People could do it with cite
plus a process plus produce
, but that is a lot for a simple copy that doesn't really do any transformation. It still could be appropriate for a copy that does involve other inputs or some processing that rises to the level where it wants to be recorded. But I think it would be good to have a simple action that works like transfer
or move
(has a resourceInventoriedAs and a new "to" resource, and no process) but has different behavior, i.e. it does not affect the resourecInventoriedAs, and creates a new resource for the toResourceInventoriedAs.
When tracing, it could work like a cite, i.e. credit the resource that was copied.
Thoughts are welcome! I'll also come back here, after we do some more work on the particular use cases.