This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
devel:feature_list [2013/07/25 10:31] – [Use single dataset(s) as input for processing (for example CP pipeline)] epujadas | devel:feature_list [2013/07/25 11:45] – epujadas | ||
---|---|---|---|
Line 2: | Line 2: | ||
===== Use existing storage datasets as input for processing ===== | ===== Use existing storage datasets as input for processing ===== | ||
- | See: [[devel: | + | See: \\ [[devel: |
==== Concept ==== | ==== Concept ==== | ||
Line 17: | Line 17: | ||
===== Use single dataset(s) as input for processing (for example CP pipeline) ===== | ===== Use single dataset(s) as input for processing (for example CP pipeline) ===== | ||
- | See: [[devel: | + | See: \\ [[devel: |
This is specifically a request for the user interface. When starting a specific workflow | This is specifically a request for the user interface. When starting a specific workflow | ||
Line 206: | Line 205: | ||
===== Avoid Database duplication ===== | ===== Avoid Database duplication ===== | ||
- | See: Combining Processing Information with Storage Information | + | See: [[devel: |
Many properties of datasets can and should be annotated with the datasets in the | Many properties of datasets can and should be annotated with the datasets in the | ||
Line 220: | Line 219: | ||
===== Easy data maintenance: | ===== Easy data maintenance: | ||
- | |||
- | See: Split into User Interface and Backend Daemon | ||
This is given by tight integration with the storage. Data maintenance is easy on the | This is given by tight integration with the storage. Data maintenance is easy on the |