Question: should we implement these? Doing so would require 6 new functions:
show_all_collections() and search_collections()
show_all_datasets() and search_datasets()
show_all_providers() and search_providers()
Although 6 new functions is a lot to add, the fact that they expand on existing syntax (i.e. show_all_ and search_) should mitigate the added complexity to some degree. However, the challenge here is that it may not be clear to users what the differences are between collections, providers, or data resources, and therefore which function they should use. We would also need to be clear about how to use this information in practice; i.e. what the resulting call to galah_filter() would look like.
At present, there is no way to get information on collections, providers, or data resources in R. However, the APIs are fairly straightforward;
Question: should we implement these? Doing so would require 6 new functions:
show_all_collections()andsearch_collections()show_all_datasets()andsearch_datasets()show_all_providers()andsearch_providers()Although 6 new functions is a lot to add, the fact that they expand on existing syntax (i.e.
show_all_andsearch_) should mitigate the added complexity to some degree. However, the challenge here is that it may not be clear to users what the differences are between collections, providers, or data resources, and therefore which function they should use. We would also need to be clear about how to use this information in practice; i.e. what the resulting call togalah_filter()would look like.