hamstudy / examtools-docs Goto Github PK

From Janet: This is my first pass at how we run an in-person session using examtools. Any questions of anything I’ve left out would be appreciated.

https://docs.google.com/document/d/1ZoDxg3vcI37-ZUUQssoIAnxzmUfLl_Tk0Zf0rrnJoVE/edit

https://docs.exam.tools/docs/ve/veadditionalvec/ says "Fill out this form" but following that link leads to "And please inform the person who told you to go here so they can update their links!"

https://github.com/hamstudy/examtools-docs/edit/master/content//docs/cve/cveCreateSession.md

(which has links to exam.tools & ham.study throughout, NOT sandbox)

You may do this to proof-read it, experiment with formatting or share it with your VE team before it goes live using the private link.

(bolded for emphasis)

is contrary to "Please use the sandbox for all training, demonstrations, or experimentation -- that's what it is there for."

If experiments/experimentation may not be done on prod, do not say it may be done on prod.

Under Wrong Person admitted from the Waiting Room

You write that removing someone from the meeting room with remove moves them back to waiting room. My experience in the past, and again today, while testing this, removed the person from the meeting. In the picture above the highlighted remove option is "Put in Waiting Room" why not use this instead?

Update, I was not using waiting room, hence the meeting removal. But removals do put you onto a bad boy list. if you do not follow the instruction to allow rejoining, they will not be allowed back. I have found that Zoom software updates resets switches. Just one more thing to worry about. The most recent update also reset the cohost switch, and my ability to share full screen as the host.

Thanks for all your great work

Dave N4NG

It appears that exam.tools doesn't care to know what VEC a VE is accredited by as long as they were accredited when they initially submitted the tier2 form. The ARRL FAQ says to notify experienced support. For one of my VEs whose initial examtools VEC was GLAARG, we ended up not having to do anything to get them into my sessions. The CVE (ARRL VEC liason) does need to validate their VEs in the usual way (look at the ARRL VEC Session counts) as an indication of accreditation before adding them to a session.

I'll look at doing an update pull request for this but Alan wanted me to track it to not lose it... ;-)
Scott AG7T