Skip to content

propose a naming scheme #2

Description

@afolarin

questionnairedataanalysis is too generic. It might be useful to have a canonical naming scheme for the pipelines (my preference would be to name these after the feature they generate (if they are feature generating pipeline) or after the output (e.g. if data loading or preprocessing pipeline). That said this is not necessarily straightforward e.g. QuestionnaireCompletionTime and QuestionnaireNotificationResponseLatency are two output types in this particular pipeline -- I'd suggest therefore something like questionnairetimefeatures or similar.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions