You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Text from our P&S proposal where discussed:
Initially, the ToolMatch service was developed to solve two simple but prevalent use cases. The first use case involves the fact that, for a given dataset, the visualization tools that can be used to work with that data collectionthe dataset, (e.g., by reading, rendering, and mapping the data) are difficult to find. What a user needs to do is to be able to search for the tools that can be used with a given dataset, and then find out what the tool can do with that dataset.
The second use case is a converse of the first: for a given data tool, it can be difficult to find datasets that will work with the tool most appropriately, and also to find data users who can provide the feedback necessary to build comprehensive and sustainable frameworks and methods of access / use of a tool. What a tool developer needs to do is to be able to search for datasets that can be used with their tool, and to capture information about what the data user would like to be able to do with their data in the shorter and longer terms.
Since our initial scoping of the ToolMatch service, a third use case has been proffered that is the subject of a Funding Friday proposal by one of the ToolMatch team members, Matthew Ferritto. This use case extends the initial two by adding another condition where a dataset user with certain semantics in mind for a given dataset (such as a domain model), wants to find tools that can be used with the content of that data. For instance, a researcher who has identified certain types of rainfall or topological measurements with a hydrological model wants to know what tools will work with the measurement data.
Patrick's comments from proposal:
This is new and is not yet modeled. this, to me, would be a new use case. The second use case is to find a collection of data that can be used with a given tool. A fourth use case (Matt's is the third) is that now that one has found the data collection that works with their tool they want contact information for that data collection to learn more about the collection, have users try out the tool, or for whatever reason.
Nancy's comments from proposal:
I disagree that this is another use case, but rather further context for the data users described in the first part of the sentence.
The text was updated successfully, but these errors were encountered:
Text from our P&S proposal where discussed:
Initially, the ToolMatch service was developed to solve two simple but prevalent use cases. The first use case involves the fact that, for a given dataset, the visualization tools that can be used to work with that data collectionthe dataset, (e.g., by reading, rendering, and mapping the data) are difficult to find. What a user needs to do is to be able to search for the tools that can be used with a given dataset, and then find out what the tool can do with that dataset.
The second use case is a converse of the first: for a given data tool, it can be difficult to find datasets that will work with the tool most appropriately, and also to find data users who can provide the feedback necessary to build comprehensive and sustainable frameworks and methods of access / use of a tool. What a tool developer needs to do is to be able to search for datasets that can be used with their tool, and to capture information about what the data user would like to be able to do with their data in the shorter and longer terms.
Since our initial scoping of the ToolMatch service, a third use case has been proffered that is the subject of a Funding Friday proposal by one of the ToolMatch team members, Matthew Ferritto. This use case extends the initial two by adding another condition where a dataset user with certain semantics in mind for a given dataset (such as a domain model), wants to find tools that can be used with the content of that data. For instance, a researcher who has identified certain types of rainfall or topological measurements with a hydrological model wants to know what tools will work with the measurement data.
Patrick's comments from proposal:
This is new and is not yet modeled. this, to me, would be a new use case. The second use case is to find a collection of data that can be used with a given tool. A fourth use case (Matt's is the third) is that now that one has found the data collection that works with their tool they want contact information for that data collection to learn more about the collection, have users try out the tool, or for whatever reason.
Nancy's comments from proposal:
I disagree that this is another use case, but rather further context for the data users described in the first part of the sentence.
The text was updated successfully, but these errors were encountered: