Kepler

Yes the reap usecase isn't specific, it requests "an archive that contains the Kepler workflow, all required inputs (data sources like database tables are included), and all produced output."

All the things you mention do seem likely.

If they don't fall in the 'workflow outputs' category, determining what are 'Intermediate Data products' and 'Final results' seems difficult without user help.

In the past we've discussed the PRA being a kar file. It must provide enough metadata to be useful in the repository (description, search), to a user that downloads it, and to a publication. I imagine Kepler should be able to open it (the wf contained within) as well.

It's been discussed that a PRA could be either contain (all of the described from) a set of runs, or just one.

Filing under Provenance as requested in last reporting/provenance meeting.

In a recent meeting with Matt and Ben, we discussed a proposal for a redefinition of KAR that would be able to contain, among other things, everything needed for a publication ready archive. I've posted the proposal here: https://kepler-project.org/developers/teams/framework/proposed-changes-to-kar

Original Bugzilla ID was 3668