This design has not been user tested yet.
This is the initial screen users will see when loading Decapod. From this screen users can create new book projects, or continue previously saved projects. They can also manage multiple saved projects from this interface as well.
- Above: User's initial view after a few other books have been started.
- There are three main panels: start a new book, saved books, and remaster process queue.
- Each panel can be minimized and dragged around like movable portlets. (Interaction needs to be finalized)
- User about to start a new book after entering some metadata.
- Metadata error detection.
- User selects a book to resume and selects Open.
Maximize and Minimize
Drag and Drop
Wireframe (Old - to be replaced)
Image 1: User's initial view.
Image 2: User about to start a new book.
Image 3: User finished editing new book, it appears in the list (assuming they saved it to the same directory location.
Image 4: User selects a file to resume.
- The welcome screen has two collapsible panels.
- Collapsed state is saved throughout user's session.
- Year field has logic to prevent users from entering invalid date (i.e. letters).
Saved Books panel
Note: The interaction for opening multiple books has not been finalized.
- This image shows what happens when there are many Decapod books in a specified Projects directory.
- The Saved Books panel expands downward as far as possible in the client's window, and displays a vertical scrollbar if necessary.
- If metadata is long horizontally, then each individual metadata field should be truncated with an ellipsis rather than have a horizontal scrollbar.
Batch Save As
|There are no images attached to this page.|
- Status messages displayed after a batch operation should not automatically disappear (as they would in other cases). This is done to help orient a user after a potentially long operation (i.e. a different user comes to the system at a later time, or the original user left and came back later).
- When resuming a book from this interface, the book should load into the appropriate stage in the workflow (capture or remaster), with the previously selected image already selected.