List view
- No due date•0/3 issues closed
- No due date•1/6 issues closed
- No due date•0/3 issues closed
- No due date•0/3 issues closed
- No due date•2/3 issues closed
- No due date•0/5 issues closed
- No due date•0/1 issues closed
- No due date•1/1 issues closed
- No due date•1/2 issues closed
- No due date•0/3 issues closed
- No due date•3/7 issues closed
Specification and Plan here: https://docs.google.com/document/d/1kErS6Mjgh7NynbYjd-Z7So7Nnqs60Z7SKNnUU_1joxo
No due date•3/4 issues closed- No due date•1/6 issues closed
- No due date•1/1 issues closed
The next iteration of the Diagram must be scalable, The page loading should be robust for 2x more associations The impact of Diagram generation on the data release must be minimised - Utilize the present SVG User interface alone - Investigate & understand how the data is plotted on the UI - Ascertain the possibility of retrieveing the data using a new and scalable approach - Retire the Old pussycat - Retire the old virtuoso Infrastructure and other supporting technologies (OWL, RDF, ...) - Retire the Old GWAS Diagram Data Release technologies - Use a new approach to generate and present the same data for the SVG Diagram
No due date•2/2 issues closed- No due date•13/18 issues closed
- Overdue by 10 month(s)•Due by May 28, 2025•13/13 issues closed