This item is deleted.
Syntax highlighting of a26cb65 ~( ArchivedProducts)
Discussion and ideas to archive products done with a previous version of a pipeline and allow to create new versions. == Design == === Archived products accessibility === Archived products are to be explicitly accessed (productid+prodtype). There is no need to modify/have a map interface dedicated to them (which works with observations anyway, not products), and probably no need in the workspace too? === Dependencies === MarsSI products have a dependency fields since the major DB rewrite. What about an archived products dependencies? We cannot archive deps at the same time, they might be still up-to-date. Forget deps as they are used foremost for procesing logic? What about an archived product that is a dependancy? It should trigger a archival of the other products too. But their own pipeline version do not change... Use mctime? == Implementation == === Data === Files are to be moved to /data/archive/$TARGET/$INSTHOSTID/$INSTID/$VERSION (ex /data/archive/MARS/MRO/CTX/CTX_008716_1998_008782_1999/V1) === Database === Create an ArchivedProduct model === Web === Provide a set of search/display interface that allow for copy operations.