Skip to content

Docs: describe metadata conventions on single-modality derived assets - #236

Open
dougollerenshaw wants to merge 1 commit into
mainfrom
232-clarify-derived-asset-metadata
Open

dougollerenshaw wants to merge 1 commit into
mainfrom
232-clarify-derived-asset-metadata

Conversation

@dougollerenshaw

@dougollerenshaw dougollerenshaw commented Oct 3, 2026 •

Copy link
Copy Markdown
Contributor

Closes #232.

Clarifies the metadata conventions for each of the single-modality derived assets that are produced by multiple parallel single-modality processing pipelines (e.g. behavior and ephys)


📚 Documentation preview 📚: https://scicomp-docs--236.org.readthedocs.build/en/236/

@tmchartrand

Copy link
Copy Markdown
Member

I'd suggest a bit less detail here and linking to https://aind-data-schema.readthedocs.io/en/latest/inheritance.html instead. at the very least, add the link and edit the processing bullet to be compatible (pipeline processing should be added to any existing processing)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Clarify how metadata is handled for single-modality derived assets

3 participants