Morpho: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362010-01-25T21:45:28ZEcoinformatics Redmine
Redmine Bug #4695 (Resolved): CSS doesn't work on mac installer versionhttps://projects.ecoinformatics.org/ecoinfo/issues/46952010-01-25T21:45:28ZJing Taotao@nceas.ucsb.edu
<p>The morpho metadata display loses color on mac installer version. Howerver, it works on windows and linux installer. The morpho built from svn on mac works too.</p> Bug #4692 (Resolved): Morpho cannot open EML docs with <?xml-stylesheet> directivehttps://projects.ecoinformatics.org/ecoinfo/issues/46922010-01-22T18:22:10Zben leinfelderleinfelder@nceas.ucsb.edu
<p>SBC and MCR LTER sites are including <?xml-stylesheet> directives in their EML docs. This is valid XML, but Morpho was expecting the document root/schema def/doctype to be on the second line of the XML (not the 3rd or fourth or fifth...).<br />With this error, the documents could not be opened in Morpho at all (symptom: <a class="external" href="http://bugzilla.ecoinformatics.org/show_bug.cgi?id=3482">http://bugzilla.ecoinformatics.org/show_bug.cgi?id=3482</a>)</p> Bug #4687 (Resolved): Morpho logs password in plaintexthttps://projects.ecoinformatics.org/ecoinfo/issues/46872010-01-21T20:50:38Zben leinfelderleinfelder@nceas.ucsb.edu
<p>from Gastil:<br />Morpho logs my password in plain text in the stderr.log file when there is a login error.<br />Call me paranoid, but this seems inappropriate and makes me feel uncomfortable.</p> Bug #4678 (Resolved): Modify the documentation for 1.8 releasehttps://projects.ecoinformatics.org/ecoinfo/issues/46782010-01-15T20:18:16ZJing Taotao@nceas.ucsb.edu
<p>I will draft a new version of user manual.</p> Bug #4677 (Resolved): Windows 7 installer/testinghttps://projects.ecoinformatics.org/ecoinfo/issues/46772010-01-15T20:13:17Zben leinfelderleinfelder@nceas.ucsb.edu
<p>Make sure Morpho installs and runs on Windows 7</p> Bug #4661 (Resolved): table 'worksheet' display not updated after table deletedhttps://projects.ecoinformatics.org/ecoinfo/issues/46612010-01-12T21:43:14ZMargaret O'Brienmob@msi.ucsb.edu
<p>a user wanted to replace a dataTable in a package. She chose 'Data->delete data table'. The data table disappeared, and she added uploaded a new table and a created a new set of attribute descriptions. So far, this is as expected.</p>
<p>However, when she finished the attribute descriptions, and Morpho displayed the table, it displayed the old attribute descriptions in the 'worksheet' pane. When she clicked on an attribute, the new attribute description was displayed on the right (alongside the old table). When she closed the data package and reopened, the new data table was there, so it seems to be just a worksheet display issue.</p>
<p>The EML docids are cdonahue.26.2 (old table, to be deleted) and cdonahue.26.3 (new table)</p> Bug #4657 (Resolved): morpho creates <keyword> elements out of keywordType attribute contenthttps://projects.ecoinformatics.org/ecoinfo/issues/46572010-01-08T22:13:18ZMargaret O'Brienmob@msi.ucsb.edu
<p>the <keyword> element has an optional attribute keywordType, as in this snippet from knb-lter-sbc.17.12</p>
<p><keywordSet><br /> <keyword keywordType="theme">Santa Barbara Coastal</keyword><br /> <keyword keywordType="theme">LTER</keyword><br /></keywordSet></p>
<p>EML created by Morpho does not include this attribute, but when Morpho encounters one, it takes the attribute content and moves it to a keyword element, yielding a node like this (knb-lter-sbc.17.13):<br /><keywordSet><br /> <keyword>theme</keyword><br /> <keyword>Santa Barbara Coastal</keyword><br /> <keyword>theme</keyword><br /> <keyword>LTER</keyword><br /></keywordSet></p>
<p>So now we have extra erroneous keywords, and no keywordType attributes. <br />Morpho seems to do this as soon as it reads the EML in, since the extra keywords show up immediately.</p>
<p>Note: this data set is still EML201, and so was was edited with Morpho 1.6.1. I confirmed the behavior with Morpho 1.7 and a local test dataset.</p> Bug #4646 (Resolved): when upgrading from 2.0.1, morpho did not catch empty <offline> elementhttps://projects.ecoinformatics.org/ecoinfo/issues/46462010-01-04T23:00:54ZMargaret O'Brienmob@msi.ucsb.edu
<p>a user updated her morpho to 1.7.1, and loaded a 2.0.1 package. The first thing she must do is upgrade to EML2.1.0<br />The data package did not included a data table, but included the table attribute descriptions, so morpho 1.7.1 had inserted 2 elements which are not allowed in EML2.1:<br />1. an empty <objectName> </objectName><br />2. <offline> with no children<br />Morpho presented the user with a dialog box for adding the objectName, but ignored the offline element. The error message (from the parser) was not useful to the scientist.<br />The file is attached.<br />[Note: this file actually had 2 errors, but the other problem is addressed in another bug: 3978]</p> Bug #4623 (Resolved): docid conflict box needs a button or somethinghttps://projects.ecoinformatics.org/ecoinfo/issues/46232009-12-11T01:26:10ZOliver Soongsoong@nceas.ucsb.edu
<p>I created a package (.1 revision), synced local->remote (.2 revision?), then edited the local EML to produce a docid conflict (another .2 revision). When trying to sync local->remote, a message pops up about a docid conflict and asks how I want to resolve this. There's a radio selector but no "Ok" button or anything like that. The only option is to close the dialog window with the X in the upper right corner, which isn't exactly intuitive. It seems to function properly, though.</p> Bug #4622 (Resolved): local copies of zip "data tables" corrupthttps://projects.ecoinformatics.org/ecoinfo/issues/46222009-12-11T00:52:21ZOliver Soongsoong@nceas.ucsb.edu
<p>The example is soong.37.2 on the dev metacat (search for soong). The data package contains zip files as "data tables". The zip files are intact in the cache folder (can be expanded). After syncing remote->local, the zip files in the data folder are corrupt (contents can be listed but not expanded).</p> Bug #4543 (Resolved): export to FGDC BDP formathttps://projects.ecoinformatics.org/ecoinfo/issues/45432009-11-12T20:09:19ZMatt Jonesjones@nceas.ucsb.edu
<p>Include a 'format' dropdown in the Export dialog that allows people to choose the 'FGDC BDP' format as an export choice. The set of export formats should be configurable at runtime, and should allow for a mapping between the format name and an XSLT script used to generate that format from the EML document.</p> Bug #4537 (Resolved): MS accesss file importing leads an invalid eml-2.1.0 documenthttps://projects.ecoinformatics.org/ecoinfo/issues/45372009-11-08T23:52:34ZJing Taotao@nceas.ucsb.edu
<p>Hi Jing,</p>
<p>Here is a copy of the local file (906.2) that I am having problems saving to the network. I am also having this problem with<br />903.3<br />901.4<br />904.7<br />917.2<br />910.4</p>
<p>For all of these data packages I have been able to save to the network before. The only new thing that I have done to each of these packages is<br />import an MS access file (under the data drop down menu)</p>
<p>Thanks!<br />Marissa</p> Bug #4459 (Resolved): Need a minimum display of access order in Access pagehttps://projects.ecoinformatics.org/ecoinfo/issues/44592009-10-15T16:54:34ZJing Taotao@nceas.ucsb.edu
<p>Currently morpho will use allowFirst as default access order. And it still respects the access order (denyFirst or allowFirst) from eml itself. However, it doesn't display the order in Access page. So sometime it is confusing to interpret the rules without displaying the access order. We need a minimum display of access order in Access page.</p> Bug #4426 (Resolved): export fails to create html with attribute informationhttps://projects.ecoinformatics.org/ecoinfo/issues/44262009-09-30T16:06:35ZMatt Jonesjones@nceas.ucsb.edu
<p>Hi Gail,</p>
<p>Yes, my guess is that this is a stylesheet problem. The stylesheet has two modes -- one that displays just the summary information and attribute information separately, and one that displays them together. It appears for some reason that the export function is not using the mode that displays all of the metadata together. We'll look into this and get back to you.</p>
<p>Matt</p>
<p>On Wed Sep 30 06:17:29 2009, <a class="email" href="mailto:gss1@cornell.edu">gss1@cornell.edu</a> wrote:</p>
<blockquote>
<p>Greetings,</p>
<p>I notice that when I export a new data package from Morpho <br />(v1.7.0-RC2), the HTML display of the metadata record doesn't include <br />complete metadata for individual tables (or links to complete <br />metadata), even though the information is in the XML file. There is <br />some partial/summary table info at the top of the HTML display of the <br />record, but no attribute info. Is that a stylesheet problem, and is a <br />fix in the works? We have researchers who are sharing data sets with <br />colleagues for whom that HTML display is very useful. Any thoughts on <br />why the display has become a little whacky?</p>
<p>I recreated the problem by creating a new/clean data set with just <br />one table - I can send a screenshot and/or the metadata file, if <br />that's helpful.</p>
<p>Thanks so much,<br />Gail</p>
<p>Gail Steinhart<br />Research Data & Environmental Sciences Librarian<br />Albert R. Mann Library<br />Cornell University<br />Ithaca, NY 14853</p>
<p>Phone: 607-255-7251<br />Fax: 607-255-0318<br />E-mail: <a class="email" href="mailto:GSS1@cornell.edu">GSS1@cornell.edu</a></p>
</blockquote> Bug #4422 (Resolved): morpho installer freezes when it creates short cut on windows 64-bit machinehttps://projects.ecoinformatics.org/ecoinfo/issues/44222009-09-28T19:22:00ZJing Taotao@nceas.ucsb.edu
<p>I think this is the right group of people for this problem, but I'm<br />not entirely sure. I'm trying to install Morpho 1.7.0, but it's<br />getting stuck when trying to create shortcut icons. The same thing<br />happened with the Kepler 2.0.0-alpha installer, and we figured out<br />that izpack requires some special 64-bit dlls for 64-bit Windows. I<br />don't really know any more specific details, but I recall Chad being<br />able to fix it for Kepler.</p>