Complex question type: Repository selector

[briri]

We need to define what we want the repository selector to look like and its overall functionality.

The current DMPTool's repo selector looks like this:

It offers some basic filters and a search box. The template admin is able to customize the initial list that the user is presented with (preferred repos). The user selects a repo by clicking the 'Select' button. The smaller blue pills contain keywords related to that repo. Clicking on one of those pills presents the user with all of the repos that use that keyword.

Once the user selects an item it appears on the underlying research output page:

The user can 'Remove' the repo from this page or click the button to add more repos.

In the new system we want:

• Retain the functionality that allows the template author to define preferred (or required) repositories. For example some institutions may require that a copy of the research output be placed into their institutional repository. The user would still be able to submit to other repos in that scenario.
• Provide more robust filter/facet controls along with the search box
• Consider other information provided elsewhere in the plan creation process. For example if they specify that their project is in the Biology research domain, we could pre-filter the repository list to show repositories that specialize in that area. Or (a more advanced thing) if the funder is NIH and we know they require the outputs to have a DOI and certain access methods, we can tap into the repository's extended metadata to prefer or somehow highlight a repository as being compliant with that funder's needs.
• MIT has a good example we can learn (borrow) from:
  • A page discussing some of the considerations/guidance for selecting: https://libraries.mit.edu/data-management/share/find-repository/
  • Here is their finder tool: https://data-repository-finder.ll.mit.edu
• Re3data itself (where we get the repository list and metadata from) is also a good source for inspiration:

See the corresponding AWS infrastructure ticket

[jupiter007]

Thanks @briri. This almost seems like a UI/UX ticket, and subsequent work for frontend can be blocked by this one. Should we add a label for UI/UX work?

[briri]

Yeah I think that's a good idea