Features/Transfer to many options



Basic Usage

 * This feature helps share Journal/Documents/Mounted-Drives' entries across XOs, via the following two mechanisms ::


 * Peer-to-Peer mode
 * Sharing in this mode is possible, only when the server and client XO(s) are on the same networks. Thus, peer-to-peer sharing would work on
 * XOs connected to the same Access Point.
 * Adhoc-Network connections.


 * 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
 * XOs are connected to the same Access Point (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).

Credits

 * Plan Ceibal
 * For supporting this feature development.


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


 * Anish Mangal anish@activitycentral.com
 * 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 a Sugar-entry is 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 Rodriguez 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.


 * Nitika Mangal nitika@activitycentral.com
 * Testing


 * David Rodriguez daroal@activitycentral.com
 * Testing

[PEER 1] "Journal" - View.

 * p11.png

[PEER 1] Detail view of the journal-entry. Note the preview presence.

 * p12.png

[PEER 1] Initial "Local Shares" View

 * p13.png

[PEER 1] Copy the journal entry to "Local Shares", to make it available for sharing to other peers.

 * p14.png

[PEER 1] "Local Shares" view, after copying the entry.

 * p15.png

[PEER 1] The detail view in "Local Shares". NOTE that the preview MUST be present, and it must be same as that of "Journal".

 * p16.png

[PEER 2] Initial "Journal" - View.

 * p20.png

[PEER 2] Neighborhood View.

 * p21.png

[PEER 2] Click on "Access Share" of the peer, whose shares need to be accessed.

 * p22.png

[PEER 2] The peer's shares are mounted.

 * p23.png

[PEER 2] Copy the entry to the journal.

 * p24.png

[PEER 2] Final "Journal" View.

 * p25.png

[PEER 2] Detail-view of the entry. Note that the preview is the same as was on the remote peer.

 * p26.png

[UPLOAD] Initially, no entries are present on the school-server.

 * sss1.png

[UPLOAD] Choose an entry to upload to the school-server.

 * sss2.png

[UPLOAD] Enter the pasphrase when prompted.

 * sss3.png

[UPLOAD] After uploading, ensure that the entry has in fact been uploaded to the school-server.

 * sss4.png

[DOWNLOAD] Initial "Documents" view.

 * sss5.png

[DOWNLOAD] Choose to copy the entry from school-server, to "Documents".

 * sss6.png

[DOWNLOAD] Enter (incorrect) password.

 * sss7.png

[DOWNLOAD] 'Passphrase not match' error occurs.

 * sss8.png

[DOWNLOAD] Try copying again.

 * sss9.png

[DOWNLOAD] Enter (correct) password.

 * sss10.png

[DOWNLOAD] Confirm that the entry has been successfully downloaded.

 * sss11.png

[DOWNLOAD] Ensure that in the detail view, the uploader-details are present.

 * sss12.png

TEST-CASES THAT NEED TO PASS

 * Inter-copying an entry between Journal/Documents/Mounted-Drives/Local-Shares/School-Server-Shares should behave in the same way. For eg, in the peer-to-peer mode, it was shown that the source-entry (on PEER-1) had a preview; the same was true when the entry finally arrived on PEER-2. In particular, the preview should "go along" as and when the entry goes, intra-XO or inter-XO.


 * Things should work fine, irrespective of the fact that whether the sharing is done via single-mode, or batch-mode.