see: #9031 7 | 1.7.2 | Implementation of UI modules to improve the dataset landing page and access to remote data | 5

[sync-by-unito]

reference:

• Backlog Grooming Board

---

November
(1.7.1, 1.7.2) The first version of White paper has been finished and submitted to the Dataverse open source community and feedback has been collected and incorporated. Conversations have intensified. Working groups have been established around Authentication/Authorization, and UI Modularity. Our contractor Agile Monkeys have helped to create a proof of concept to test preliminary ideas that are needed for the re-architecture effort. The white paper describing the areas of the architecture that need to be addressed and proposed solutions continues to be created.

---

┆Issue is synchronized with this Smartsheet row by Unito
┆!Priority: Normal
┆!State: Approved
┆End Date: 2023-01-31T16:59:59.000Z
┆ItemIDHelper: 0061
┆Start Date: 2022-10-03T08:00:00.000Z

[mreekie]

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: 1) 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, 2) expand and clarify the dataset creation and publishing workflow to make it easier to add a wider variety of data with appropriate metadata, 3) 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.

[mreekie]

Who:

• Bob
• Jim
• Phil
• Ellen

[mreekie]

November
(1.7.1, 1.7.2) The first version of White paper has been finished and submitted to the Dataverse open source community and feedback has been collected and incorporated. Conversations have intensified. Working groups have been established around Authentication/Authorization, and UI Modularity. Our contractor Agile Monkeys have helped to create a proof of concept to test preliminary ideas that are needed for the re-architecture effort. The white paper describing the areas of the architecture that need to be addressed and proposed solutions continues to be created.

[mreekie]

deprecated and closed