ucdavis / ucdavis/ipa-client-angular
Design: Scheduling View
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 2
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Why do we have two filter drop-downs?
Is there a better way to accommodate the SOE / Arts Group style calendar?
Could we use drop-downs with checkboxes to hide a lot of this information, e.g. do they need to see the section groups once they've selected one, or could the list of SGs collapse into a drop-down above?
Activity date/location editing is important but we currently give about 1/8 of the page to this activity.
The calendar gets too dense too quickly.
The calendar needs the ability to drag items around.
Are there examples of programs like this that have better interfaces?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not name a file, entry point, or test. Begin by locating the existing scheduling view and documenting its current filters, calendar density, editing behavior, and drag interactions; clarify the desired SOE/Arts Group workflow and identify comparison interfaces before defining what a completed design should include.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angularjs, javascript
- Domain
- design, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100