carpentries / amy

A web-based workshop administration application built using Django.
https://amy.carpentries.org
MIT License
113 stars 72 forks source link

Comments from review of AMY docs and corresponding UI operations #2328

Open elichad opened 1 year ago

elichad commented 1 year ago

Dumping all my notes from a thorough read of the AMY docs and corresponding operations on the test server. Many of them are small things and I'll make a PR to fix as many of those as possible. Some probably deserve their own issues.

Questions:

Outdated things in docs:

Miscellaneous issues:

Accessibility issues:

Moved to #2332

maneesha commented 1 year ago

what criteria make an instructor or other Person 'active' vs 'inactive?' Am I right in thinking that people are made inactive manually? under what criteria would you archive a Person?

These are both part of the soon-to-be-defined archival process; there is no current system.

maneesha commented 1 year ago

Training requests: Is there any particular reason why we allow matching trainees to multiple TTT events? I expected it'd throw an error but it didn't.

Yes, someone can be matched to multiple TTT events if the had to re-take a training.

maneesha commented 1 year ago

Organization: Affiliated organizations not used - hide/remove?

This is another example of a feature that was implemented but not fully thought through. We had wanted to be able to identify organizations that are identified with each other through their own networks (not through The Carpentries).

For example, in the United States, there is the University of California system. Within that, there are many colleges and universities (University of California Los Angeles, University of California Irvine, University of California San Francisco, etc...). We wanted to be able to identify all organizations that were part of a given network.

The relationship matching was difficult to enforce. We never used this feature, and should consider whether we want to keep it.

maneesha commented 1 year ago

@elichad can put in PRs to update these items:

  • Membership: Person roles (Trainer missing from docs)
  • Event: URL validation error suggests pointing to a github repo rather than a github.io site
  • url_validation_out_of_date
  • Docs: various references to separate DC/LC/SWC badges/demos/instructors etc
  • Find workshop staff: Badge filter has been changed to a couple of checkboxes

For this item:

Add Person to Event: Title and URL are not used - hide/remove?

That's correct - we aren't using those fields. This was brought up for in this issue which I said I'd start on but never did... this would be a good issue for @elichad

maneesha commented 1 year ago

For all of the accessibility issues - we are planning to do a comprehensive accessibility audit of AMY this year. @elichad can you open a new issue that is a log of all accessibility issues we come across so we have a good starting point for that?

elichad commented 1 year ago

dropdowns start to 404 if the page is kept open for a long time (5-10 min), displaying "The results could not be loaded." I assume this is a form timeout and possibly deliberate? But it's not that clear that that's what's happening.

From django-select2 docs:

The timeout of select2’s caching backend determines how long a browser session can last. Once widget is dropped from the cache the json response view will return a 404

We can configure the timeout of the Django cache used for select2 if we want - the default is 300 seconds.

Note that the current behaviour is technically a WCAG failure under 2.2.1 Timing Adjustable.