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

Dead links in OPG #468

Open
mauromiguelm opened this issue Jun 13, 2023 · 13 comments
Open

Dead links in OPG #468

mauromiguelm opened this issue Jun 13, 2023 · 13 comments
Labels
bug Something isn't working uncloseable This issue is written such that the conditions to close the issue can never be acheived.

Comments

@mauromiguelm
Copy link
Contributor

on geneset enrichment, some of the links are directing to "gene set not found" on GSEA website

image

see user feedback

@mauromiguelm mauromiguelm added the bug Something isn't working label Jun 13, 2023
@ncullen93
Copy link
Contributor

Assuming you mean the Enrichment analysis table in the Geneset enrichment page:

Screen Shot 2023-06-14 at 11 13 47 AM

I'm marking this issue as uncloseable, since we can never know when "some of the links" are fixed. I would recommend that we either get a list of the specific links that were broken for the user, or we repurpose this issue to creating a catalogue all of the links that are broken for a specific dataset or two. But going through 2000+ links manually sounds tough.

@ncullen93 ncullen93 added the uncloseable This issue is written such that the conditions to close the issue can never be acheived. label Jun 14, 2023
@mauromiguelm
Copy link
Contributor Author

I agree, we could have a report form for when people find deadlinks in the table itself... there will be future challenges as API changes, websites down, renaming of genesets, etc...

so we need to activelly fix these things, as it seems they are important to the users!

@ncullen93
Copy link
Contributor

ncullen93 commented Jun 15, 2023

Ah that's a beautiful idea. It would be possible to extend this idea to include a caution icon or report icon in all plotmodules that would dropdown to a textareainput so that users could easily submit an issue for any given plot. then the report could get emailed to us.

@mauromiguelm
Copy link
Contributor Author

would be useful for bugs and suggestions in general, we can discuss with Ivo and see how to move forward. I would love see this implemented.

@mauromiguelm
Copy link
Contributor Author

I will reopen this, as we might have a solution that applies to many cases:

One solution would be for the user to be able to report broken links (or plots, tables) directly in the plot or table. What do you think?

User reply: Yes that would be a nice way implement noting dead links.

Should we use this approach @ivokwee?

@mauromiguelm mauromiguelm reopened this Aug 9, 2023
@ncullen93
Copy link
Contributor

Should the "report" icon be added to the plotmodule / tablemodule in general so that it's on every plot/table? Then if a user reports something as not working, we can pull info from the environment / settings that caused it?

@mauromiguelm
Copy link
Contributor Author

I think that would be great, both for suggestions and issues. For example, certain datasets might create plot problems, and would be nice if the user could report to us.

Let's get the ok from @ivokwee as this is a big change.

@ivokwee
Copy link
Member

ivokwee commented Aug 9, 2023

I don't like the reporting thing. Before that we should investigate why the links are not working. You do not need to check 2000 links manually, you can create a simple loop and do a curl to check them all. In any case, if you get them from external DB there must be a link.

@ivokwee
Copy link
Member

ivokwee commented Aug 22, 2023

I don't like asking users to actively debug dead links. Looks like we ship broken stuff. Better disable the link. Again, we could just test each link in a loop if needed.

@ncullen93
Copy link
Contributor

No, maybe asking users to report dead links for us is a bit much. They should just work. @mauromiguelm mentioned that it wasn't as simple as running curl because the links do return something but just not the right info? Is that right?

@mauromiguelm
Copy link
Contributor Author

correct, the link works, but the database cannot find the entry, as image below, and returns a standard page. I dont see any easy solution other than Beautiful Soup or some report button.

on geneset enrichment, some of the links are directing to "gene set not found" on GSEA website

image see user feedback

@ivokwee
Copy link
Member

ivokwee commented Aug 22, 2023

So you can grep on 'geneset not found'... But again I think we should find out why a certain gene set is not found: any extra spaces? Newline? Non UTF8 chars? Can you give me an example of a geneset that is not there?

@ESCRI11
Copy link
Contributor

ESCRI11 commented Aug 24, 2023

Did some research, looks like all C5 genesets links are broken, have not found any other broken link on different genesets.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working uncloseable This issue is written such that the conditions to close the issue can never be acheived.
Projects
None yet
Development

No branches or pull requests

4 participants