The DataManager activity provides a unifed view of the user`s datastore including both documents on the schoolserver and those local to the XO. The user can choose which documents to keep local and which to keep only on the schoolserver. It also provides a Commons which has documents shared among all users registered to the schoolserver.

Entries are color-coded. Light green for documents located only on the schoolserver. Green for documents stored both locally and on the schoolserver. Cyan for documents in Commons. Blue for documents from Commons stored locally. Red for new documents not yet uploaded to the schoolserver. White for entries which do not have a document.

The activity has three phases. In the first phase, the activity makes a list of all entries in the data store and shows the percentage of the local store in use. In the second phase, the user may double-click on entries. If the entry is local it will be removed. If the entry is only on the schoolserver, it will be downloaded. The user initiates the last phase by the quit button on the activity toolbar. In this phase the activity performs the requested upload, download and removal operations. Note: red documents will be uploaded to the schoolserver and after one day white entries will be removed.

There is a `usage` tab on the toolbar with three buttons. If a document is selected and the information button is clicked, the user will see a display of the document`s metadata in the status bar. If a `green` document is selected and the up-arrow button is clicked, the document will be uploaded to Commons (shared with all registered XOs). If a local document is selected and the delete (-) arrow is clicked, it will be deleted (whether or not it has been
saved on the schoolserver).

Support

Support for this activity is provided by the developer at tony_anderson at usa dot net

Developer Comments

The DataManager Activity is relevant only in an enviroment where the XO is supported by a schoolserver. It must run as user olpc (add org.olenepal.DataManager to the list of activities
run as olpc in /usr/share/lib/python2.5/site-packages/sugar/activityfactory.py). On the schoolserver, it is necessary to add two folders (/library/Datastore and /library/Commons).
In addition there needs to be a symbolic link in /var/www/moodle (ln -s /library/Commons Commons). Commons should be owned by apache and in group xousers (775). Datastore also needs a link in /var/www/moodle (ln -s /library/Datastore Datastore). Datastore should be owned by apache, group apache, permissions 775. Each registered user needs a folder in Datastore whose name is the XOs serial-number (see /library/users). The user folder in Datastore should have the serial-number as both owner and group and permissions 775.
Finally, public keys need to be set up. Copy /home/olpc/.sugar/default/owner.key to /home/olpc/.ssh/id_dsa. Install owner.key.pub needs to be copied to the schoolserver: /library/users/serial-number/.ssh/authorized_keys2. (Note: authorizedkeys2 is the key file not a folder.)

In a deployment, this can probably be incorporated into the schoolserver registration procedure. At the moment I am doing it manually.

See all 1 reviews of this activity

Adds a `delete` button primarily for use in testing. If a datastore local
entry is selected and the button is clicked, that entry will be removed whether or not it is saved on the schoolserver. The fix to the closing logic includes waiting one day before deleting metadata only entries.
(The previous version removed the datastore entry for the activity before it closed - a situation to which
Sugar took exception).

• View Older Versions