Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Determine which resources from the DBL can be opened in P10S now and filter out the rest #1395

Open
lyonsil opened this issue Dec 13, 2024 · 3 comments
Labels
enhancement New feature or request ux UX design needed

Comments

@lyonsil
Copy link
Member

lyonsil commented Dec 13, 2024

User Story
As a user who wants to download resources, I only want to see resources that I can successfully open. Resources that will fail to open should be excluded.

Description
Details about why some resources fail to open is in #1344.

Implementation idea
The idea of this ticket is to write a script or in some other way quickly identify which resources will not open properly from the DBL. Then update the download resources UI to exclude that list until we can successfully migrate all the resources to the latest version.

Testing ideas
If there is a way to automatically verify that P10S can open all remaining resources that would cover this ticket.

@lyonsil lyonsil added enhancement New feature or request ux UX design needed labels Dec 13, 2024
@lyonsil lyonsil added this to Paranext Dec 13, 2024
@lyonsil lyonsil added this to the 2025 Q1 (Internal Milestone) milestone Dec 13, 2024
@lyonsil lyonsil moved this to 📥 For Consideration in Paranext Dec 13, 2024
@Sebastian-ubs
Copy link
Contributor

Sebastian-ubs commented Dec 20, 2024

If this is a short term solution, fine, if it should be released we should indicate in the ui why a user would not find expected resources @paranext/paranext-ux e.g. maybe by showing them, but disabled.

Considered alternatives were

  • show all, but have a timeout and indicate failure (as well not the best ux)
  • maybe implementing the converter for old resources will not take too much effort (preferred)

@Sebastian-ubs
Copy link
Contributor

@rolfheij-sil fyi the existence of this issue looks like it is unlikely that the conversion will be quick

@merchako
Copy link
Contributor

As a UX issue,

  • How might we help users voice their desires for non-qualifying resources to be updated to work with USFM3.1 and Studio?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request ux UX design needed
Projects
Status: 📥 For Consideration
Development

No branches or pull requests

3 participants