Development - ToDo

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
• facilities export

Scheduling

Processing

• runTS.php - runTS - convert to db based loop instead of file based
  • have started process
• runSI - see about doing schedule query further down the subcommands
  • look for comments in runSI.php -> siteScheduleSection
• Sort out the multiple Instructional Summary Runs

Locations

• multiple (3) location processing steps
• runTI::loadProximityDistances
  • currently file based, need to convert to db based - I think I started the proximity stuff somewhere
• proximity
  • would be nice to have linear distance as well as drive time (minutes)

Support for Advanced Juniors and other oddities

• 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

Data Management

• xfering/exporting latest datasets/settings etc...
• 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
• tooltip over sample data entries with description
  • collapsible
• Sample Data Sets
  • Add form to create sample data (from last updloaded or possibly other)
  • Want to be able to save a copy of the most recent upload, rename it, and maybe even export the associated files (-ev.csv, -tm.csv, .meta) (tar? zip?), import it
• copy poolLayoutDb from tools to local dev (removed a row, I should not have).

HTML Pages/Schedules/HTML

• add time stamp to static site and tourn info sheets (like was done with PDFs)
  • possibly more detail, branch and hash?
• add the no-cache goodies to all pages in schedules
• setup an xfer to a secondary location on the main system
  • as opposed to an FTP xfer
  • simple copy by php to s.usyvl.org
• NetLabel PDFs
  • make watermark darker or maybe in color (usyvlFPDF.php:381)
  • add the netlabel pdf to the TI html pages
  • need to check handling of missing division
    • had an empty 7-8 division that created a blank page for the 7-8
    • had an overprint of the match grid for 7-8 and 9-10
    • example would be: 2023_C_Fall-ts/2023-10-28-Ventura-Goleta-Ojai.pdf
      • This was an unusual case since 10-14 match with Goleta/Ojai was OK, think maybe because of single 7-8 team moved into 9-10. So 7-8 pool was created, but not deleted after moving that one team to 9-10 pool
  • add branch to bottom page label

Web Services

• repoint schedules.usyvl.org at linode
• remove extra index file variations, currently there are three, and one is supporting ancient forms
  • explore options for altering colors: background, text etc... easily and modularly without having to have completely separate styles
• work on having dprint/print_pre - return vs print functionality be more consistent: ie: one is true for returning, the other false to return
  • look for other php examples of WHAT that return value should be

Mobile

• fix or remove links for tournaments/games/etc...
  • currently only daily schedules is correctly linked
• 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

• 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