Jalama: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362005-03-11T21:40:18ZEcoinformatics Redmine
Redmine Bug #2041 (Resolved): Servlet should save Data (EML) to user's ~/.jalama directoryhttps://projects.ecoinformatics.org/ecoinfo/issues/20412005-03-11T21:40:18ZMatthew Brookebrooke@nceas.ucsb.edu
<p>Servlet needs changing so that when it saves data (when user hits "next" and<br />"finish"), it does so to the user's ~/.jalama directory, instead of to the<br />servlet context, as is currently the case. Note that the proposed deployment<br />server (see bug <a class="issue tracker-1 status-3 priority-5 priority-highest closed" title="Bug: Build deployment server using http over tcp/ip (Resolved)" href="https://projects.ecoinformatics.org/ecoinfo/issues/2017">#2017</a>) will ultimately need to sync these data files with those<br />on the server machine, so maybe it would be a good idea to mirror the directory<br />structure proposed in bug <a class="issue tracker-1 status-3 priority-5 priority-highest closed" title="Bug: Morpho Plugin - Basic Dataset Upload and Merging (Resolved)" href="https://projects.ecoinformatics.org/ecoinfo/issues/2021">#2021</a>, comment <a class="issue tracker-1 status-3 priority-5 priority-highest closed" title="Bug: need more extensive element documentation (Resolved)" href="https://projects.ecoinformatics.org/ecoinfo/issues/1">#1</a>, to make this simpler?</p> Bug #2040 (Resolved): Morpho Plugin - Installer to add to existing Morpho installationhttps://projects.ecoinformatics.org/ecoinfo/issues/20402005-03-11T21:32:40ZMatthew Brookebrooke@nceas.ucsb.edu
<p>Need an installer to add the Jalama plugin to an existing Morpho installation<br />and update the config.xml file accordingly etc</p> Bug #2039 (Resolved): XBL DATATABLE WIDGET Tracking Bughttps://projects.ecoinformatics.org/ecoinfo/issues/20392005-03-11T21:20:10ZMatthew Brookebrooke@nceas.ucsb.edu
<p>Tracking bug for all tasks concerning XBL datatable widget -</p>
<p>use "Show dependency tree" link to see dependent bugs</p> Bug #2026 (Resolved): MORPHO PLUGIN Tracking Bug - Field Data-Collection Adminhttps://projects.ecoinformatics.org/ecoinfo/issues/20262005-03-11T20:46:10ZMatthew Brookebrooke@nceas.ucsb.edu
<p>This is a top-level bug to reference all tasks associated with creating a Morpho<br />Plugin for Field Data-Collection Admin</p>
<p>use "Show dependency tree" link to see dependent bugs</p> Bug #2021 (Resolved): Morpho Plugin - Basic Dataset Upload and Merginghttps://projects.ecoinformatics.org/ecoinfo/issues/20212005-03-11T20:36:58ZMatthew Brookebrooke@nceas.ucsb.edu
<p>Morpho Plugin for Field Data-Collection Admin:</p>
<p>2) dataset merging and Upload</p>
<p>a) basic requirement:</p>
<p>incoming datasets would all be put inside a subfolder that resides in the same<br />root directory, within the user's morpho profile - eg</p>
<pre><code>~/.morpho/[...]/jalama_incoming/Intertidal_12Jan05/<br /> ~/.morpho/[...]/jalama_incoming/Intertidal_28Jan05/<br /> ~/.morpho/[...]/jalama_incoming/Intertidal_31Jan05/</code></pre>
<p>...where "Intertidal" represents the form title or table name etc - this is<br />consistent across all tablets used by different people for any given group of<br />measurements.</p>
<p>Plugin would allow user to pick one <strong>or more</strong> of these directories, and all<br />those dirs' contents would be sent to the fragment aggregator for merging. Note<br />that multiple selection is needed because collection might take place over<br />multiple days for a single dataset.</p>
<p>Resulting merged dataset would then be copied to user's main morpho profile<br />directory, so it can be browsed and manipulated in morpho, and can be uploaded<br />to metacat if required</p> Bug #2020 (Resolved): Morpho Plugin - let user define which of multiple tables used for UI genera...https://projects.ecoinformatics.org/ecoinfo/issues/20202005-03-11T20:25:50ZMatthew Brookebrooke@nceas.ucsb.edu
<p>Morpho Plugin for Field Data-Collection Admin:</p>
<p>1) Form generation:</p>
<p>b) If chosen Dataset has multiple tables, let user define which of these are used<br />as the basis of UI generation. Potentially the first step towards Mark's<br />requested "templating" feature, whereby an existing dataset is used as a<br />starting point for a new dataset</p> Bug #2019 (Resolved): Morpho Plugin - 'Generate form' menu optionhttps://projects.ecoinformatics.org/ecoinfo/issues/20192005-03-11T20:21:39ZMatthew Brookebrooke@nceas.ucsb.edu
<p>Morpho Plugin for Field Data-Collection Admin</p>
<p>1) Form generation:</p>
<p>a) basic requirement:</p>
<p>Add a 'Generate form' menu option, so user can browse EML data sets (local or<br />metacat) in morpho; which passes the current doc to the UI Generation code, and<br />the resulting XUL is saved somewhere (in profile?) for later download to a tablet</p>
<p>User can also go thru' DP wizard and create a new dataset to use as the basis of<br />UI generation - after creating document, proceed as above</p> Bug #2017 (Resolved): Build deployment server using http over tcp/iphttps://projects.ecoinformatics.org/ecoinfo/issues/20172005-03-11T20:03:36ZMatthew Brookebrooke@nceas.ucsb.edu
<p>Build deployment server that can be contacted from tablet PCs (using http over<br />tcp/ip) in order for them to get a zip file containing generated form(s) and<br />associated EML files</p>
<p>IMPLEMENTATION NOTES:</p>
<p>1) because jalama's httprenderer directory in the tomcat servlet context may be<br />deleted and replaced by a new WAR at some point, we should ensure that we don't<br />lose any critical files during this process (like data that the user has saved).<br />Data files should therefore be stored in ~/.jalama, which is where xul forms are<br />already stored</p>
<p>2) Tomcat config on workstation/server should allow connections only from the<br />local subnet, for security reasons. Tomcat on tablets should allow connections<br />only to localhost.</p>
<p>3) when client originally tries to connect to workstation/server, or if tablet<br />cannot connect to server at previously-known address (eg if operating on a<br />quickly-changing DHCP network), then a dialog should ask user for the server's<br />hostname or IP address. Otherwise, should just connect automatically, without<br />prompting user for address</p> Bug #1941 (Resolved): Data Collection Output Should be a Complete EML Documenthttps://projects.ecoinformatics.org/ecoinfo/issues/19412005-02-02T04:33:44ZMatthew Brookebrooke@nceas.ucsb.edu
<p>add original EML document around collected datatable fragment, so output of data<br />collection is a complete EML document, instead of just the fragment, as is<br />currently the case. This can be done by servlet when user hits finish. EML<br />should then be saved to disk automatically, without user intervention, ready for<br />upload to workstation.</p> Bug #1940 (Resolved): Get ASCII function in Spreadsheet summary view on Finishhttps://projects.ecoinformatics.org/ecoinfo/issues/19402005-02-02T04:28:32ZMatthew Brookebrooke@nceas.ucsb.edu
<p>On finishing the data collection (user hits the "finish" button), the<br />spreadsheet summary view is shown (see Bug <a class="issue tracker-1 status-2 priority-2 priority-default" title="Bug: Spreadsheet summary view during collection (In Progress)" href="https://projects.ecoinformatics.org/ecoinfo/issues/1939">#1939</a>), but now it also has a "get<br />ascii" button, which returns data as an ascii file (e.g. CSV) for manipulation<br />in an external stats program</p> Bug #1938 (Resolved): XBL Datatable Widget - allow user modifications to auto-increment fieldhttps://projects.ecoinformatics.org/ecoinfo/issues/19382005-02-02T04:15:44ZMatthew Brookebrooke@nceas.ucsb.edu
<p>auto-increment field is already implemented in XBL, but currently has admin-set<br />start, end and increment values.</p>
<p>Needs additional functionality, editable by user in field to reflect field<br />conditions, such as starting at user-defined values, and counting in<br />user-defined direction. For example, pisco collections depend on tides, so<br />collection might start at the end of each transect and work backwards to<br />halfdway, to beat the tide, then remaining measuerments would start at beginnign<br />of each transect and work up to halfway, after the tide has come in and covered<br />the already-measured parts.</p> Bug #1937 (Resolved): XBL Datatable Widget - fields shouldn't automatically keep prev record's va...https://projects.ecoinformatics.org/ecoinfo/issues/19372005-02-02T04:02:10ZMatthew Brookebrooke@nceas.ucsb.edu
<p>fields shouldn't automatically keep prev record's values, but this should be<br />configurable by the admin. Keeping same values may be appropriate for<br />"metadata"-type attributes that aren't being collected (eg site, date, etc), but<br />not for data-type values (species found etc)</p>
<p>Settings for this woudl ultimately be made in admin rules gui - see Bug <a class="issue tracker-1 status-2 priority-1 priority-lowest" title="Bug: Build customization dialog to modify UIGen rules for form generator (In Progress)" href="https://projects.ecoinformatics.org/ecoinfo/issues/1930">#1930</a></p> Bug #1927 (Resolved): Build screen listing available Jalama Forms (XUL files) on Jalama startuphttps://projects.ecoinformatics.org/ecoinfo/issues/19272005-02-01T21:22:50ZMatthew Brookebrooke@nceas.ucsb.edu
<p>When the user clicks on a desktop or start menu "Launch Jalama" link, the first<br />index page returned from Tomcat should show a listing of available Jalama Forms<br />(XUL files) that have been installed on that machine.</p>
<p>this listing woudl preferably tell the user something about each form, so they<br />can make an informed choice</p> Bug #1926 (Resolved): Build Installer For Jalamahttps://projects.ecoinformatics.org/ecoinfo/issues/19262005-02-01T19:31:31ZMatthew Brookebrooke@nceas.ucsb.edu
<p>possibly using InstallAnywhere -</p>
<p>installer tasks are:<br />1) Hardcode tomcat configuration <br />2) Hardcode JRE into InstallAnywhere<br />3) Hardcode firefox install/unzip<br />4) Place Jalama war in right place<br />5) create ~/.jalama dir for XUL library, and populate with an initial XUL file<br />6) Create Start menu item for launching Jalama</p>