Jalama

============================================================

EXAMPLE:

i) show directories containing forms that have been uploaded, listed by table
or form name:

intertidal_DatasetID
tidal_DatasetID
forest_DatasetID

user then picks one of these groups

ii) for picked one - show directories containing data collected from (say) 4
different tablets on 3 different days -

user selects which ones (directories) contain the data to be merged

iii) do merge

...so hierarchy might actually look like this:

~/.morpho/[...]/jalama_incoming/Intertidal_brooke.5.1/12Jan05/
 ~/.morpho/[...]/jalama_incoming/Intertidal_brooke.5.1/28Jan05/
 ~/.morpho/[...]/jalama_incoming/Intertidal_brooke.5.1/31Jan05/
 ~/.morpho/[...]/jalama_incoming/Tidal_brooke.3.2/11Feb05/
 ~/.morpho/[...]/jalama_incoming/Tidal_brooke.3.2/26Feb05/
 ~/.morpho/[...]/jalama_incoming/Forest_brooke.8.7/28Jan05/

============================================================

AFTER MERGE:

after merge, move datasets from jalama_incoming to jalama_processed. Ask if they
want to keep original forms or delete them

conf call 18 March 2005:

when synchronizing data from tablet, put it in a subdir of ~/.jalama directory
(like: ~/.jalama/[...]/jalama_incoming/...)
instead of in ~/.morpho (like: ~/.morpho/[...]/jalama_incoming/...), as
previously mentioned.

This keeps all jalama-plugin files separate from morpho files, and dispenses
with the problem of the synch code needing to know which profile is currently
running, and therefore where to put the data.

After merge ("import"), dataset would be displayed in morpho, and then when the
user saves it, it will be put into the correct profile dir by morpho's existing
code - no brainer

~/.morpho/[...]/jalama_incoming/In

basic call to merger done - only thing left to do is split data out and make it
online instead of inline, then get morpho to recognize this and open it in
spreadsheet view

Finished first version of morpho plugin.

Original Bugzilla ID was 2021