Limit Dataset Visibility by Role

​@Jesse Jenken Good to hear that you managed to figure this out. 

Could we request the YAML reference documentation be updated?

Are you referring to this in the documentation? 
 

I am wondering the best way to improve your experience. The above documentation is referring to a threedAcl, which use a ‘datasetScope’, while you are using a datasetsAcl which use ‘idscope’. The YAML files you use with Toolkit are reflecting the API:
 

I will change Toolkit by creating a error message that checks the scopes vs the ACL you are using. In your case, when you try to create a datasetsAcl the only scopes available are the ‘all’ and ‘idscope’ which will then be reflected in the error message.

Thanks you so much for reporting. Let me know if this should be sufficient, or if there are other improvements we should make.

I am wondering the best way to improve your experience. 

Thanks Anders, the toolkit has been extremely helpful and the improvements with v3 have been very welcomed, coming from our initial 0.1.4 install.

Where I got hung up and a bit confused is the case sensitivity of the API documentation.

It speaks to one of idscope but the yaml requires idScope with a capital S.  I’m not sure how to have come to that conclusion on my own and whether that represents a deficiency in my Python skills, or if that’s enough of a misnomer on my part to suggest the value of having every YAML property explained for every type of configuration without needing to lean on the API docs.

Regardless, lesson learned, and onward we go.  Thanks for being receptive to the feedback!

The case sensitivity of the idscope/idScope is an unfortunate part of the API that cannot be changed. It is a good point that this is an easy trap, will try to improve the error message to also pick up and tell you if you use the wrong casing.