Skip to content

Conversation

@jstone-dev
Copy link
Collaborator

  • Consume the revised score set search endpoints, which return total result counts along with results.
  • Obtain score set search filter options from a separate API request.

@jstone-dev jstone-dev changed the title Jstone dev/score set search result optimization Score set search result optimization Sep 30, 2025
@jstone-dev jstone-dev changed the base branch from release-2025.4.1 to release-2025.4.2 October 1, 2025 01:24
@jstone-dev jstone-dev marked this pull request as ready for review October 1, 2025 15:32
Copy link
Collaborator

@bencap bencap left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good pending any changes from the API side of things.

},
fetchFilterOptions: async function () {
try {
const requestParams: SearchParams = {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it'd be nice (although not necessary) to explicitly define the limit here. Should we eventually overhaul the search we could revisit the value but to me an explicit limit here is just an improvement in every case. There's no reason to ever have a result set that's 3000 score sets long on a single page (and I'm sure Alan would thank us 😄).

Depending on what you think about the page suggestion from VariantEffect/mavedb-api#525 (review) we would also add that here along with a next/previous UI element.

Base automatically changed from release-2025.4.2 to main October 3, 2025 23:35
@bencap bencap changed the base branch from main to release-2025.4.3 October 3, 2025 23:37
@bencap bencap linked an issue Oct 4, 2025 that may be closed by this pull request
Base automatically changed from release-2025.4.3 to main October 13, 2025 17:50
@bencap bencap changed the base branch from main to release-2025.4.4 October 13, 2025 17:53
Base automatically changed from release-2025.4.4 to main October 13, 2025 19:40
@bencap bencap changed the base branch from main to release-2025.4.5 October 13, 2025 19:54
Retrieves AlphaFold model version from API to be included in CIF file URL, rather than hardcoding, to prevent 404s when old file versions are purged by AlphaFold.

Goes with [#VariantEffect/mavedb-api/davereinhart/alphafold-files-version-proxy](VariantEffect/mavedb-api@590844e)
…h terms

- Adds support for ClinGen allele IDs, dbSNP rs IDs, and ClinVar Variation IDs.
- Dynamically determine search type based on search term and make appropriate request to ClinGen Allele Registry
- Add examples to page for newly supported search terms
- Support return of multiple alleles from ClinGen Allele Registry request
@bencap bencap changed the base branch from release-2025.4.5 to release-2025.4.6 October 24, 2025 17:05
davereinhart and others added 7 commits October 24, 2025 15:52
…fold-cif-version

ProteinStructureView: dynamic AlphaFold model file version
…rror message generation

- Adds fixed width to search type dropdown
- Add search examples to searchTypeOptions for dynamic generation of HTML elements and error messages displayed via toast
- Add support for seaching via dbSNP rs IDs without rs prefix
…-options

Add MaveMd search options for ClinGen Allele IDs, dbSNP rs IDs, and ClinVar Variation IDs
The search endpoint now returns a limited set of results, so a complete list of options for further filtering the result set cannot be obtained from the result set.
@jstone-dev jstone-dev force-pushed the jstone-dev/score-set-search-result-optimization branch from 30a06b9 to 782095d Compare November 5, 2025 21:22
@jstone-dev jstone-dev merged commit 289f458 into release-2025.4.6 Nov 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Long score set search result optimization

4 participants