Jalama: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362006-05-26T22:50:36ZEcoinformatics Redmine
Redmine Bug #2447 (New): Jalama web-app XUL doesn't work in Firefox 1.5+https://projects.ecoinformatics.org/ecoinfo/issues/24472006-05-26T22:50:36ZMatthew Brookebrooke@nceas.ucsb.edu
<p>In the Jalama web-app ("Whippet"), the automatic XUL generation works fine, but the resulting XUL UI's don't display properly in Firefox 1.5+ (but are fine in Firefox 1.0x)</p>
<p>What has changed with XUL rendering in FF between 1.0.7 and 1.5?</p>
<p>This seems to be a problem with the "container" type XBL components - see the "record_per_screen" binding in the XBL file:</p>
<p>jalama/chrome/content/jalama_library/widgets/datatable_bindings.xml</p>
<p>or maybe the "complex_element", "invisible_container" and "bordered_vbox" bindings in the file:</p>
<p>jalama/chrome/content/jalama_library/widgets/complex_element.xml</p> Bug #2037 (New): Promoting Data/Metadatahttps://projects.ecoinformatics.org/ecoinfo/issues/20372005-03-11T21:12:18ZMatthew Brookebrooke@nceas.ucsb.edu
<p>Promoting Data/Metadata</p>
<ul>
<li>Please add any clarifications/comments that any of you may have **</li>
</ul>
<p>A) as part of the UI Generation process, need to:</p>
<p>1) inspect incoming table(s) for temporal fields</p>
<p>2) determine which if any go to temporal metadata [**SEE NOTE 1**]</p>
<p>3) repeat for spatial fields</p>
<p>4) repeat for taxonomic coverage</p>
<p>5) temporarily record these assignments in "additional metadata" section of the<br />EML doc</p>
<p>B) as part of the merging process, need to:</p>
<p>1) during the merge, use this info that was put into "additional metadata" to<br />pull out the correct values from the predefined <strong>data</strong> table columns, and use<br />them to populate the <strong>metadata</strong> (ie temporal, geographic and taxonomic coverage<br />sections)</p>
<p>2) IMPORTANT: on finish, delete the "additional metadata" section that we added</p>
<p>**NOTE 1: we are anticipating that the form designer (through the use of rules)<br />would somehow define which columns should subsequently be used for promoting to<br />metadata. Note that there are some potential difficulties with these definitions<br />- for example, timestamps may be spread over sevaral columns (for example -<br />separate columns for year, month, day, time), so the rules and the markup added<br />to "additional metadata" should be rich enough to define such combinations of<br />columns etc, and define which values to use (eg "the minimum value of combined<br />cols a, b and c" etc). Needs some careful consideration</p>
<p>**NOTE 2: As a first pass, restrict designer to using fields that are explicitly<br />included in the data (denormalized) - not data referenced via foreign key<br />constraints etc</p> Bug #2022 (In Progress): Morpho Plugin - Enhanced Dataset Upload and Merginghttps://projects.ecoinformatics.org/ecoinfo/issues/20222005-03-11T20:39:40ZMatthew Brookebrooke@nceas.ucsb.edu
<p>Morpho Plugin for Field Data-Collection Admin:</p>
<p>2) dataset merging and Upload</p>
<p>b) future development:</p>
<p>(see bug 2021#)<br />Allow more sophisticated browsing (and poss Morpho search function?) to choose<br />datasets for merge - browser would show metadata in listings, like morpho search<br />results currently do (title, keywords, owner etc). User can select multiple<br />datasets and then hit merge button</p> Bug #2018 (New): Allow deployment server to check and sync latest Jalama s/w (war file)https://projects.ecoinformatics.org/ecoinfo/issues/20182005-03-11T20:07:44ZMatthew Brookebrooke@nceas.ucsb.edu
<p>Upon connection, deployment 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>) should check clients (eg<br />tablet PCs) to see if they have latest verion of Jalama software, and if not,<br />update the software, in the form of a new WAR file for deployment in Tomcat</p> Bug #1939 (In Progress): Spreadsheet summary view during collectionhttps://projects.ecoinformatics.org/ecoinfo/issues/19392005-02-02T04:23:39ZMatthew Brookebrooke@nceas.ucsb.edu
<p>Need a spreadsheet summary view to show already-collected data - displayable at<br />any point during data collection. Especially useful in instance where data is<br />not being collected sequentially (see, for example, the description in Bug #<br />1938) - so user can see what has and hasn't been collected.</p>
<p>We also need a method of navigating quickly to the records that remain to be<br />filled in, or to records that need to be edited, and it strikes me that this<br />spreadsheet view would be a good place to implement this - maybe the user clicks<br />on a row and is immediately taken to the relevant record form. This is how it is<br />handled in the current handBase app on the palm, I believe</p> Bug #1936 (In Progress): XBL input widgets - Allow Widgets to be collapsed to save space if not r...https://projects.ecoinformatics.org/ecoinfo/issues/19362005-02-02T03:50:38ZMatthew Brookebrooke@nceas.ucsb.edu
<p>Allow fields that are not marked as required by the rules/admin to be minimized<br />or hidden in the form, and to be associated with other fields to which they have<br />an association</p> Bug #1935 (New): Redesign PISCO EML to have complete list of fields, including the optional fieldshttps://projects.ecoinformatics.org/ecoinfo/issues/19352005-02-02T01:17:26ZMatthew Brookebrooke@nceas.ucsb.edu
<p>Redesign PISCO EML to have complete list of fields, including the optional fields<br />(Pool (boolean), Epiphyte & Canopy (species) for each classification)</p> Bug #1934 (In Progress): XBL Datatable Widget - Implement Overridable Validationhttps://projects.ecoinformatics.org/ecoinfo/issues/19342005-02-02T00:54:02ZMatthew Brookebrooke@nceas.ucsb.edu
<p>Implement Overridable Validation in XBL Datatable Widget - currently tells user<br />something's not filled in, and they can't proceed to next record. However, at<br />the form-designer's discretion (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>), this should be overridable,<br />although overriding should be ergonomically difficult to prevent abuse (eg popup<br />saying you really shouldn't - are you sure? etc)</p>
<p>Possibly the form designer should be able to designate fields that are not<br />overridable (again, 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 #1933 (In Progress): XBL 2d Dropdown: various improvementshttps://projects.ecoinformatics.org/ecoinfo/issues/19332005-02-02T00:35:42ZMatthew Brookebrooke@nceas.ucsb.edu
<p>In order of priority, most urgent to least urgent:</p>
<p>1) rethink how enumerations get populated at runtime - currently done in<br />javascript, and this is so slow (for large lists like species in the pisco app)<br />that firefox pops up a dialog asking if user wants to terminate JS process.<br />Other possibilities include:<br />- optimizing the existing javascript code (NOTE - maybe the bottleneck is the<br />alphabetical reordering? is this done in JS? if so, can we do it in the rules<br />instead?)<br />- getting menuitems from a call to a java Command in the backend</p>
<p>2) make scrollbox arrows bigger and easier to hit - need to inherit from and<br />override default XUL arrowscrollbox to do this (see how default XUL menuitem was<br />overridden in a similar fashion, in the<br />jalama/chrome/content/widgets/enumeration_bindings.xml file)</p>
<p>3) reordering of entries on 2d popup screen - for example:<br />- most recently used at top, with separator line?<br />- alphabetical (current scheme)<br />- cluster species groups together<br />- species in the same spatial zone are grouped together<br />- other arbitrary grouping to accomodate individual preferences</p> Bug #1931 (New): Support multiple tableshttps://projects.ecoinformatics.org/ecoinfo/issues/19312005-02-01T23:42:36ZMatthew Brookebrooke@nceas.ucsb.edu
<p>Support multiple tables</p>
<p>Three Cases</p>
<p>A -</p>
<p>1) Lookup tables (follow the EML references to get enumerated values out of a<br />table). This is probably just a case of writing rules to do it - should be<br />possible without any architectural changes</p>
<p>2) Normalized data - foreign key constraints between tables:<br />Context versus measurements (e.g., site table versus plot measurements table)</p>
<p>3) Orthogonal tables - no foreign key constraints - just need to generate<br />mutliple unrelated UIs into individual XUL forms (currently, all tables appear<br />in one form)</p> Bug #1930 (In Progress): Build customization dialog to modify UIGen rules for form generatorhttps://projects.ecoinformatics.org/ecoinfo/issues/19302005-02-01T23:23:32ZMatthew Brookebrooke@nceas.ucsb.edu
<p>Build "customization dialog" (see whiteboard photo in cvs:<br />jalama/docs/dev/Sep2004mtg-whiteboard/configure_entry_form_03.jpg) that is used<br />to customize some aspects of the form generated by the form generator.</p>
<p>Customizable aspects include field visibility, default value, validation<br />required, location etc. Dialog basically amends Drools rules before ui<br />generation takes place</p> Bug #1630 (In Progress): Drools Rules - Layout (pagination & flow) stage of UI Genhttps://projects.ecoinformatics.org/ecoinfo/issues/16302004-07-07T23:05:52ZMatthew Brookebrooke@nceas.ucsb.edu
<p>Need to look at this properly and write some rules - currently just does a<br />pass-thru without changing the layout</p> Bug #1627 (In Progress): XBL Datatable Widget - Configurable first page & headerhttps://projects.ecoinformatics.org/ecoinfo/issues/16272004-07-07T22:44:10ZMatthew Brookebrooke@nceas.ucsb.edu
<p>closed bug 1106 and opened this one to update it.<br />-------------------------------------------------</p>
<p>first page editable fields should be configurable thru rules - can do this by<br />adding XPaths of elements to be edited, in much the same way as the population<br />rules currently do for other parameters in datatabl binding (for example, we<br />already set the xpath for the table name and the data location). The process<br />for reading these (since we don't know ahead of time how many there will be) is<br />similar to that used in the selectbox binding for reading the enumerated list<br />values.</p>
<p>As a first pass, assume that these editable fields then appear in the header for<br />each page. Furhter development might include lettign the rules decide where<br />exactly to locate them, and whether any should be suppressed in the header, or<br />non-editable.</p> Bug #1624 (New): XBL Datatable Widget - make single values into labelshttps://projects.ecoinformatics.org/ecoinfo/issues/16242004-07-07T22:26:42ZMatthew Brookebrooke@nceas.ucsb.edu
<p>closed bug 1106 and opened this one to update it.<br />-------------------------------------------------</p>
<p>If a data entry field has only one possible value, make it a label or make it<br />non-editable so it doesn't get focus. This will make it easier for user tabbing<br />thru fields</p> Bug #1093 (In Progress): Unit tests for JS and XBLhttps://projects.ecoinformatics.org/ecoinfo/issues/10932003-06-06T00:54:43ZMatthew Brookebrooke@nceas.ucsb.edu
<p>Need to come up with a framework for testing JavaScript and XBL bindings.</p>
<p>For JS, look at JsUnit ( <a class="external" href="http://jsunit.berlios.de/">http://jsunit.berlios.de/</a> )</p>