Report 22-02-18

To recap:

I'm accepted in the PaymentWorks system I can even use the email ([email protected]) I'd like to use there The Insurance requirement has been waived.

Thanks for simplifying this as much as possible!

How is the equipment order coming?

I'd also like to schedule a regular check in on the project - even if it's just email. If we could find another researcher in the same space with the time to weigh in on technical or accessibility issues, I'd appreciate it. Thomas would be great, but he's always too busy.

I'll archive that progress in the project Wiki, which I add to from time to time: https://github.com/jhhl/AUMI-Together/wiki

Speaking of which, there are a few things which I guess I could pay for and put on in invoice, like:

An AUMI Together Github account so the project won't need to st in my account, but rather, one for the project itself. This may require a new email address that's not a jhhl.net address, which I'd like to get on some non-google or other massive system. It could be through panix, the ancient provider I've been on for decades, or one from rpi.edu (which might be trouble if the project ever migrates from RPI, to, say, Concordia or KU).

I've also talked with my friend Bill Brovold, who has connections to a pool of potential AUMI users in NYC. I'd also like to see about finding more users I can work with and throw ideas at as the program develops though https://www.adaptivedesign.org

I'm thinking that once there's a good operating framework, making variant versions that concentrate on different capabilities would be good. For instance, a version that requires minimal physical engagement can be different rom a version that is geared more for the visually impaired. That would mean UI techniques can be streamlined instead of slowing down all possible versions.

The first part of the project is getting some segments of the program worked out and made into modules, and to get user interface standards of accessibility for different capabilities in place. Some of the trackers, the color and ML ones, may have some ways to be configured that require less interaction.

Some of these ideas may be patentable (RPI would own them, as part of their 'we own the work you do' clause of the contract), so finding any RPI patent research resources might be good to have. The same goes for the eventual privacy documents related to logging in for AUMI Together sessions. I'm hoping there can be a way to identify people for the period of the session that has nothing to do with real names or other information that can be traced back to people.

That's my report for now! -- Henry