View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0009661 | Taler | exchange | public | 2025-03-26 13:24 | 2025-04-22 23:20 |
| Reporter | Florian Dold | Assigned To | Christian Grothoff | ||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | resolved | Resolution | fixed | ||
| Target Version | 1.0 | Fixed in Version | 1.0 | ||
| Summary | 0009661: consider storing metadata about attribute collections | ||||
| Description | That way the UI can properly show the "index" of the AML file without having to fetch *all* attributes including large files. Candidates for meta-data are: * Form ID and version * Who submitted the form (AMLO vs customer) | ||||
| Tags | compliance | ||||
|
|
I thought this was already done? Please check, and if so, resolve! |
|
|
on kyc upload we are storing: TalerFormAttributes.FORM_ID and TalerFormAttributes.FORM_VERSION on aml decision we are storing: TalerFormAttributes.FORM_ID and TalerFormAttributes.FORM_VERSION I thought we already established that if the form was completed by kyc it means that it was completed by the customer and aml it means by the officer. Do we need more information? |
|
|
I think we may have both mis-read the bug: I think Florian wants the *exchange* database to store the form_id in a separate column so we can select it or select by it. Correct? |
|
|
Exactly. I'm not quite sure this is a 1.0 bug, but I imagine that "show the latest filled out form $X" could be a common action in the AML SPA. |
|
|
Well, extracting the form ID into a PG-column _later_ is tricky, as we encrypt the attributes inside the DB. So I guess that justifies 1.0, but makes it *my* issue (to at least change the DB schema). |
|
|
Columns added in d160847fc..d9a2f5aa6 (only form_name and submitter type; form_version makes little sense IMO -- if you're looking for say a vqf-902.11, you unlikely care if it is 2022 or 2023-edition.d160847fc..d9a2f5aa6 |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-03-26 13:24 | Florian Dold | New Issue | |
| 2025-03-26 13:24 | Florian Dold | Status | new => assigned |
| 2025-03-26 13:24 | Florian Dold | Assigned To | => Christian Grothoff |
| 2025-03-26 13:25 | Florian Dold | Summary | consider storing (indexed) metadata about attribute collections => consider storing metadata about attribute collections |
| 2025-03-28 06:50 | Christian Grothoff | Assigned To | Christian Grothoff => |
| 2025-03-28 06:50 | Christian Grothoff | Status | assigned => confirmed |
| 2025-04-17 22:32 | Christian Grothoff | Tag Attached: compliance | |
| 2025-04-17 22:32 | Christian Grothoff | Assigned To | => sebasjm |
| 2025-04-17 22:32 | Christian Grothoff | Status | confirmed => assigned |
| 2025-04-17 22:33 | Christian Grothoff | Note Added: 0024598 | |
| 2025-04-17 22:33 | Christian Grothoff | Target Version | 1.1 => 1.0 |
| 2025-04-21 12:48 | sebasjm | Note Added: 0024626 | |
| 2025-04-21 12:48 | sebasjm | Assigned To | sebasjm => Florian Dold |
| 2025-04-21 12:48 | sebasjm | Status | assigned => feedback |
| 2025-04-21 13:27 | Christian Grothoff | Note Added: 0024627 | |
| 2025-04-22 11:52 | Florian Dold | Note Added: 0024645 | |
| 2025-04-22 12:56 | Christian Grothoff | Note Added: 0024646 | |
| 2025-04-22 12:56 | Christian Grothoff | Assigned To | Florian Dold => Christian Grothoff |
| 2025-04-22 12:57 | Christian Grothoff | Status | feedback => assigned |
| 2025-04-22 13:24 | Florian Dold | Note Edited: 0024645 | |
| 2025-04-22 23:20 | Christian Grothoff | Status | assigned => resolved |
| 2025-04-22 23:20 | Christian Grothoff | Resolution | open => fixed |
| 2025-04-22 23:20 | Christian Grothoff | Fixed in Version | => 1.0 |
| 2025-04-22 23:20 | Christian Grothoff | Note Added: 0024652 |
