You can use this feature to backup Journal entries to a USB drive or SD card.
You can use this feature to backup Journal entries to a USB drive or SD card.
+
+
=== Sharing/Backup Journal entries using a storage device===
+
The new code will store the metadata and preview in a hidden folder like in 0.82. The folder will be named ''.Sugar_metadata''. There will be two files per entry, one for the metadata named ''filename''.metadata and one for the preview (if exists) named ''filename''.preview. The data files will be stored in the root folder of the device. Like in 0.82 the entries will be colored in the creator's color.
+
+
Note: Entries that do not contain a data file can not be copied to a storage device anymore in 0.84 (this was possible in 0.82), an alert is displayed to the learner in those cases. This change has been independent of these patches.
+
+
The code is written defensive. If the metadata/preview is corrupted or has been removed it will be skipped, so the deletion of a data file on the device is handled gracefully.
+
+
The learner has now the options to: backup the Journal entry to a storage device and copy it back to his own Journal later, share his entry with another learner over a storage device and use the file on a non Sugar machine (showing a picture to your friend on his computer).
+
+
===Convert Journal entries that have been saved to a storage device in 0.82===
+
This code will convert the old Journal entries to the new scheme described above. When a device containing a folder ''.olpc.store'' is plugged into the machine the conversion will happen automatically in the background. Files that have the metadata converted already from a previous run will be omitted from the conversion. The ''.olpc.store'' won't be removed after completion to be able to restore if anything goes wrong during conversion.
+
+
Note: Entries that do not contain a data file can not be copied to a storage device anymore in 0.84 (this was possible in 0.82), for code simplification we do not restore those entries from 0.82.
+
+
The conversion code is written defensive. If an entry can not be converted it will be skipped, if the database is broken the conversion is skipped etc. So the deletion of a data file on the device or any corruption to the ''.olpc.store'' should not cause a crash to Sugar.