Arvados

arv-copy does accept collection PDHs. --help could be clearer about this.

•      copy_opts.add_argument(
           'object_uuid',
  -        help='The UUID of the object to be copied.')
  +        help='The UUID (or portable data hash) of the object to be copied.')
  

My 2 cents: In a collection page, we refer to the pdh as a "Content address", I think we should be consistent here and say "Content address". PDH works for me too, I'm just being nitpicky.

Bryan's comment pokes at a terminology tension here we haven't fully resolved. Most of Arvados refers to this consistently as a "portable data hash." But when we made the relevant Workbench changes, we were very specifically requested to call it "content address."

"Portable data hash" is a term specific to Keep manifests that has a very precise meaning. "Content address" is a general concept that most of our users can grok after just a sentence or two of explanation. A collection's portable data hash serves as a content address for it, but if you try to generate it the same way you generate content addresses for individual Keep data blocks, you'll be disappointed.

I think the number of people who need to know how to generate portable data hashes is comparatively small enough that we should prefer "content address" in all UIs, so I'd vote with Bryan. But maybe we should have that general conversation and at least figure out some basic rules of what term gets used when.