Arvados

There are lots of details to work out, but the gist is:

• If the user's workflow argument is not in any currently supported format, search for registered workflows in the system with that name.
• If there is more than one match, maybe fail with a message that lists project names+UUIDs for a limited number of the most recent matching workflows (just one idea, open to discussion)
• With exactly one match, act as though the user provided that workflow's UUID.
• With zero matches, fail with a message saying no workflow was found with that name.

The idea is, in more managed environments, workflow names should be standardized and avoid conflicts. When that's true, users are more likely to remember workflows by name than any identifier.

It would be cool if you could narrow the search with metadata. The next obvious thing to do is to let the user specify a workflow version that is matched against arv:gitDescribe. But this is less standardized so we might need more thought about how to build that part of the search.