| %s | |||
| %s | |||
| %s.%s | ' % ( str( i+1 ), name ) ) + out.append( '%s.%s | ' % ( str( i + 1 ), name ) ) # This data type requires at least 11 columns in the data if dataset.metadata.columns - len( self.column_names ) > 0: for i in range( len( self.column_names ), dataset.metadata.columns ): - out.append( '%s | ' % str( i+1 ) ) + out.append( '%s | ' % str( i + 1 ) ) out.append( '
|---|
The menu on the left provides the following features
-Data Security and Data Libraries
- - Security - Data security in Galaxy is a new feature, so familiarize yourself with the details which can be found - here or in our data security page. The data security - process incorporates users, groups and roles, and enables the application of certain permissions on datasets, specifically "access" - and "manage permissions". By default, the "manage permissions" permission is associated with the dataset owner's private role, and - the "access" permission is not set, making the dataset public. With these default permissions, users should not see any difference - in the way Galaxy has behaved in the past. -- If no roles with the "access" permission are associated with a dataset, the dataset is "public" and may be accessed by anyone - that can access the data library in which it is contained. See the Manage data libraries section above for - details. Public datasets contained in public data libraries will be accessible to all users (as well as anyone not logged in - during a Galaxy session) from the list of data libraries displayed when the "Data Libraries" menu item is selected. -
-- Associating a dataset with a role that includes the "access" permission restricts the set of users that can access it. - For example, if 'Role A' includes the "access" permission and 'Role A' is associated with the dataset, only those users - and groups who are associated with 'Role A' may access the dataset. -
-- If multiple roles that include the "access" permission are associated with a dataset, access to the dataset is derived - from the intersection of the users associated with the roles. For example, if 'Role A' and 'Role B' are associated with - a dataset, only those users and groups who are associated with both 'Role A' AND 'Role B' may access the dataset. When - the "access" permission is applied to a dataset, Galaxy checks to make sure that at least 1 user belongs to all groups and - roles associated with the "access" permission (otherwise the dataset would be restricted from everyone). -
-- In order for a user to make a dataset private (i.e., only they can access it), they should associate the dataset with - their private role (the role identical to their Galaxy user name / email address). Associating additional roles that - include the "access" permission is not possible, since it would render the dataset inaccessible to everyone. -
- To make a dataset private to themselves and one or more other users, the user can create a new role and associate the dataset - with that role, not their "private role". Galaxy makes this easy by telling the user they are about to share a private dataset - and giving them the option of doing so. If they respond positively, the sharing role is automatically created for them. -
-- Private data (data associated with roles that include the "access" permission) must be made public in order to be used - with external applications like the "view at UCSC" link, or the "Perform genome analysis and prediction with EpiGRAPH" - tool. Being made publically accessible means removing the association of all roles that include the "access" permission - from the dataset. -
-