Features/Transfer to many options: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
=== Proposal for a client-initiated journal transfer (1-to-N feature) === | === Proposal for a client-initiated journal transfer (1-to-N feature) === | ||
''' Note that the initial "Browse" based solution (of which comments have been struck out) cannot fill the purpose, because of the following reasons ''' | ''' Note that the initial "Browse" based solution (of which comments have been struck out) cannot fill the purpose, because of the following reasons ''' | ||
* (Thanks Anish) "Browse" based solution only allows files to be downloaded. But Sugar's entries are more than just a file - they are a combination of metadata, and data (files). Eg. - Turtle Art Journal entry. | * (Thanks Anish) "Browse" based solution only allows files to be downloaded. But Sugar's entries are more than just a file - they are a combination of metadata, and data (files). Eg. - Turtle Art Journal entry. | ||
| Line 33: | Line 35: | ||
** Start service "httd". | ** Start service "httd". | ||
** ALL THESE STEPS WOULD BE DONE AS PART OF OOB STAGE. | ** ALL THESE STEPS WOULD BE DONE AS PART OF OOB STAGE. | ||
* '''[Code-Requirements] Setting up WebDAV on a server XO.''' | * '''[Code-Requirements] Setting up WebDAV on a server XO.''' | ||
** "httpd" will have to be patched, so that PROPFIND also returns Sugar's metadata as properties (in obvious addition to the standard WebDAV properties [http://rfc-ref.org/RFC-TEXTS/2518/chapter13.html]) | ** "httpd" will have to be patched, so that PROPFIND also returns Sugar's metadata as properties (in obvious addition to the standard WebDAV properties [http://rfc-ref.org/RFC-TEXTS/2518/chapter13.html]) | ||
* '''[User-Workflow] Exporting Data to WebDav, on a server XO.''' | * '''[User-Workflow] Exporting Data to WebDav, on a server XO.''' | ||