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

Prototype for storing single-cell data #1020

Draft
wants to merge 298 commits into
base: development
Choose a base branch
from
Draft

Conversation

arteymix
Copy link
Member

@arteymix arteymix commented Feb 5, 2024

TODO

  • add a CLI for loading/reloading single cell data and cell type assignments
  • extend the GEO loader to detect MEX and other supported formats and apply the appropriate strategy for loading vectors
  • Add support for HDF5-based single-cell data formats #1039
  • support saving single cell data to disk (I already added a SingleCellExpresionDataMatrix, we need to finish the work and write it to file). I think MEX is a pretty decent output format for this.

REST API

  • review which fields should be exposed on the REST API for filtering purposes
  • add aliases in the REST API to refer to the preferred single cell dimension and cell assignment

@arteymix arteymix force-pushed the feature-single-cell branch 6 times, most recently from 9222a95 to 788a61b Compare February 7, 2024 20:13
@arteymix arteymix force-pushed the feature-single-cell branch 2 times, most recently from f04ae2f to d791771 Compare February 7, 2024 20:23
Remove Serializable and serialVersionUID to classes that we never
serialize or put on disk caches.

Relocate some utility methods from the models into utility classes.

Replace LocalFile by java.io.File.
Provide multiple strategies for mapping gene IDs and pick the one with
the greatest overlap.

Include mapping statistics in the audit event for the created
single-cell vectors.
Display the biomaterial and bioassay hierarchy.
Remove JAWR and any mention of it in the code and comments.

Add support for Webpack development server for serving continuously
built static assets.
Add resolveUrl and use that in the tags to generate link to resources.

Add a list of allowed directories to serves assets from. It does not
really do much security-wise, but it will catch unintended usages of the
JSP tags.

Add a useful message when the development profile is active and the
server is not running.
Ensure that the appropriate assets are built when deploying to staging
or dev servers.
Include annotations applicable at the subset-level.

Handle case where there might be more than one dimension for a given
subset.
Generate all the DWR scripts and controllers with appropriate binding to
the window object.

Separate models from controllers.

Add overrides such as adding GA4 tracking and defining inheritance
structure in a separate file.
Ensure that all declared function are properly namespaced.
Rewrite the edit page with Spring form tags.

Enable HTML escaping by default for Spring tags.

Allow for dynamic JSP attributes to be used for various tags.
@arteymix arteymix linked an issue Nov 23, 2024 that may be closed by this pull request
8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment