Implement JSON based large scale dootronic tagging


Status message

You are not a member of this team. If you want to be part of this team, click on 'Subscribe to this team'.
General task

This task involves the implementation of two advanced features that will be available only for superhub users:

  1. Implementation of an interface to allow users to clone one dootronic at large scale. Currently we can only clone one dootronic at a time. This feature will allow to clone a given dootronic N times in just 1 click, where N can be arbitrarily large up to a limit.
  2. Implementation of another interface to allow users to upload a JSON file providing the set of specifications of an arbitrary number of dootronics. This feature allows to automate (removing manual intervention) the process of updating dootronics once they have been sanitized (change to status S2) and their specifications are know. The specifications of the JSON file are defined in this document:

This feature provides a very relevant capability to allow hubs that sanitize many dootronics in one shot (e.g., more than 100 laptops in one day) to efficiently manage their online dootronic updates without having to manually update each dootronic one at a time.


frankgeisler's picture
Submitted by frankgeisler on Mon, 04/01/2019 - 07:37

Regarding the second task I have an extended wish:
- the pre-cloned laptops from part one currently have status S2
- when the interface update is running, then the status continues to be S2 (so no e-mail notifications to the donors)

Wouldn't it be better if we mass clone with status S1 and then as part of the interface update also a status update to S2 is happening?

Maybe there are other options but we feel that a donor might be interested to see that his laptop donation has achieved S2 rather than waiting until we set the laptops manually to S3?

Cheers, Frank

jordi's picture
Submitted by jordi on Mon, 04/01/2019 - 07:45

Certainly, to do that all you have to do is clone from an initial laptop that has status S1, instead of S2. Then the cloning (step #1) will generate S1 laptops, and then the update (step #2) will change them all to S2 and generate emails out. (It's just going to take longer to do the updates to send out each email but it should work the same way.) Shall we test this during your next workshop?

frankgeisler's picture
Submitted by frankgeisler on Mon, 04/01/2019 - 08:26

This is a great idea Jordi and yes, we can test it during the next workshop in June.

Just wondering: We will have "new cloned" records with status S1 but also "old existing" records with status S2 - will the JSON file upload recognize and send/not send emails according to the previous status?