|
Difference between
version 37
and
version 35:
| At line 206 added 2 lines. |
| + !! Taxon-related Plenary Notes |
| + * Need a set of scenarios for the different tasks we are trying to improve and/or enable for our various user groups. They are in peoples' heads and discussed but not really written down anywhere. |
| At line 207 added 19 lines. |
| + * TOS user interaction: |
| + ** could be embedded within data search so user can make decision about what data set to get. |
| + ** or use to extract the rows from a data set? |
| + ** What do the user interfaces look like for user to interact with? |
| + *** What about asking user to pick the best match? |
| + *** What about asking user to rank the authoritative sources then having the system do the concept resolution based on that? |
| + *** Have user specify some level of precision for matching/concept resolution etc.? |
| + |
| + * Establish plan for showing Martin's visualization to collection managers. This is a near term activity. We will structure the feedback and conduct the feedback most likely remotely using technology. General plan is demo the product, demonstrate the current tasks it can support, then get user feedback on tasks they would like to do that it doesn't support. |
| + |
| + * Concept mapper - change connect to DB to read and write TCS documents |
| + |
| + * Kepler actors: |
| + ** There is an actor that does the querying of data and returns concepts (for several species) so this would replace the user using the data tab and getting results and then dragging that data set on to the canvas. (Laura's question). This would then feed into the ENM workflow. |
| + ** Should we have a tool outside or within Kepler for users to configure the data (based on TOS). Users could configure the actor to fire automatically or manually. |
| + ** Jessie feels strongly that the searching should be part of the workflow why is there a data tab separately? |
| + *** One reason is because a search returns multiple objects and then a decision needs to be made of which data sets to use. This was seen as a separate step since the workflow objects/actors are seen as configurable but not necessarily interactive. |
| + *** There are some technical issues within Kepler that have prevented more interactive actors. |
| + |
Back to All Hands Meeting 2005 Taxon Agenda And Notes,
or to the Page History.
|
