With the new security features (requiring to log in to even see datasets) how will this affect the request (by Sorin, a stakeholder from Cyprus Institute) for datasets to be searchable by search engines? Search engines surely cannot crawl protected resources- this means that in order to satisfy this requirement, the security features for viewing existing datasets will have to be disabled.

Or, even better, have the admin decide whether to enable protection for viewing existing datasets (and as a tradeoff disable search engine crawling of datasets and their metadata). How can this be done (ie via securesocial.conf)?

Another idea would be private datasets-the dataset uploader to be able to choose whether the uploaded dataset is not viewable by people/machines not logged in, even if protection for datasets viewing is disabled by the admin.

Also, editing of "open" datasets should be disabled to people/machines not logged in to prevent abuse.