Ecoinformatics Redmine: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362011-01-13T17:37:32ZEcoinformatics Redmine
Redmine Metacat - Bug #5273 (Resolved): docs with inline-data allow invalid xml into metacathttps://projects.ecoinformatics.org/ecoinfo/issues/52732011-01-13T17:37:32ZChad Berkleyberkley@nceas.ucsb.edu
<p>If you insert a document with inline-data, the data is stripped out of the document before it is validated. However, when you do a GET on the document, it is read off of the disk. So if you insert a doc with inline-data that has invalid characters in it (like unescaped ampersands), metacat will not recognize that it is invalid, but when you try to get the document, you will get a parser error if you try to parse it.</p>
<p>We should be validating the document first before stripping inline-data out of it.</p> Kepler - Bug #5021 (Resolved): release date is wrong in installer readmehttps://projects.ecoinformatics.org/ecoinfo/issues/50212010-05-20T18:42:15ZChad Berkleyberkley@nceas.ucsb.edu
<p>change the date to the actual release date. it's set as may 12 right now.</p> Kepler - Bug #4956 (Resolved): make sure matlab works with installed version of kepler 2.0https://projects.ecoinformatics.org/ecoinfo/issues/49562010-04-23T16:43:41ZChad Berkleyberkley@nceas.ucsb.edu
<p>need to get matlab demo workflows working.</p> Kepler - Bug #4943 (Resolved): RC5 Installer Tracking Bughttps://projects.ecoinformatics.org/ecoinfo/issues/49432010-04-19T18:39:33ZChad Berkleyberkley@nceas.ucsb.edu
<p>Please have all RC1 installer bugs block this bug.</p> Kepler - Bug #4941 (Resolved): Data search causes menus to disappear on the machttps://projects.ecoinformatics.org/ecoinfo/issues/49412010-04-16T19:09:38ZChad Berkleyberkley@nceas.ucsb.edu
<p>If you do a data search on the mac, all of the menus in the menu bar disappear and never return. To recreate, click the data tab, type in a search term, click "search". the menus will disappear.</p> Kepler - Bug #4940 (Resolved): User is never notified of incorrect loginhttps://projects.ecoinformatics.org/ecoinfo/issues/49402010-04-16T18:32:00ZChad Berkleyberkley@nceas.ucsb.edu
<p>When you do a data search and login, if you put an incorrect username or password, then do a search, Kepler never tells you your username/pass is incorrect and tries to do the search anyway.</p>
<p>To recreate:<br />1) go to the data tab<br />2) search for "aphid" <br />3) input a fake username/pass<br />4) click "ok"</p>
<p>Kepler will sit there like it's searching, but if you look at the log, no search is taking place and it will never tell you that the login failed. I'm unsure if the problem is with Kepler not properly handling incorrect login results from the ecogrid or if ecogrid isn't properly notifying kepler of the failed login attempt.</p> Kepler - Bug #4899 (Resolved): Installer Bugshttps://projects.ecoinformatics.org/ecoinfo/issues/48992010-03-23T17:07:01ZChad Berkleyberkley@nceas.ucsb.edu
<p>Tracking bug for 2.0 installer issues.</p> Kepler - Bug #4883 (New): Need more command line options for kar fileshttps://projects.ecoinformatics.org/ecoinfo/issues/48832010-03-15T20:51:05ZChad Berkleyberkley@nceas.ucsb.edu
<p>right now, we can execute a single workflow contained in a kar file with the -runwf command line switch. It would be nice to have more options for working with kar files on the command line. The minimal options I would like to see are:</p>
<p>1) allow the user to specify which workflow within a kar file to execute (if there is >1). <br />2) allow the user to specify the output location. Either a server or local directory.<br />3) allow the use of a remote kar file with an https url (i.e. for a kar file stored in a repository).</p>
<p>Please add more requirements as you see fit. We will add this to the queue of post-2.0 enhancements.</p> Kepler - Bug #4873 (Resolved): Actors in repository library subtree are crammed togetherhttps://projects.ecoinformatics.org/ecoinfo/issues/48732010-03-09T23:53:44ZChad Berkleyberkley@nceas.ucsb.edu
<p>On Windows XP (maybe on other versions of windows) the actor icons are crammed tightly together when you open up Actors-2_0/CoreActors,kar or the other yellow repositories. They should be spaced similarly to the mac.</p> Kepler - Bug #4868 (Resolved): Update R paths in documentation and demoshttps://projects.ecoinformatics.org/ecoinfo/issues/48682010-03-04T17:11:38ZChad Berkleyberkley@nceas.ucsb.edu
<p>The demos path to the R demos should point to the R demos directory, not the outreach demos directory. Make sure this is updated in chapter 8 of the UM and in the demos themselves.</p> Kepler - Bug #4867 (Resolved): Update screenshots for the documentationhttps://projects.ecoinformatics.org/ecoinfo/issues/48672010-03-04T17:07:07ZChad Berkleyberkley@nceas.ucsb.edu
<p>Any screen shots that are out of date should be retaken and updated in the documentation.</p> Kepler - Bug #4864 (Resolved): Update paths in demo workflowshttps://projects.ecoinformatics.org/ecoinfo/issues/48642010-03-03T20:22:43ZChad Berkleyberkley@nceas.ucsb.edu
<p>After RC1 is cut, update all file paths in the demo workflows to use the module-X.0 format.</p> Kepler - Bug #4803 (Resolved): Review the README filehttps://projects.ecoinformatics.org/ecoinfo/issues/48032010-02-17T22:50:30ZChad Berkleyberkley@nceas.ucsb.edu
<p>Need to review the readme for factual accuracy and new content additions.</p> Kepler - Bug #4785 (New): move cache object from 1.0 to 2.0https://projects.ecoinformatics.org/ecoinfo/issues/47852010-02-10T23:13:31ZChad Berkleyberkley@nceas.ucsb.edu
<p>Cache kar objects from 1.0 that contain customized actors (i.e. not those shipped with 1.0) need to be migrated to the 2.0 installation. Any kars that include jars must be made into modules (see bug 4702).</p> Kepler - Bug #4735 (New): Allow params to be passed to ConfigurationManager from the command linehttps://projects.ecoinformatics.org/ecoinfo/issues/47352010-02-04T20:48:06ZChad Berkleyberkley@nceas.ucsb.edu
<p>Need a mechanism for passing params to CM from the command line. This is a post 2.0 feature.</p>