Below is the slideshow of our project blueprint — which lays out the plan for the year.
As part of this User Experience project, we spend a lot of time talking to people about how they interact with HydroShare and hydrology data. It’s important, with all of this user data, to have a framework for capturing all of this data so that we can learn from it later. So…
Our team are not hydrology experts, and hadn’t used the software before. For some initial investigation into HydroShare, we went through a task list of the most common uses / workflows in the HydroShare environment. The landing page for HydroShare looks as follows:
By the end of this semester, we’ll need to produce a report on our progress thus far and our plan for next semester. In order to prepare for that, we’re thinking now about our project narrative and what we hope to deliver in the future.
We’ve started with user interviews, and we’re focusing on getting to know WHO they are. That sounds redundant, or at least a little simplistic, but it’s true. We’ve been talking to some graduate students from the University of Washington, getting to know why they got started with the…
This is where we will be documenting our findings! Yay
