Skip to content

Docs: extend description of derived data naming conventions - #237

Open
dougollerenshaw wants to merge 1 commit into
mainfrom
231-clarify-derived-asset-naming
Open

dougollerenshaw wants to merge 1 commit into
mainfrom
231-clarify-derived-asset-naming

Conversation

@dougollerenshaw

@dougollerenshaw dougollerenshaw commented Oct 3, 2026 •

Copy link
Copy Markdown
Contributor

Closes #231

Extends the discussion about derived asset naming conventions in data_organization.md. Steers users away from simply using 'processed' as a label.


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

@arielleleon arielleleon left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is much better, thank you. One small comment

Comment thread docs/source/policies_practices/data_organization.md
@arielleleon

Copy link
Copy Markdown
Collaborator

Good call regarding the fiber pipeline. I don't want to add project specific logic to pipelines like fiber but if users want to have a process label such as behavior-df, I'm not opposed to that.

@tmchartrand

Copy link
Copy Markdown
Member

this is a pretty big change to not suggest using the generic "processed" at all. I'm not sure the original context of that, so might be helpful to at least document that in this discussion before discarding. do we want to suggest users doing more ad-hoc reprocessing outside of a standard pipeline use that instead of making up new short-names for instance?

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 the derived data data naming convention description.

3 participants