From RD: "You can select multiple files and folders for ingest – but how would this work, as you can only input one checksum, and presumably checksums are unique to individual files. There is clearly a practical scalability issue here if users have to ingest file by file, as it would defeat the purpose of this functionality, which is to handle multiple/many-file datasets. Not sure what the workable solution is here. Can you generate at the top level checksums for all files in a container? I guess the problem is that the container is the fileshare but you need to validate against files before they are added to the fileshare – or would a desktop client fileshare be suitable for this purpose?"
From RD: "You can select multiple files and folders for ingest – but how would this work, as you can only input one checksum, and presumably checksums are unique to individual files. There is clearly a practical scalability issue here if users have to ingest file by file, as it would defeat the purpose of this functionality, which is to handle multiple/many-file datasets. Not sure what the workable solution is here. Can you generate at the top level checksums for all files in a container? I guess the problem is that the container is the fileshare but you need to validate against files before they are added to the fileshare – or would a desktop client fileshare be suitable for this purpose?"