Difference between revisions of "Data/provenance browser"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
Add ideas/suggestions/goals here | ==Add ideas/suggestions/goals here== | ||
* We need a better mechanism that allows users to search/query for workflows and provenance, for example search by project, parameter names and values | * We need a better mechanism that allows users to search/query for workflows and provenance, for example search by project, parameter names and values | ||
* One way to view this is to allow the creation of mappings between the vistrails/projects into different structures---like "smart folders", e.g., /projectN/vt1/wf3/exec23/O1.... | * One way to view this is to allow the creation of mappings between the vistrails/projects into different structures---like "smart folders", e.g., /projectN/vt1/wf3/exec23/O1.... | ||
| Line 7: | Line 7: | ||
* Keep mappings from our datatypes to file structures | * Keep mappings from our datatypes to file structures | ||
* Need an exportable archive (to send with a paper, allow browsing outside of VisTrails) | * Need an exportable archive (to send with a paper, allow browsing outside of VisTrails) | ||
==Juliana's suggestions== | |||
As for the steps, here's what I suggest: | |||
# try and get multiple vistrails accessible through the browser | |||
# allow users to sort the information in different ways, based on the metadata stored in SQLLite. | |||
# support for (simple) queries over the actual provenance info (version tree, workflows and logs), e.g., we could support the layered queries we described in the First Provenance Challenge. | |||
# design and implement the map-to-directory functionality. | |||
As we implement these, we should make sure we have a clean API that can be used without a GUI. | |||
Revision as of 08:26, 10 December 2010
Add ideas/suggestions/goals here
- We need a better mechanism that allows users to search/query for workflows and provenance, for example search by project, parameter names and values
- One way to view this is to allow the creation of mappings between the vistrails/projects into different structures---like "smart folders", e.g., /projectN/vt1/wf3/exec23/O1....
- Support editing and synchronization in both ways (if edit smart folder, should update vt)
- Should be able to script the use of the browser, e.g., to test a new version of a workflow against a saved test suite
- Scientists like a directory structure and can go browse there like they browse files with finder/explorer
- Keep mappings from our datatypes to file structures
- Need an exportable archive (to send with a paper, allow browsing outside of VisTrails)
Juliana's suggestions
As for the steps, here's what I suggest:
- try and get multiple vistrails accessible through the browser
- allow users to sort the information in different ways, based on the metadata stored in SQLLite.
- support for (simple) queries over the actual provenance info (version tree, workflows and logs), e.g., we could support the layered queries we described in the First Provenance Challenge.
- design and implement the map-to-directory functionality.
As we implement these, we should make sure we have a clean API that can be used without a GUI.