Methods and systems for mitigating the effects of intermittent network connectivity in educational settings

• US 10,741,091 B2
• Filed: 02/03/2017
• Issued: 08/11/2020
• Est. Priority Date: 02/05/2016
• Status: Active Grant

• Current Assignee: ThinkCERCA.com, Inc.
• Original Assignee: ThinkCERCA.com, Inc.
• Inventors: Tolman, Joshua, Busser, Jerry
• Primary Examiner(s): Rahman, Sm A
• Assistant Examiner(s): Siddiqi, Emad
• Application Number:
  US15/424,562
• Publication Number:
  US 20170230479A1
• Time in Patent Office: 1,285 Days
• Field of Search: 709203
• CPC Class Codes: G06F 3/04847 Interaction techniques to control parameter settings, e.g. interaction with sliders or dials
• CPC Class Codes: G06F 40/169 Annotation, e.g. comment data or footnotes
• CPC Class Codes: G09B 5/02 with visual presentation of the material to be studied, e.g. using film strip
• CPC Class Codes: G09B 5/06 with both visual and audible presentation of the material to be studied
• CPC Class Codes: G09B 5/08 providing for individual presentation of information to a plurality of student stations
• CPC Class Codes: G09B 7/02 of the type wherein the student is expected to construct an answer to the question which is presented or wherein the machine gives an answer to the question presented by a student
• CPC Class Codes: G09B 7/06 of the multiple-choice answer-type, i.e. where a given question is provided with a series of answers and a choice has to be made from the answers
• CPC Class Codes: G09B 7/08 characterised by modifying the teaching programme in response to a wrong answer, e.g. repeating the question, supplying further information
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context

Abstract

Disclosed herein are methods and systems for mitigating the effects of intermittent network connectivity in educational settings. A student assignment is presented via a client-side user interface of an educational platform. The client-side user interface is initially operated in a read/write mode. Student input is received via the client-side user interface in connection with the student assignment, and is responsively locally stored. A remote-save-triggering event is detected, and a remote-save method is responsively executed. The remote-save method attempts to save the locally stored student input to a remote server. If the remote-save method returns a remote-save-success promise, the client-side user interface is continued to be operated in the read/write mode. If the remote-save method returns a remote-save-failure promise, the client-side user interface is transitioned to being operated in a read-only mode.

Claims

1. A method comprising:

presenting a student assignment on a client-side user interface of an educational platform via execution of a codebase on a client-side computing device by presenting, in a view, data from a studentAssignment model provided by the codebase, the studentAssignment model comprising a plurality of studentResponse models corresponding to respective assessable tasks associated with the presented student assignment;

initially operating the client-side user interface in a read/write mode;

receiving user input associated with an argument-building-block studentResponse model from the plurality of studentResponse models, the argument-building-block studentResponse model having a status parameter and a responseData element for storing data associated with a set of argument-building-block elements, the data including at least (i) an ordering of the argument-building-block elements, and (ii) text content of the argument-building-block elements received via a corresponding set of argument input fields;

responsive to receiving the user input associated with the argument-building-block studentResponse model, changing the status parameter from a clean state to a dirty state;

detecting a remote-save-triggering event, and responsively executing a remote-save method that attempts to save the received user input to a remote server, wherein the remote-save method returns either a remote-save-success promise or a remote-save-failure promise;

continuing to operate the client-side user interface in the read/write mode and changing the status parameter from the dirty state to the clean state if the remote-save method returns a remote-save-success promise; and

transitioning to operating the client-side user interface in a read-only mode if the remote-save method returns a remote-save-failure promise.

2. The method of claim 1, wherein presenting the student assignment via the client-side user interface comprises presenting the student assignment via a web browser that is executing on a client-side computing device, the method further comprising locally storing the received user input in a memory of the client-side computing device.

3. The method of claim 1, wherein the remote-save-triggering event comprises an expiration of a remote-save-triggering timer.

4. The method of claim 1, wherein detecting the remote-save-triggering event comprises detecting the remote-save-triggering event via the client-side user interface.

5. The method of claim 1, further comprising:

downloading the codebase to the client-side computing device from the remote server, wherein;

the codebase has a model-view-controller (MVC) architecture;

the codebase defines the studentAssignment model that corresponds with the presented student assignment; and

executing the remote-save method comprises the studentAssignment model executing the remote-save method.

6. The method of claim 5, wherein receiving the user input comprises a studentResponse model of the plurality of studentResponse models receiving the user input.

7. The method of claim 5, wherein each studentResponse model of the plurality of studentResponse models includes a respective studentResponse-model-specific remote-save method, each of which returns either a studentResponse-model-specific remote-save-success promise or a studentResponse-model-specific remote-save-failure promise.

8. The method of claim 7, wherein the studentAssignment model executing the remote-save method comprises the studentAssignment model:

instructing each studentResponse model of the plurality of studentResponse models to execute its respective studentResponse-model-specific remote-save method;

returning a remote-save-success promise from the remote-save method if every such studentResponse-model-specific remote-save method returns a studentResponse-model-specific remote-save-success promise; and

returning a remote-save-failure promise from the remote-save method if at least one such studentResponse-model-specific remote-save method returns a studentResponse-model-specific remote-save-failure promise.

9. The method of claim 8, wherein a given studentResponse model executing its respective studentResponse-model-specific remote-save method comprises the given child studentResponse model:

determining whether a status parameter of the given studentResponse model is in a clean state or a dirty state, wherein the dirty state corresponds to the given child studentResponse model containing updated user input with respect to a previous execution of the remote-save method, wherein the clean state corresponds to the given child studentResponse model not containing such updated user input;

returning a studentResponse-model-specific remote-save-success promise from its respective studentResponse-model-specific remote-save method if the status parameter is in the clean state; and

executing an attempt protocol to attempt to save the updated user input to the remote server if the status parameter is in the dirty state, and returning a studentResponse-model-specific remote-save-success promise from its respective studentResponse-model-specific remote-save method if the attempt protocol results in successfully saving the updated student user input to the remote server, and instead returning a studentResponse-model-specific remote-save-failure promise from its respective studentResponse-model-specific remote-save method if the attempt protocol does not result in successfully saving the updated user input to the remote server.

10. The method of claim 9, wherein the status parameter of the given studentResponse model is initially set to the clean state, the method further comprising:

changing the status parameter of the given studentResponse model from the clean state to the dirty state responsive to receiving the user input via the client-side user interface.

11. The method of claim 10, further comprising:

resetting the status parameter of the given studentResponse model to the clean state in connection with returning a studentResponse-model-specific remote-save-success promise from the respective studentResponse-model-specific remote-save method of the given child studentResponse model.

12. The method of claim 9, wherein executing the attempt protocol comprises making multiple attempts to save the updated user input to the remote server.

13. The method of claim 5, wherein the studentAssignment model executing the remote-save method comprises the studentAssignment model:

determining that a subset of the studentResponse models of the plurality of studentResponse models contain updated user input with respect to a previous execution of the remote-save method;

instructing each studentResponse model in the subset to execute its respective studentResponse-model-specific remote-save method;

returning a remote-save-success promise from the remote-save method if every such studentResponse-model-specific remote-save method returns a studentResponse-model-specific remote-save-success promise; and

returning a remote-save-failure promise from the remote-save method if at least one such studentResponse-model-specific remote-save method returns a studentResponse-model-specific remote-save-failure promise.

14. The method of claim 13, wherein determining whether a given studentResponse model of the plurality of studentResponse models contains updated user input with respect to a previous execution of the remote-save method comprises determining whether a status parameter of the given studentResponse model is in a clean state or a dirty state, wherein the dirty state corresponds to the given studentResponse model containing updated user input with respect to a previous execution of the remote-save method, wherein the clean state corresponds to the given studentResponse model not containing such updated user input.

15. The method of claim 14, wherein a given studentResponse model executing its respective studentResponse-model-specific remote-save method comprises the given studentResponse model:

executing an attempt protocol to attempt to save the updated user input to the remote server;

returning a studentResponse-model-specific remote-save-success promise from its respective studentResponse-model-specific remote-save method if the attempt protocol results in successfully saving the updated user input to the remote server; and

returning a studentResponse-model-specific remote-save-failure promise from its respective studentResponse-model-specific remote-save method if the attempt protocol does not result in successfully saving the updated user input to the remote server.

16. The method of claim 15, wherein the status parameter of the given studentResponse model is initially set to the clean state, the method further comprising:

changing the status parameter of the given studentResponse model from the clean state to the dirty state responsive to receiving the user input via the client-side user interface; and

resetting the status parameter of the given studentResponse model to the clean state in connection with returning a studentResponse-model-specific remote-save-success promise from the respective studentResponse-model-specific remote-save method of the given studentResponse model.

17. The method of claim 1, wherein the remote-save method includes a retry protocol.

18. A client-side computing device comprising:

a client-device communication interface;

a client-device user interface;

a client-device processor; and

client-device data storage containing client-device instructions executable by the client-device processor for causing the client-side computing device to carry out a set of functions, wherein the set of functions includes;

presenting a student assignment on a client-side user interface of an educational platform via the client-device user interface by presenting, in a view, data from a studentAssignment model provided by a codebase, the studentAssignment model comprising a plurality of studentResponse models corresponding to respective assessable tasks associated with the presented student assignment;

wherein the client-side user interface is operable in a number of different modes including a read/write mode and a read-only mode;

initially operating the client-side user interface in the read/write mode;

receiving user input via the client device user interface, the user input associated with an argument-building-block studentResponse model from the plurality of studentResponse models, the argument-building-block studentResponse model having a status parameter and a responseData element for storing data associated with a set of argument-building-block elements, the data including at least (i) an ordering of the argument-building-block elements, and (ii) text content of the argument-building-block elements received via a corresponding set of argument input fields;

responsive to receiving the user input associated with the argument-building-block studentResponse model, changing the status parameter from a clean state to a dirty state;

detecting a remote-save-triggering event, and responsively executing a remote-save method that attempts, via the client-device communication interface, to save the received user input to a remote server, wherein the remote-save method returns either a remote-save-success promise or a remote-save-failure promise;

continuing to operate the client-side user interface in the read/write mode mode and changing the status parameter from the dirty state to the clean state if the remote-save method returns a remote-save-success promise; and

transitioning to operating the client-side user interface in a read-only mode if the remote-save method returns a remote-save-failure promise.