Leaving early to participate in CLSA.
The Songhees conference site is now live on the production server. Pat did all of the layout, presentation and graphics work.
I did the registration form, back-end database and php to communicate between the two. The form has a javascript function to check data before submission to a "confirm.php" page, which shows the user what they're about to send to the DB. When user confirms, data is sent to DB by process.php page and user gets message saying "Click to go on to Payment".
Payment is being handled by UVic library, so the receipt the user gets when they pay says "UVIC LIBR CONFERENCE". I added a line to the message on the process.php page telling user what to expect.
Leaving early.
With advice from GB at Oxygen, figured out how to increase the stack for Jing to do validation, so that's all now working; also figured out how to suppress messages from repeated ant target calls to do that validation, so the output is less cluttered. Confirmed that all validation in the build is now working. Tweaked the Python script so it knows about the taxonomies and personography files.
Then started on meta-diagnostics. I have it now generating a graph showing the progress on all four of the metrics we have right now, by date. I've also started on building a projection object which will tell us whether we're actually going to finish in time or not; lots more to do on that.
In Genealogy--> children
the full stop appears before the children's names are fully sorted alphabetically.
making blog post for greg
following link produces an error
http://mythsdev.uvic.ca/exist/apps/myths/modules/detail.xqm?id=AIGA1
making blog post for greg
Completed the build target which creates the diagnostics for the current day, and then adds, commits and pushes the result to GitHub. As soon as we have meaningful multi-day diagnostics in the repo, I'll be able to move on to the meta-diagnostics, and we'll start to see our progress.
Also created docs/about.md, which is the beginning of a proper piece of documentation for the programmer side of the project.
Did three more and started the fourth; waiting on the answer to a question from the prog committee on that one.