Feature request: save log button?

[kieranjol]

Would it be possible to add a 'Save Log' button at the end of a job, for example bag validation and bag creation?
I'm aware of the log file but it could be useful to allow a user to save the outcome of the job, even if it's just the Job/ProcessID/Started At/Validation/outcome etc.

[diamondap]

This feature is already in the pipeline for DART 3, in which I plan to automatically save artifacts for each job. Artifacts include:

1. A summary of the outcome of the job's bagging, validation and upload steps.
2. The bag's tag files.
3. The bag's payload manifests.

I've gotten various requests for all of these over the years, so it seems to be a pretty common need. DART 3's improved storage layer makes these features much easier to implement. These artifacts will be searchable and discoverable through the UI.

[kieranjol]

This is brilliant, I'll leave this open so.

[diamondap]

Update: This feature won't make it into the existing DART, but it is now fully implemented in DART 3, which still has a ways to go before release. Here's what the jobs list looks like in DART3. You'll notice an Artifacts link for each job.

If you click that, you'll see artifacts from each time this job was run listed in the left nav. Artifacts include manifests, tag files, and a JSON file describing what happened when the job ran. Click any file to view its contents. This shows the md5 manifest from the last run.

[kieranjol]

This is wonderful! I’m teaching a class on file transfer and fixity in University College Dublin on Thursday and I’ll show off these screenshots :)
Will there be a “save as” type button where these artefacts can be saved in a file that an archivist could store as evidence that the workflow and validation was carried out?

[diamondap]

Yes. At the bottom of the artifact page is a Copy to Clipboard button so you can copy the file contents into a text file or wherever else you want. It was cut off in the other screenshot, but you can see it here.