2562 describes an approach to implement per-file parsing logs, stored alongside the submission in s3. #3294 implements this approach, but does not associate the resulting log file to the submission in the Django Admin Console. This would provide easier access to the log file for end-users.
Following the design outlined in #2562, associate the log file to the datafile submission by
Modifying ReparseMeta and ReparseFileMeta to be ParseMeta and ParseFileMeta, creating meta models for every run of the parser (not just reparse), and save the s3 url to the ParseFileMeta model; OR
Create a new model to hold the s3 url, with its own ForeignKey to DataFile
Acceptance Criteria:Create a list of functional outcomes that must be achieved to complete this issue
[ ] Parsing log files are associated with a datafile submission and can be downloaded in the Django Admin Console
[ ] Testing Checklist has been run and all tests pass
[ ] README is updated, if necessary
Tasks:Create a list of granular, specific work items that must be completed to deliver the desired outcomes of this issue
[ ] Implement the log file association (Method/Design step 6 of the tech memo)
[ ] Run Testing Checklist and confirm all tests pass
Notes:Add additional useful information, such as related issues and functionality that isn't covered by this specific issue, and other considerations that will be helpful for anyone reading this
Need to decide on the approach
Supporting Documentation:Please include any relevant log snippets/files/screen shots
Doc 1
Doc 2
Open Questions:Please include any questions or decisions that must be made before beginning work or to confidently call this issue complete
Description:
2562 describes an approach to implement per-file parsing logs, stored alongside the submission in s3. #3294 implements this approach, but does not associate the resulting log file to the submission in the Django Admin Console. This would provide easier access to the log file for end-users.
Following the design outlined in #2562, associate the log file to the datafile submission by
ReparseMetaandReparseFileMetato beParseMetaandParseFileMeta, creating meta models for every run of the parser (not just reparse), and save the s3 url to theParseFileMetamodel; ORForeignKeytoDataFileAcceptance Criteria: Create a list of functional outcomes that must be achieved to complete this issue
Tasks: Create a list of granular, specific work items that must be completed to deliver the desired outcomes of this issue
Notes: Add additional useful information, such as related issues and functionality that isn't covered by this specific issue, and other considerations that will be helpful for anyone reading this
Supporting Documentation: Please include any relevant log snippets/files/screen shots
Open Questions: Please include any questions or decisions that must be made before beginning work or to confidently call this issue complete