Skip to content

Alternatives doesn't indicate terms that should not be used #33

@kellijohnson-NOAA

Description

@kellijohnson-NOAA

The 'Alternative' category in the .R files does not delineate between terms that should and should not be used. Alternatives, perhaps this should be renamed and/or a new category should be added such as synonyms. I am just trying to work out how users will know which term they should use if an alternative also has a definition and the words are essentially synonyms. Or, would the previous NEVER happen because synonyms would only be listed in the alternative category and not have their own .R file. This is coming up for me because of forecast vs. projection. They are not really alternatives of each other but I would like some way to link them so users know they should look at both definitions before deciding which term applies to their situation.

Metadata

Metadata

Assignees

No one assigned

    Labels

    questionFurther information is requested

    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