| | 1 | == Design |
| | 2 | |
| | 3 | Triggering the creation of the checklist must be idempotent and account for Notes previously converted into Useful links. |
| | 4 | |
| | 5 | The user interface is the above ''Checklist creator'' field with its selectable options. |
| | 6 | |
| | 7 | The first four options indicate "Create/recreate ..." so we can safely overwrite any previous checklist Note of the same name. They are lengthy notes with lists of IUCLID6 dossier file numbers and their titles. |
| | 8 | |
| | 9 | * Help-text for the ''Checklist creator'' field can advise the user to change the Note title if the contents have been changed and need to be saved. |
| | 10 | |
| | 11 | The fifth and sixth options each scan their respective checklist note and create document management notes. |
| | 12 | |
| | 13 | Titles of those checklist notes are ... |
| | 14 | |
| | 15 | {{{ |
| | 16 | Assessment dossier checklist Required items |
| | 17 | Assessment dossier checklist If available items |
| | 18 | }}} |
| | 19 | |
| | 20 | For either checklist the top line of the note is the date the checklist was created. It is ignored here. |
| | 21 | |
| | 22 | For either checklist, if a line begins with an IUCLID6 number, that line plus " (Required)" or " (If available)" as appropriate becomes the title for the document management note. |
| | 23 | |
| | 24 | All text below that line and above the next IUCLID6 number is added to the top of that document management note. |
| | 25 | |
| | 26 | However, unlike the checklist notes themselves, document management notes must not be overwritten. Hence, if they already exist the software passes on that title. |
| | 27 | |
| | 28 | Furthermore, if any such ''Note'' has been converted to a ''Useful link'' - indicating action is complete - the software must also pass and avoid recreating a newer version of the same Note. |
| | 29 | |
