Development - ToDo
Jump to navigation
Jump to search
2023 Dev ToDos
General
- come up with shell script (or something) that goes through and does pulls on all the repos
- alternatively pull the ext repos as well, but that might not be an always...
- update production links on scheduling, workflow and wiki to point at the right locations (not venom any more)
Engage
- sort out import functionality from workflow
Scheduling
- Sort out the multiple Instructional Summary Runs
- Sort out Location processing
- runSI - see about doing schedule query further down the subcommands
- look for comments in runSI.php -> siteScheduleSection
- improving support for Advanced Juniors, Camps, Clinics
- check in with Veronica/Randy/Shirley about what that should look like
- need to sort out division designations
- U13, U16 etc... vs 16 Under
- xfering latest datasets/settings etc...
- Add form to create samle data (from last updloaded or possibly other)
- Check for non-existent location to prevent map error
- this is for data Summer 2023-pass2
- clean up timestamp adds to schedule output
- need to verify that the new no-cache code is in all the files
- tool to clear old seasons from ftp server
- specify season from a pull down - loop over dir suffixes
- add time stamp to static site and tourn info sheets (like was done with PDFs)
- remove extra index file variations, currently there are three, and one is supporting ancient forms
Mobile
- Sort order on epoch for daily schedules
- cover cases where there are two events in one day (rare, but it happens)
- remove or fix tournament listings on main site page
- make sure that tournament matches are in the match listings
- allow scorekeeping of those
- scorekeeper
- allow name editing?
- fix instructions (no - now)
Auto Generated Report Data
- It would be nice to copy the lastauto* files to the local development page...
- Not critical, but nice for testing
- web methods can get the data, but we lose the mtime...
- fetch at resetIODirectory time...
- preserve the mtime some other way for those files...
- maybe the meta file???
- That would require that we update the meta file each time we receive an entry...
- How would this work with testing/development work on the script?
- scp -p from home
- via cron from home might work
- via make target
Also need to figure out how to decide whether we should be copying this stuff and where we copy the stuff from
2014-04 Dev thoughts
- Mobile Prep
- resetTables during reset IO dir
- detect empty tables in mobile site and offer appropriate message
- Scheduling Processing
- consider storing php serialized objects in db for working with
- Want a general facelift to scheduling site
- HTML5 (with html5 shim for older browsers)
- CSS3
- HTML based nav menu
- More modern login/logout setup
- PHP session cookies, remember me setup
- Start working towards getting all scheduling data configured in the db
- Could feed both mobile site and a joomla module
- Change upload to import
- Incorporate the email check into the Import page
- Maybe an ajax request in a section of the page
- Maybe figure out a better way to do general progress display, old way produces lots of output (in HTML comments)..
- This would also possibly allow a way to do more of a template setup
- Consider moving scheduling into a drupal site
- Takes care of some of the role stuff I would like to do
- Or at least playing with a dev
Scheduling v2 thoughts
Databases
- access db - persistent data shared by all usyvl systems
- access
- settings?
- dynamic - data that is re-generated each time scheduling is run
- clear tables on resetIOdir
- Input data
- team report data (™)
- event report data (ev)
- derived data
- match table
- Consider saving serialized php objects across scripts???
- Want to square away the event id (evid) stuff
- Currently home and away tournaments have different evids, we need to clean that up
- Possibly establish evids for home tourns and then match away tourns to those
- Currently home and away tournaments have different evids, we need to clean that up
- static db - persistent data for scheduling
- location table - need some sort of a timestamp for new or updated entries to allow geocoding
- distance table - figure out how to manage this table that will store google distance api data between all of the sites