Foundations for post-import workflow in browser

[Jason Gerard DeRose]

I've been talking with Tara about the sort of workflow that makes sense for sifting through newly imported files, so I'm going to take a stab at roughly implementing this. I'm just going to focus on getting the semantics right, wont worry about making it pretty (I'll let James to that, as then it will actually being pretty cuz James rocks).

The UI needs to first make it clear whether there are any Unprocessed files (files that you imported but haven't sifted). This is your workflow Inbox.

I have a hunch that the first pass should be just one of two actions: Keep or Reject.

The Rejected files will be lazily deleted only when space is needed. In dmedia, I'm deliberately avoiding a Trash because in my experience, a Trash often becomes just a 2-step Delete without much thought. In other words, "Delete" and "Empty Trash" become so reflexively coupled that a Trash isn't really providing a way to undo the Delete.

I keeping with our "dmedia wont even give you the opportunity to make stupid mistakes" guidance, we should preserve the "undo" for as long as possible, till the space is actually needed.

I expect the 2nd pass would be rating, tagging, and similar.

[Jason Gerard DeRose (jderose)]

Ended up doing some much foundational work (on JavaScript in particular) that I went ahead and merged this even though the scope of the bug isn't yet complete.

I opened a new bug for the finishing work:

https://bugs.launchpad.net/dmedia/+bug/768571

I targeted above for 0.7 as being able to declare the schema stable is the most important for 0.6, and we have just a week left.