| | 46 | == Data Model == |
| | 47 | |
| | 48 | ''under construction...'' |
| | 49 | |
| | 50 | == Functionality needed == |
| | 51 | |
| | 52 | === CRUD === |
| | 53 | |
| | 54 | Generic CRUD is a matter of course, specialities below: |
| | 55 | |
| | 56 | === Labels === |
| | 57 | |
| | 58 | During rescue/recovery operations mostly tags are used to identify affected persons. Different types of tags are in use: barcode tags are common, but even RFID tags could be used (which contain more details on the person). |
| | 59 | |
| | 60 | The Person Registry should support (at least) barcode labels: |
| | 61 | |
| | 62 | * read labels from tags or documents (realized by the client system) |
| | 63 | * retrieve/display the corresponding record from the database |
| | 64 | * display links to process this record in other person-data-related modules |
| | 65 | * display/print out barcode labels for existing records (e.g. to forms, documents, stickers) |
| | 66 | * generate/manage new unique labels (and print them out), even pre-printed stock tags |
| | 67 | |
