Jalama: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362010-06-24T02:11:40ZEcoinformatics Redmine
Redmine Bug #5056 (Resolved): test bug 2https://projects.ecoinformatics.org/ecoinfo/issues/50562010-06-24T02:11:40ZMatt Jonesjones@nceas.ucsb.edu
<p>Another test.</p> Bug #5055 (Resolved): test bug 1https://projects.ecoinformatics.org/ecoinfo/issues/50552010-06-24T02:10:53ZMatt Jonesjones@nceas.ucsb.edu
<p>This is a test.</p> Bug #2127 (Resolved): Fix required/not required and bold labels (minoccurs/maxoccurs issue)https://projects.ecoinformatics.org/ecoinfo/issues/21272005-06-16T19:24:30ZMatthew Brookebrooke@nceas.ucsb.edu
<p>Fix required/not required and bold labels in XBL widgets. Thsi is a side-effect<br />of schema generation vs non-generated schema, and minoccurs/maxoccurs stuff.<br />widgets currently look to see if minOccurs>0, and if so, then field is<br />"required". We need another way of determining required-ness</p> Bug #2126 (Resolved): Show/hide examples for input fieldshttps://projects.ecoinformatics.org/ecoinfo/issues/21262005-06-15T16:57:27ZMatthew Brookebrooke@nceas.ucsb.edu
<p>this bug replaces bug <a class="issue tracker-1 status-3 priority-2 priority-default closed" title="Bug: XBL Datatable Widget - show/hide relevant metadata for input fields (Resolved)" href="https://projects.ecoinformatics.org/ecoinfo/issues/1626">#1626</a><br />---------------------------</p>
<p>Have implemented a framework for adding a description label above each input<br />field and an example widget below each input field.</p>
<p>Description labels are being populated OK from metadata; however, I'm not sure<br />where to pull the examples from, within the EML...</p> Bug #2090 (Resolved): problem with registering UIhttps://projects.ecoinformatics.org/ecoinfo/issues/20902005-05-25T18:38:48ZMatthew Brookebrooke@nceas.ucsb.edu
<p>using dataset:<br />seabloom.5.2<br />Sedgwick BYDV Prevalence</p>
<p>1) generate a data form</p>
<p>2) choose table "bydv-data-out.csv" for generation</p>
<p>3) see exception:<br />note "ID = data_form_seabloom.5.2_table_No_such_entity!.ser" <br />am i replacing dashes <strong>before</strong> asking datapackage for the entity? (hence<br />"No_such_entity!"??)</p>
<hr />
<p>Exception in thread "Thread-7" java.lang.IllegalArgumentException: Non-valid ID<br />received:<br /> ID = data_form_seabloom.5.2_table_No_such_entity!.ser<br /> (contains illegal characters)<br /> xulFile = <?xml version="1.0"?><br />[...]<br /></window><br /> docType_schemaLocation = eml://ecoinformatics.org/eml-2.0.0<br /> xpath = /<br /> mode = editor<br /> at<br />edu.ucsb.nceas.jalama.JalamaFormLib.throwIllegalArgumentException(JalamaFormLib.java:421)<br /> at edu.ucsb.nceas.jalama.JalamaFormLib.installForm(JalamaFormLib.java:301)<br /> at<br />edu.ucsb.nceas.jalama.entrypoint.morpho.OpenUIGenCommand$UIGenThread.run(OpenUIGenCommand.java:394)</p> Bug #2087 (Resolved): XUL Error when runnign UI for a second time on clienthttps://projects.ecoinformatics.org/ecoinfo/issues/20872005-05-24T15:23:02ZMatthew Brookebrooke@nceas.ucsb.edu
<p>start jalama on client, choose a UI and hit start. Collect data and hiot finish.<br />close this window. go back to homepage and select same UI again, and hit start.<br />window pops up showing a xul error</p> 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>