Summary

• Page properties (3 modified, 0 added, 0 removed)

Details

Page properties

Parent

...	...	@@ -1,1 +1,1 @@
1		-Collabs.the-collaboratory.WebHome
	1	+Collabs.collab-devs.WebHome

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.chaney08
	1	+XWiki.mmorgan

Content

...	...	@@ -9,7 +9,7 @@
9	9
10	10	Just as for the Drive, files stored in the Bucket of a collab all have the same collab-wide permissions. Some users of the collab Team have read access, others have write access, but there are no specific permissions to individual files or folders.
11	11
12		-The bucket of a public collab is not visible to visitors without an EBRAINS account nor to users that are not a member of the Team of the collab.
	12	+The bucket of a public collab is not visible to visitors without an EBRAINS account (% style="background-color:#f1c40f" %)nor to users that are not a member of the Team of the collab(%%).
13	13
14	14	Buckets support a public link feature. An editor or admin of a collab can create a public link to a file in a bucket of the collab to share the file beyond the members of the collab.
15	15
...	...	@@ -19,7 +19,7 @@
19	19	* videos
20	20	* large IT images, although EBRAINS has a self-hosted Docker registry which is better suited for that specific use case than the Bucket service
21	21
22		-Users can access these Bucket files programmatically (e.g. via Jupyter Notebooks) by using the [[bucket API>>doc:Collabs.collab-devs.Documentation Bucket.API.WebHome]].
	22	+Users can access these Bucket files programmatically (e.g. via Jupyter Notebooks) by using the [[bucket API>>doc:.API.WebHome]].
23	23
24	24	=== Bucket vs Drive ===
25	25
...	...	@@ -36,4 +36,5 @@
36	36	* Office file types can be opened for online collaborative editing with the Collaboratory Office service directly from the Drive.
37	37	* Access from a Jupyter notebook can be performed without importing any library/package.
38	38
	39	+
39	39