NIH AIM:7 YR:2 TASK:1 & 2 | 2.7.1 & 2.7.2 | UI related work
mreekie opened this issue · comments
| Task | Aim | Description |
|---|---|---|
| 2.7.1 | 7 | Research and design of UI modules for creating datasets and supporting publishing workflows |
| 2.7.2 | 7 | Implementation of UI modules for creating datasets and supporting publishing workflows |
For year two we are going to stay the course with the SPA creation with the aim of satisfying these deliverables.
┆Issue is synchronized with this Smartsheet row by Unito
This issue represents a deliverable funded by the NIH
This deliverable supports the NIH Initiative to Improve Access to NIH-funded Data
Aim 7: Improve the user experience and interface (UX&UI) and Application Programming Interfaces (APIs) for depositing, viewing, and accessing datasets in the repository to facilitate its use and modularity
To expand the use of generalist repositories among NIH-funded researchers, repositories must be easy to use, meet applicable WCAG 2.1 Level AA accessibility standards adopted by Harvard University, and keep the complexity and best practices of a FAIR repository. Understanding what users expect and designing the interface to be clear for all are keys to make wide adoption successful.
We propose to improve three areas of the repository UI:
- facilitate discovery and exploration of data by making it easier to customize collections of datasets, identify types of data more clearly, expand and improve tools to explore data within repositories,
- Expand and clarify the dataset creation and publishing workflow to make it easier to add a wider variety of data with appropriate metadata,
- Extend the RESTful APIs in the Dataverse software to enable more easily separating the backend web services that support the core Dataverse functionality with the frontend, and build scalable and flexible open-source UI modules for the Harvard Dataverse repository, usable by other repositories.
All UX&UI enhancements will include conducting automated and human reviews for accessibility compliance, product research, and user testing.
First draft to start March 2023 update
Work concentrated in these areas this month. Infrastructure to support automated testing including containerization. Automation of deployment of the UI components. Standardization on a UI design tool. Initial strawman React based SPA as a step towards the MVP.
updated complete: 3%
Google doc with stats for month
I reviewed this entry in the Year 2 Planning (starts March 2023) NIH OTA Copy. There are no special instructions on this for year 2. We are in a good place and are going to stay the course.
Fixed typo in title: duplicated 2.7.1 -> 2.7.2