Improved checkpointing

[jhmartin]

When transcribing a long set of paper-based records, it can be easy to lose track of where one has left off. It would be helpful if the form assisted in keeping track. Such as:

• When posting to the outbox, copy the most recently supplied entry in to a readonly field indicating it was the end of the prior batch.
• When posting to the outbox, increment the Message # field and copy the old value into a read-only fiield.

These can take the place of / supplement notations made on the source paperwork. Between the paper and alt-tabbing into Winlink to review this can be replicated, but less clicking/scrolling at 2am the better,

[nojronatron]

I will take a look at this and have something to try by July 22nd.

[nojronatron]

@jhmartin Take a look at this deploy preview for the UI and this PR for the code. Let me know what you think.

• Due to inability to access server-side (Winlink Express) code, all client-side functionality is limited when it comes to persisting data. I stuck with Browser APIs (local storage and save/load file data) to meet the request.
• User can increment Message Number using an on-screen button, in addition to entering a value manually.
• If user keep browser open between form SUBMITs, the last-entered bib data will be displayed in a new UI element "End Of Prior Batch".
• Save Race data and Load Race data buttons support Message Number and "End Of Prior Batch" data storage and retrieval.
• Updated README to include emphasis on using Save/Load Race data buttons, and keeping a single browser tab open to enable the most recent entry retention feature.

[nojronatron]

In the deploy preview you can go through the motions of entering all data, and at the end click the SUBMIT button and OK the message but don't close the tab.

Instead:

1. Paste-in the deploy preview URL into the address bar and press Enter.
2. Observe data that appears in the End of Prior Batch field.
3. Use the Tab key to cycle through the fields - it starts at the top so the user has the opportunity to click the increment button (or directly type) to overwrite the Message Number field.

Netlify does not have a server-side component that captures the sent data so an error message is displayed. This is expected.

Note: Save Race data and Load Race data behave the same as they would if you were using this form launched from Winlink Express.

[bytescream]

You should always save the form before sending it in. There are a some really basic reasons for this, but secondarily, if you did have to shut off your browser, or lost the local data for some similar reason, you should ba able to load up the most recently sent/saved copy of the form and pick up where you left off. I have not tested this, but we should test that this desired functionality works with loading up saved form data from the last submit.

I hope I am not assuming too much, and this comment is slightly valid. I'm kinda busy, but I don't want Jon feeling like nobody cares, like he's in a vacuum. It's a great tool.

On Thu, Jul 20, 2023 at 10:46 AM Jon Rumsey @.***> wrote:

In the deploy preview https://deploy-preview-41--enchanting-pony-09ae40.netlify.app/bigfoot-bib-report-initial you can go through the motions of entering all data, and at the end click the SUBMIT button and OK the message but don't close the tab.

Instead:

1. Paste-in the deploy preview URL into the address bar and press Enter.
2. Observe data that appears in the End of Prior Batch field.
3. Use the Tab key to cycle through the fields - it starts at the top so the user has the opportunity to click the increment button (or directly type) to overwrite the Message Number field.

Netlify does not have a server-side component that captures the sent data so an error message is displayed. This is expected.

Note: Save Race data and Load Race data behave the same as they would if you were using this form launched from Winlink Express.

— Reply to this email directly, view it on GitHub https://github.com/nojronatron/Bigfoot-Bib-Report-WL-Form/issues/40#issuecomment-1644340397, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAZUJIWY42IXPIOEO56JF2TXRFVF3ANCNFSM6AAAAAA2IHVAQQ . You are receiving this because you are subscribed to this thread.Message ID: @.*** com>

--

---

Mark Weisenfeld K7TUM CN87na http://www.levinecentral.com/ham/grid_square.php?Grid=CN87na (SW corner)

---

[nojronatron]

@bytescream Thanks Mark. We're is good alignment concerning usage of the Save/Load Race data buttons. Hopefully these links will save you some time researching what was done:

• Check out the backing branch changed files for code improvements.
• Check out the added emphasis to using the Save Race data button in section Form Usage in Winlink Express in the Readme.

:smiley:

[nojronatron]

Closing with merge-in of PR #41