New feature: add a toggle for datasets which users could use to say "private to space" or "public". Also, allow making an entire project space (meaning all datasets and files in the project space) public (like the Washtenaw Parks and Rec. Commission has done in 1.5).

— User story below and Acceptance Criteria —

As a researcher working in a team on SEAD, I want to make all or subsets of our project space's data public so that others can access them without us having to formally publish them.

Acceptance Criteria:
1. The default public/private status of data in a space is determined by public/private status of the project space. If the project space is in trial mode, all data can only ever be private to the space (ie only accessible to project space members).

2. By default (meaning, if the team/user does nothing to set the space or the datasets within it), all project spaces' data are private to the project space. An administrator can choose to make all of a project space's data public or private through the "edit space" page.

3. A project space user, in an administrator or editor role in that project space, can change the status of a dataset to be accessible to project space members only or to public (where public means non logged-in users as well as SEAD users that are logged in but not members of the project space in question).

4. Both new and existing datasets follow the project space setting for access; meaning that if I, as an admin, switch my project space to public, all the datasets I created before and all I create going forward are public. This holds only if access has not been specified already at the dataset level. If access has already been set at the dataset level, any changes to the access of the project space as a whole are ignored for those datasets. Admins and editors can change the status of a dataset to override the project space setting.

5. There is a clear statement on the dataset page and on the files contained within a dataset on whether it's public or private to the space.

6. Public datasets appear within search results, within the social tag list, within the Project Space landing page (such a public view does not yet exist but is a requirement of 2.0), and on the "Public Data" page under the Explore tab in the top navigation (see SEAD-1022 for more information on the new top navigation). Users do not need to be logged in to see these things.

7. Public users (by which we mean both non-logged in users AND logged in users who are not part of the project space) have viewer capabilities for datasets that are public (either by virtue of the project space or dataset setting).

8. On the landing page for a Project Space, make a heading (same style as External Links) "Project Space Stats." Underneath it, have the following fields
Members: [number of members]
Datasets: [number of datasets]
Collections: [number of collections]

Dependencies:
Dataset can only be in one space CATS-562.
Collection/subcollection can only be in one space( which task? it is part of CATS-562?)
trial space SEAD-1004

Questions for Discussion and their Resolution (taken from the comments below):
Question: What about curation objects? they are private to space users no matter public/private of the space and its live object?’
Answer: COs should be independent of this mechanism/not affected by it.

Question: Should there be a way for users to set a dataset back to unset (so it inherits the space setting again)?
Answer: Yes (Dharma initially said no, but on further thought it seems like a good idea to allow this)

Question: What about the preview & comment & metadata for datasets/files? – all follow the status of dataset & file?
Answer: yes.

Question: How to deal with collections?
Answer: Collections should follow the space default w/o having an override like we have for datasets. Meaning if a space is public, all users see the collection name and its metadata. Access to the individual datasets (including seeing their titles) depends on setting of the datasets in the collection.

Question: so you mean the status for dataset should have – private & public & unset — three status right?
Answer: yes, and the unset obeys the setting of the project space.

Question: what for space? "private & public & unset" or just "private & public"?
Answer: Private and public with private being default until changed by the admin of the space.