Features/Sharing Journal Entries Via School Server - Revision history

Ajay Garg: Replaced content with "Please see http://wiki.sugarlabs.org/go/Features/Transfer_to_many_options"

2012-09-04T07:51:12Z

Replaced content with "Please see http://wiki.sugarlabs.org/go/Features/Transfer_to_many_options"

Ajay Garg at 07:47, 4 September 2012

2012-09-04T07:47:08Z

← Older revision		Revision as of 03:47, 4 September 2012
Line 48:		Line 48:
	* '''Nitika Mangal''' ''nitika@activitycentral.com''		* '''Nitika Mangal''' ''nitika@activitycentral.com''
	** Testing		** Testing









	== Example Workflow for Peer-To-Peer Mode ==		== Example Workflow for Peer-To-Peer Mode ==

Ajay Garg: /* Credits */

2012-09-04T07:46:35Z

Credits

← Older revision		Revision as of 03:46, 4 September 2012
Line 43:		Line 43:

	* '''Ruben Rodriquez''' ''ruben@activitycentral.com''		* '''Ruben Rodriquez''' ''ruben@activitycentral.com''
	*** Feedback on the "peer-to-peer" mechanism; now when the user clicks "Access Share", the user is directly taken to the newly mounted remote-share view.		** Feedback on the "peer-to-peer" mechanism; now when the user clicks "Access Share", the user is directly taken to the newly mounted remote-share view.

Ajay Garg: /* Credits */

2012-09-04T07:46:16Z

Credits

← Older revision		Revision as of 03:46, 4 September 2012
Line 35:		Line 35:
	* '''Anish Mangal''' ''anish@activitycentral.com''		* '''Anish Mangal''' ''anish@activitycentral.com''
	** Showed why simply accessing the webdav shares via "Browse" activity won't work.		** Showed why simply accessing the webdav shares via "Browse" activity won't work.
	** The reason is that accessing Sugar-WebDAV shares via "Browse" (or in any browser), would show only the availability of files. But Sugar-entry ~~are~~ more than just the (data) file; it is a combination of		** The reason is that accessing Sugar-WebDAV shares via "Browse" (or in any browser), would show only the availability of files. But a Sugar-entry is more than just the (data) file; it is a combination of
	*** Metadata-file		*** Metadata-file
	*** Data-file		*** Data-file

Ajay Garg: /* Credits */

2012-09-04T07:45:49Z

Credits

← Older revision		Revision as of 03:45, 4 September 2012
Line 27:		Line 27:
	* '''Ceibal'''		* '''Ceibal'''
	** For supporting this feature development.		** For supporting this feature development.
	* '''Sascha Silbe''' silbe@activitycentral.com

			* '''Sascha Silbe''' ''silbe@activitycentral.com''
	** Initial Proposal for the solution based on WebDAV.		** Initial Proposal for the solution based on WebDAV.
	* '''Anish Mangal''' anish@activitycentral.com

			* '''Anish Mangal''' ''anish@activitycentral.com''
	** Showed why simply accessing the webdav shares via "Browse" activity won't work.		** Showed why simply accessing the webdav shares via "Browse" activity won't work.
	** The reason is that accessing Sugar-WebDAV shares via "Browse" (or in any browser), would show only the availability of files. But Sugar-entry are more than just the (data) file; it is a combination of		** The reason is that accessing Sugar-WebDAV shares via "Browse" (or in any browser), would show only the availability of files. But Sugar-entry are more than just the (data) file; it is a combination of
Line 36:		Line 40:
	*** Preview-file (optional)		*** Preview-file (optional)
	** Also, the current workflow conforms to the sugar look-and-feel too. (Thanks again Anish).		** Also, the current workflow conforms to the sugar look-and-feel too. (Thanks again Anish).
	* '''Ruben Rodriquez''' ruben@activitycentral.com

			* '''Ruben Rodriquez''' ''ruben@activitycentral.com''
	*** Feedback on the "peer-to-peer" mechanism; now when the user clicks "Access Share", the user is directly taken to the newly mounted remote-share view.		*** Feedback on the "peer-to-peer" mechanism; now when the user clicks "Access Share", the user is directly taken to the newly mounted remote-share view.
	* '''Nitika Mangal''' nitika@activitycentral.com

			* '''Nitika Mangal''' ''nitika@activitycentral.com''
	** Testing		** Testing

Ajay Garg: /* Credits */

2012-09-04T07:44:43Z

Credits

← Older revision		Revision as of 03:44, 4 September 2012
Line 25:		Line 25:

	== Credits ==		== Credits ==
	* Ceibal		* '''Ceibal'''
	** For supporting this feature development.		** For supporting this feature development.
	* Sascha Silbe		* '''Sascha Silbe''' silbe@activitycentral.com
	** Initial Proposal for the solution based on WebDAV.		** Initial Proposal for the solution based on WebDAV.
	* Anish Mangal		* '''Anish Mangal''' anish@activitycentral.com
	** Showed why simply accessing the webdav shares via "Browse" activity won't work.		** Showed why simply accessing the webdav shares via "Browse" activity won't work.
	** The reason is that accessing Sugar-WebDAV shares via "Browse" (or in any browser), would show only the availability of files. But Sugar-entry are more than just the (data) file; it is a combination of		** The reason is that accessing Sugar-WebDAV shares via "Browse" (or in any browser), would show only the availability of files. But Sugar-entry are more than just the (data) file; it is a combination of
Line 36:		Line 36:
	*** Preview-file (optional)		*** Preview-file (optional)
	** Also, the current workflow conforms to the sugar look-and-feel too. (Thanks again Anish).		** Also, the current workflow conforms to the sugar look-and-feel too. (Thanks again Anish).
	** Ruben Rodriquez		* '''Ruben Rodriquez''' ruben@activitycentral.com
	*** Feedback on the "peer-to-peer" mechanism; now when the user clicks "Access Share", the user is directly taken to the newly mounted remote-share view.		*** Feedback on the "peer-to-peer" mechanism; now when the user clicks "Access Share", the user is directly taken to the newly mounted remote-share view.
			* '''Nitika Mangal''' nitika@activitycentral.com
			** Testing





	== Example Workflow for Peer-To-Peer Mode ==		== Example Workflow for Peer-To-Peer Mode ==

Ajay Garg at 07:43, 4 September 2012

2012-09-04T07:43:11Z

← Older revision		Revision as of 03:43, 4 September 2012
Line 18:		Line 18:
	**** XOs are connected to the different Access Points (as long as school-server is pingable throughout).		**** XOs are connected to the different Access Points (as long as school-server is pingable throughout).
	**** XOs are conencted to Adhoc-Network (as long as school-server is pingable throughout).		**** XOs are conencted to Adhoc-Network (as long as school-server is pingable throughout).






			== Credits ==
			* Ceibal
			** For supporting this feature development.
			* Sascha Silbe
			** Initial Proposal for the solution based on WebDAV.
			* Anish Mangal
			** Showed why simply accessing the webdav shares via "Browse" activity won't work.
			** The reason is that accessing Sugar-WebDAV shares via "Browse" (or in any browser), would show only the availability of files. But Sugar-entry are more than just the (data) file; it is a combination of
			*** Metadata-file
			*** Data-file
			*** Preview-file (optional)
			** Also, the current workflow conforms to the sugar look-and-feel too. (Thanks again Anish).
			** Ruben Rodriquez
			*** Feedback on the "peer-to-peer" mechanism; now when the user clicks "Access Share", the user is directly taken to the newly mounted remote-share view.

Ajay Garg at 07:31, 4 September 2012

2012-09-04T07:31:23Z

@@ Line 18: / Line 18: @@
 **** XOs are connected to the different Access Points (as long as school-server is pingable throughout).
 **** XOs are conencted to Adhoc-Network (as long as school-server is pingable throughout).
@@ Line 387: / Line 388: @@
 == [DOWNLOAD] Ensure that in the detail view, the uploader-details are present. ==
 :[[File:sss12.png|640px]]

Ajay Garg at 07:23, 4 September 2012

2012-09-04T07:23:05Z

@@ Line 12: / Line 12: @@
-**Via School-Server
+**Via-School-Server mode
 *** In this mode, an XO uploads an entry to the central School Server; from where the client XO(s) may download the entry.
 *** This mode of sharing works as long as the School-Server is HTTP-pingable between the server and client XOs. Thus, this mode of sharing would work when
@@ Line 214: / Line 214: @@
 == [UPLOAD] Initially, no entries are present on the school-server. ==
 :[[File:sss1.png|640px]]
@@ Line 226: / Line 245: @@
 == [UPLOAD] Choose an entry to upload to the school-server. ==
 :[[File:sss2.png|640px]]
@@ Line 235: / Line 258: @@
 == [UPLOAD] Enter the pasphrase when prompted. ==
 :[[File:sss3.png|640px]]
@@ Line 244: / Line 271: @@
 == [UPLOAD] After uploading, ensure that the entry has in fact been uploaded to the school-server. ==
 :[[File:sss4.png|640px]]
@@ Line 253: / Line 284: @@
 == [DOWNLOAD] Initial "Documents" view. ==
 :[[File:sss5.png|640px]]
@@ Line 262: / Line 297: @@
 == [DOWNLOAD] Choose to copy the entry from school-server, to "Documents". ==
 :[[File:sss6.png|640px]]
@@ Line 272: / Line 311: @@
 == [DOWNLOAD] Enter (incorrect) password. ==
 :[[File:sss7.png|640px]]
@@ Line 280: / Line 326: @@
 == [DOWNLOAD] 'Passphrase not match' error occurs. ==
 :[[File:sss8.png|640px]]
@@ Line 288: / Line 343: @@
 == [DOWNLOAD] Try copying again. ==
 :[[File:sss9.png|640px]]
@@ Line 296: / Line 359: @@
 == [DOWNLOAD] Enter (correct) password. ==
 :[[File:sss10.png|640px]]
@@ Line 305: / Line 373: @@
 == [DOWNLOAD] Confirm that the entry has been successfully downloaded. ==
 :[[File:sss11.png|640px]]

Ajay Garg at 07:17, 4 September 2012

2012-09-04T07:17:47Z

← Older revision		Revision as of 03:17, 4 September 2012
Line 27:		Line 27:


	== ~~TERMINOLOGIES~~ ==		== NOTES ==
	*'''Local Shares'''
	** An entry present in "Local Shares", is available to other peers, when the peer(s) mount this XO's shares.		** An entry present in "Local Shares", is available to other peers, when the peer(s) mount this XO's shares.
	** Note that the entries present in "Local Shares", have nothing to do with the entries present in "School Server Shares".		** Note that the entries present in "Local Shares", have nothing to do with the entries present in "School Server Shares".
			** In the following screenshots' example, "PEER 2" mounts the shares of "PEER 1"; and uses that to copy entries onto its own XO. Thus, the entry is copied from XO-of-PEER-1 to XO-of-PEER-2.