Kepler: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362007-09-12T01:09:33ZEcoinformatics Redmine
Redmine Bug #2969 (New): Ability to join tables _across_ EML data packageshttps://projects.ecoinformatics.org/ecoinfo/issues/29692007-09-12T01:09:33Zben leinfelderleinfelder@nceas.ucsb.edu
<p>Ability to join tables <em>across</em> EML data packages or even non-EML actors.<br />Hopefully leverage some of the org.ecoinfomatics.datamanager library (eml module).</p> Bug #2968 (New): Ability to join tables within same EML data packagehttps://projects.ecoinformatics.org/ecoinfo/issues/29682007-09-12T01:06:11Zben leinfelderleinfelder@nceas.ucsb.edu
<p>Ability to join tables within same EML data package.<br />This does exist on the backend...just have UI issues with it being clear and easy-enough-to-use.</p> Bug #2964 (New): Change RExpression plotting actors to allow custom axis and title labelshttps://projects.ecoinformatics.org/ecoinfo/issues/29642007-09-12T00:53:57Zben leinfelderleinfelder@nceas.ucsb.edu
<p>If/When metadata is being passed around with workflow tokens, use the information contained within that to set the labels for chart axis, title etc...</p> Bug #2962 (New): Add metadata to data tokens so that it can be used downstreamhttps://projects.ecoinformatics.org/ecoinfo/issues/29622007-09-12T00:42:02Zben leinfelderleinfelder@nceas.ucsb.edu
<p>Add metadata to data tokens so that it can be used downstream (e.g., names, descriptions, units, travel with data).<br />Would be useful for plotting in the R actor (among other things) so that axis can be labeled in a meaningful way.</p> Bug #2123 (New): need a way to uniquely identify actor in a workflow and locate ithttps://projects.ecoinformatics.org/ecoinfo/issues/21232005-06-13T19:25:10ZLaura Downeyldowney@lternet.edu
<p>need a way to uniquely identify actor in a workflow that is exposed to the <br />user so that if one person says look at actor X in workflow y, they know <br />exactly which one is being referenced. There could be many of the same kind <br />of actors in a workflow and users need a way to uniquely identify a specific <br />actor.</p>
<p>This could be done by making use of and exposing the actor ID. It could be <br />exposed in the general tab on the new proposed tabbed configuration dialog for <br />an actor.</p>
<p>Searching by actor ID could be added to the advanced search.</p>