Closed FedorSteeman closed 2 years ago
Go-back button: There could be 'state' (tilstand) represented as a python dictionary (key-value pair structure/array) because the field names are unique and they can double as keys, while the input from each field can populate the 'value' in the dictionary. When a specimen is saved, the data saved could come from the dictionary (that is one option) and if there is an error, the operator can press Go-back and the form would be populated with the content of the last dictionary.
Workflow: For every digitization session, initiate a dictionary. For each submit action in the session: Save the dictionary and initialize a new one. This would yield a perfect history for that session. At the end of the session - in stead of ditching the dicts - they could be saved as log.
@PipBrewer To specify here exactly which fields are to be sticky.
Go back button split out into ticket #137
Checkbox 'Upon save: Clear non-sticky fields and indicate specimen has been saved' is basically done. Functionality is in place, but I need a final authoritative list of non-sticky elements.
@jlegind Just go ahead with educated guesses. We can adjust when Pip gets back.
Pretty much everything but barcode to be sticky unless part of log in
From: Fedor Alexander Steeman @.***> Sent: 05 September 2022 17:23:18 To: NHMDenmark/DaSSCo Cc: Pip Brewer; Mention Subject: Re: [NHMDenmark/DaSSCo] Optimize Data Entry UX (Issue #95)
@jlegindhttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjlegind&data=05%7C01%7Cpip.brewer%40snm.ku.dk%7C2cbd27c0324440a379ad08da8f52909c%7Ca3927f91cda14696af898c9f1ceffa91%7C0%7C0%7C637979882087809784%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=qStkknjn1FNKNAawiPNIuEeNiL%2Bon3%2BR5gugaSKTunc%3D&reserved=0 Just go ahead with educated guesses. We can adjust when Pip gets back.
— Reply to this email directly, view it on GitHubhttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FNHMDenmark%2FDaSSCo%2Fissues%2F95%23issuecomment-1237202100&data=05%7C01%7Cpip.brewer%40snm.ku.dk%7C2cbd27c0324440a379ad08da8f52909c%7Ca3927f91cda14696af898c9f1ceffa91%7C0%7C0%7C637979882087809784%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=JzvD4g5o5M%2B3RL1URkarzXdDMYOk4Z3g6D0HpHg7UE4%3D&reserved=0, or unsubscribehttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAWTTEXDFSGLQCL2SKEI77C3V4YF6NANCNFSM57O2OURQ&data=05%7C01%7Cpip.brewer%40snm.ku.dk%7C2cbd27c0324440a379ad08da8f52909c%7Ca3927f91cda14696af898c9f1ceffa91%7C0%7C0%7C637979882087966015%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=mvZF618%2FWfNaRRBnSubi5lFqTEl8jOQEhcN6Bupa6Gs%3D&reserved=0. You are receiving this because you were mentioned.Message ID: @.***>
The 'barcode' item has a dependency, and that is the driver for the barcode scanner. Driver for DataLogic Quickscan model 2430: DR9100399.zip
Remaining or new bugs moved to #153
Issue
Speed up the digitizing process by streamlining the UI.
Bugs (moved to #153):