Ask a categorizer for name and initials on their first login

[ZhongweiL]

Intends to resolve issues #100 and #132 Potential issue: A logged-in categorizer could change the URL to access and submit the form multiple times(with different names and initials) to create multiple entries in the categorizers table. I don't think the database prevents the user from doing that.

Tests:

• Created a user on the admin's page and add that user as a categorizer. Then logged in as the user. The user got directed to the categorizers form. The user fills in the name and initials then submits the form. A new entry with that info appeared in the categorizers table.
• Created a user on the admin's page without adding that user as a categorizer. The user was not directed to the categorizers form after login.
• Created a user on the admin's page and added that user as a categorizer. Then logged in as the user. The user got direct to the form but changed the URL to access the home page. The view categorization option did not appear on the home page, the user tried to access them by changing the URL to the categorizations page but was denied access. After the user submitted the categorizers form with name and initials, the view categorization option appeared on the home page and the user was able to view and add categorizations.

[khatchad]

@ZhongweiL How was this tested and what were the results?

[khatchad]

Also:

Intends to resolve issues #100 and #132 Potential issue: A logged-in categorizer could change the URL to access and submit the form multiple times(with different names and initials) to create multiple entries in the categorizers table. I don't think the database prevents the user from doing that.

Was this potential issue solved?

[khatchad]

Looks like there's some test plans here: https://github.com/ponder-lab/Imperative-DL-Study-Web-App/issues/132

[ZhongweiL]

Also:

Intends to resolve issues #100 and #132 Potential issue: A logged-in categorizer could change the URL to access and submit the form multiple times(with different names and initials) to create multiple entries in the categorizers table. I don't think the database prevents the user from doing that.

Was this potential issue solved?

I've been looking into some documentation for one-to-one relationships and I think this might satisfy our needs. https://docs.djangoproject.com/en/3.2/ref/models/fields/#django.db.models.OneToOneField