[SDKs] Document that arv-copy accepts collection PDHs (ie content addresses) as arguments
#4 Updated by Brett Smith over 4 years ago
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.
#7 Updated by Tom Morris almost 4 years ago
- Subject changed from [SDKs] Document that arv-copy accepts collection PDHs as arguments to [SDKs] Document that arv-copy accepts collection PDHs (ie content addresses) as arguments
- Story points set to 0.5
Does anyone disagree with using "Content Address" here? That term sounds good to me for this type of usage.