Skip to content

Enforce canonical naming in categorical upload fields #18

Description

@quasimik

This is related to #17 .

So here's the problem:
Screenshot from 2020-02-17 13-33-54
"Peter Reiher", "Peter Rieher", "Reiher", and "Reiher, Peter L." are obviously all the same professor. How do you prevent this kind of mislabeling and resulting name fragmentation?

I think we should pick a canonical name for Reiher, let's say, "Peter Reiher". Then, we put this somewhere in the database (probably in a professors collection), and enforce this in the test file upload form.

The same also applies to other "categorical" fields, like course subject ("COM SCI"), kind name ("Midterm"), and term quarter ("Winter").

A good idea is to reuse a subset of the Autocomplete search bar already implemented in the main course search page (also seen in the screenshot above):

<Autocomplete
className={classes.filterAutocomplete}
autoComplete
multiple
id='grouped-filter'
options={filterOptions}
groupBy={option => option.fieldDisplay}
getOptionLabel={option => option.display}
filterSelectedOptions
onChange={handleFilterItemsChange}
renderInput={params => (
<TextField
{...params}
onClick={handleOpenFilterBar}
label='Filter / Search'
variant='outlined'
fullWidth
/>
)}
ChipProps={{ color: 'primary' }}
/>

Finally, how do we allow people to add new professor names? Maybe we can allow this later by having a "My professor isn't listed" button that leads into a flow allowing them to add a new professor. We should think of other ways to allow such a thing, while still keeping name fragmentation to a minimum.

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions