Summary
In this mockup, I started to think more about the whole UI flow, including:
- Logging in
- Setting up Fedora Repositories
- Setting up DuraCloud Spaces
- Listing the content of each and creating "Copy" jobs
- Listing Running/Scheduled/Completed jobs
Download
Bill Branan:
- I expected the creation of jobs to occur in the Jobs tab, and not in the Repositories/Spaces tabs. Would be nice to see an "Add" tab in there along with the others that list the jobs. In that dialog you'd be able to select the repo/space involved, then define the criteria.
- May make sense to bring the creation of "criteria"/"selection sets" up a level, on it's own tab. So people can create these, give them names, and use them in various jobs. (Chris: Had similar thought...esp. regarding re-use)
Dan Davis:
- I tend to think the normal case is to have the "list" functionality report on diffs between storage locations, and a job is the specification of the differences to resolve.
- It would be useful to be able to say "Copy all except the selected objects" too
- For sync use cases, would be useful to have delete option (Bill and Chris agreed)
Chris Wilper:
- Maybe "Jobs" tab should be leftmost (default) then, if that's where most work would be done.
- Clarification: All jobs are scheduled. Some are repeatable.
- RE: Sync and deletes: Thought so far has focused mostly on "copy" semantics. But the ability to delete makes me think that grouping multiple selection criteria together when creating a job would be useful (e.g. "these specific pids and the results of this query should be synced to DuraCloud")
Andrew Woods:
- Much thought on fixity yet? (Chris: No, but seems clear that compare and repair should be distinct actions, and probably assisted by similar listing functionality to what's present in this mockup)