You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just published the new archive explorer. Here are some ToDos for the future, ideally for @93Boy. Generally each of them deserves an own Pull Request, but maybe the map-related ones can be solved in one go.
The per-sample popups in the map should only show the information we actually have for a given sample, so the empty fields should be omitted.
The sample popups should also have a button to open the relevant per-package page.
Modern and ancient samples should be distinguished by marker shape in the map (although the marker clusters generally omit the individual markers, admittedly...)
Currently possible changes beyond the map:
The per-package pages should include some more summary statistics for the package. E.g. How many modern/ancient samples are in the package? How many are male/female/unknown? What is the mean number of SNPs?
We should get a clever mechanism to attribute each per-package page an own URL, so that they can be referenced directly.
List old package versions on the per-package pages.
Changes that will be possible in the future with a more beefed-up version of the Web API:
Load detailed sample information for the per-package pages only per package to safe bandwidth.
Display more general meta/context information (e.g. contributors) for each package on the per-package pages.
Render the package changelog on the per-package pages as we did for the old homepage.
Render the literature references on the per-package pages as we did for the old homepage.
@stschiff Do you agree with this? Feel free to add or change any of these suggestions.
The text was updated successfully, but these errors were encountered:
I just published the new archive explorer. Here are some ToDos for the future, ideally for @93Boy. Generally each of them deserves an own Pull Request, but maybe the map-related ones can be solved in one go.
Currently possible changes for the map:
Currently possible changes beyond the map:
Changes that will be possible in the future with a more beefed-up version of the Web API:
@stschiff Do you agree with this? Feel free to add or change any of these suggestions.
The text was updated successfully, but these errors were encountered: