Just wondering out loud if disabling the s3 listBucket operation will affect other methods developed to work with the buckets (FSx, for example, was next on my list of things to look into). Using a more visually intuitive presentation of the manifest to peer into the organization of one’s package seems a lot simpler and lightweight for arranging any read/write calls.
In case anyone else out there wants to try…to easily grab the s3 prefixes for an HCP package, I’ve used the downloadcmd python script from the command line:
- create a package (without associated files) using NDA query tool and instructions,
- pip install nda-tools,
- run “downloadcmd 1234568 -dp -u username -p password -d /place/you/want/your/manifest” and wait for results.
- Find the file that has ‘manifest’ in its name.
- See the S3 links for all of the data in your package.
- See that behavioral data (if you included this in your package) is a the root of the download directory and not along a S3 link.
I look forward to gaining the datalad intuition to appropriately wrap this process into a well annotated research object.