Retain the functionality that allows the template author to define preferred (or required) standards.
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 standards list to show metadata standards appropriate for that area. Or (a more advanced thing) if the funder is NIH and we know they require certain standards, we can tap into the metadata standard's extended metadata to prefer or somehow highlight ones that are compliant with that funder's needs.
We need to define what we want the metadata standard selector to look like and its overall functionality.
Here is what it looks like in the current tool:
It offers a basic search field and otherwise behaves the same way that the current repository selector works (see screenshots in issue #25).
We get the metadata list from a combination of:
In the new system we want:
Biologyresearch domain, we could pre-filter the standards list to show metadata standards appropriate for that area. Or (a more advanced thing) if the funder is NIH and we know they require certain standards, we can tap into the metadata standard's extended metadata to prefer or somehow highlight ones that are compliant with that funder's needs.See the corresponding AWS infrastructure ticket