Summary:
It would be highly useful to have the ability to add metadata to a bilag in the bilagspulje.
Current Behavior:
Currently, the pulje interface displays the selected kladdelinje in the bottom-right corner, but this selection is not tied to the scanned file. The only persistent data associated with a bilag is the PDF file itself. As a workaround, metadata like amount, date, and description is often stored in the filename, which is not ideal for usability or automation.
Suggested Improvement:
Enable structured metadata storage for bilag in the bilagspulje, potentially by using the existing documents table to store fields such as:
- Total bilag amount
- Description
- Date
This would allow metadata to follow the file throughout the workflow and improve data integrity.
References:
- A implementation that supports date and description inputs in the upload interface but stores them in the filename can be seen here c84d608
- There is a reference to a .spec file in /includes/docIncludes/ that touches on metadata handling, but it is not a complete solution and is not fully integrated into the bilagspulje workflow.
Use Case:
In many cases, the person scanning bilag is not the same person doing the accounting. Scanning is often performed by lower-cost labor, while an accountant reviews and processes the entries. If the scanner could input metadata such as date, description, and amount during upload, it would streamline the workflow, save time, and reduce the need for redundant data entry by the accountant.
Summary:
It would be highly useful to have the ability to add metadata to a bilag in the bilagspulje.
Current Behavior:
Currently, the pulje interface displays the selected kladdelinje in the bottom-right corner, but this selection is not tied to the scanned file. The only persistent data associated with a bilag is the PDF file itself. As a workaround, metadata like amount, date, and description is often stored in the filename, which is not ideal for usability or automation.
Suggested Improvement:
Enable structured metadata storage for bilag in the bilagspulje, potentially by using the existing documents table to store fields such as:
This would allow metadata to follow the file throughout the workflow and improve data integrity.
References:
Use Case:
In many cases, the person scanning bilag is not the same person doing the accounting. Scanning is often performed by lower-cost labor, while an accountant reviews and processes the entries. If the scanner could input metadata such as date, description, and amount during upload, it would streamline the workflow, save time, and reduce the need for redundant data entry by the accountant.