Input Map Fulfillement

input specs and input maps

This document is intended for developers with some knowledge of compspecs, inputspecs and how they relate to running a computation.

• Each computation consumes a fulfilled input map.
• Input maps are saved to the database in a potentially unfulfilled state.
• Fields with a source of "owner" are already in their fulfilled state and don't need to be modified after saving to the database.
• Fields with a source of "member" must be fulfilled by the user at the mapping stage. When a pipeline is saved, fields with a source of "member" are saved to the database in an intermediary state.

At the mapping stage, "member" fields are fulfilled and the resulting input map is saved to local storage. The input maps in local storage are what will be used to run the pipeline on each member's machine.