| | 1 | == Use Cases for Client API and Bulk Operations == |
| | 2 | |
| | 3 | === Description === |
| | 4 | The two key use cases (from one of Nick's emails): |
| | 5 | |
| | 6 | 1) User submits data to caTissue such that participant(s) are created and assigned to the BRICCS collection protocol, primary samples received |
| | 7 | are logged, derived samples are recorded, and aliquots are created, and located, appropriately.[[BR]] |
| | 8 | 2) User submits an excel chart style array of aliquot barcodes and a box identifier, such that caTissue can update the location of the aliquots |
| | 9 | with reference to their container (the box) and their location within the box (the grid reference). |
| | 10 | |
| | 11 | === Implementation === |
| | 12 | Here is a fairly generic strategy: |
| | 13 | |
| | 14 | * Develop the use cases, in sufficient detail to be able to... |
| | 15 | * Translate use cases into actions using caTissue's domain objects |
| | 16 | * Analyse in terms of client API and / or bulk operations |
| | 17 | 1. For client API |
| | 18 | a. Decide the user interface |
| | 19 | a. Evaluate how to use the 2-d barcode reader |
| | 20 | 1. For bulk operations |
| | 21 | a. Design mapping file |
| | 22 | a. Design utility (or find a utility?) to export csv file from a spreadsheet |
| | 23 | * Code and Test |
| | 24 | |
| | 25 | |
