Bug #3668

Define contents of "Publication Ready Archive"

Added by ben leinfelder over 13 years ago. Updated about 13 years ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:


It's still unclear exactly what will be included (user specified?) and how it will be structured.
From past discussion these seem to be likely:
-Original Input Data
-Intermediate Data products
-Various workflow outputs (images, tables, graphs, charts)
-Final Data results
-Workflow file (MOML)
-Defining parameters for included execution[s]
-Report instance (XML and/or PDF?

Also, will the the "PRA" contain more than one execution? I believe that was indicated in meetings


#1 Updated by Derik Barseghian over 13 years ago

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.

#2 Updated by Derik Barseghian over 13 years ago

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

#3 Updated by Derik Barseghian about 13 years ago

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:

#4 Updated by Redmine Admin over 9 years ago

Original Bugzilla ID was 3668

Also available in: Atom PDF