AllenInstitute / AllenInstitute/ConnectsCommonConnectivity
AIT schema comparison + adapter/migration strategy
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 4
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Task: review the AllenInstituteTaxonomy schema and compare it to CCM's clustering schemas (Cluster, ClusterHierarchy, ClusterMembership, AlgorithmRun) — field-mapping memo.
Context: AIT is a spec (anndata h5ad + markdown/CSV schema; R tooling) — no releases, no pip package, actively evolving.
Versioning approach: pin a specific AIT commit as our de-facto version; maintain a migration script for switching pins; conformance test against one published taxonomy from their taxonomies.md breaks loudly on drift. Coordinate with the hmba_taxonomy_annotation_schema.yaml draft (@morriscb branch).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the AllenInstituteTaxonomy schema and comparing it with CCM's Cluster, ClusterHierarchy, ClusterMembership, and AlgorithmRun schemas. Review taxonomies.md and the hmba_taxonomy_annotation_schema.yaml draft, then define the field-mapping memo, pinned AIT commit, migration script, and conformance test; done means drift causes the test to fail clearly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jupyter-notebook, r, yaml
- Domain
- data, data-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100