Skip to content

Home

Jump to bottom
Cameron King edited this page Aug 2, 2020 · 11 revisions

Welcome to the universityofscouting wiki!

Scope

Volunteers registered with Longhorn Council will be able to view past University of Scouting transcript data (if such data is available) and see classes and scheduled for the current year.

Iteration 1 Deliverables

  • Complete - A registered member can login to the site using information which he/she already knows
  • Complete - A registered member can view available transcript data on a desktop or mobile device
  • Complete - A registered member can print past transcript data in a format resembling that of a university transcript

Iteration 2 Deliverables

Skipped. MongoDB.com and Compass will be used to manage data in the immediate term.

Iteration 3 Deliverables

  • Complete - A registered user can view courses they are signed up for
  • Complete - A registered user can see times, physical, and online meeting places for courses they are signed up for

Development

As far as the developers are aware, there is not a ready-made tool to do exactly what we need that also provides a positive user experience. As such, something custom must be created. Custom tools are always a risk in volunteer-run organizations, so we strive to abide by the following principles as best we can, to ensure that someone else will be able to pick up the baton, should it ever fall from our hands.

  • We shall strive to use modern, well supported tools. By choosing tools that are widely used and in current use, we increase the odds that at some point in the future another developer may come along who is familiar with the technology.
  • We shall keep it simple. We will avoid solutions which are overly complex, when a simpler solution is capable of accomplishing the same task.
  • We shall document our code and methods. Documentation will make our code more understandable, both for ourselves and others who are interested in it.
  • We shall code with good style. We will use automated code processing tools to ensure that best practices are followed regarding code style, to reduce the difficulty in maintaining the code.
  • We shall help the community by publishing this code under a permissive open source license. This ensures that future developers, and possibly those with other councils, do not find themselves bound by copyright restrictions should future alterations be required.

Roadmap

  • Iteration 1 - Feature. Read only by users: view on web or print.
  • Iteration 2 - Maintenance. Faculty/admin export and import of data via. CSV.
  • Iteration 3 - Feature. Course catalog and viewing online meeting information.
  • Iteration 4 - Maintenance. Faculty can update individual record metadata, such as completions for students who attended class.

Reference

Demos

Clone this wiki locally