0

The scenario is a user has organised a bunch of folders and files which will be stitched together to form a book online. The idea is users will be able to drag & drop / click to upload all of these files and folders at once, rather than doing them individually.

Added complexity: users structure their files and folders differently which often calls for custom import settings. There's 3 key settings that vary depending on the user and the book they're creating.

  1. Create a chapter per file (very common setting turned on)
  2. Number chapters (useful for majority of users)
  3. Remove leading numbers (users will add numbers to their folders / files to create a custom order, for example "01__My First Chapter" will be ordered before "02__Bees can fly".

When a users first creates a book, it's significantly likely they'll stick to the upload settings they've defined as that's how they're structuring the book in their file management system.

I have two workflows I'm having difficulty deciding between. One pretty seamless, the other adds a layer of security / validation of how things are being imported later down the track.

  1. Let the user pre-define their bulk import settings, and from that point on any files that are uploaded will inherit those properties. This can be changed manually in a separate options menu, but when the user uploads their files, they upload and are modified instantly to match your import settings. To me this would be a seamless approach so the user can add any additional files in the future and they'll be presented as they've defined. However some situations might call for NOT creating a chapter per file as they're being uploaded and would mean the user would have to update their settings beforehand in order to ensure they're uploaded how the user expects. Or upload files individually and just re-order / change them if necessary.

  2. We could still do some pre-defined settings when a book is initially created and empty, however in the future if the user wants to upload multiple files, we provide the user the ability to configure their import settings before starting the upload. What I don't like is that this introduces an additional step when uploading files in bulk instead of a seamless interaction like google drive.

Would be keen to hear your thoughts. Originally I wanted to have it so you could seamless upload whatever content you wanted, and could configure the presentation easily later on if needed — however due to the dev infrastructure it would be a significant effort to do this.

I've found it difficult to find examples of bulk import settings / configuration as you're uploading — usually it just starts and that's how it is so this is a kind of unique workflow.

Cheers.

0

Christian, how will your users initiate an upload in the first place? E.g., will there be a dialog in which users select the files to be uploaded, etc.?

As a possible compromise between the two (valid) options you describe, you might want to consider this, if the upload flow includes some kind of dialog box: include the options in that dialog box and persist their settings, so they do not reset to their defaults when the users closes and then relaunches the application.

That way, your uses can instantly change the settings for every upload, but they don't have to set them each time once they have found the settings that are right for them.

  • Good question. The upload can be initiated in 2 ways — both begin with an empty book, an empty state prompting the user to either drag and drop their files, or click "browse" to select the files they want to upload. Forgive me for not providing screenshots as the design assets / output is confidential. – Christian Dixon-McIver Jul 4 at 4:48
  • Initially the empty state prompted the user to configure their import, and then the user would upload their files in a seamless way, building their book. It's a seamless upload which is great, we do some magic, however the user is forced to visualise what the end result will look like, which I want to avoid as it demands them to think a lot. – Christian Dixon-McIver Jul 4 at 4:48
  • 1
    Instead I'm opting to have the user drag and drop their files, we mock up what their book will look like, we provide some options to configure how it looks which will happen dynamically, once they're happy they click a button to start the upload, then things start to happen. Essentially I think this is the dialog option you've described as a compromise so I think we're on the same page :). – Christian Dixon-McIver Jul 4 at 4:48
  • Sure sounds like it, Christian, especially if you persist settings between uploads. (Well, at least those settings that can be meaningfully persisted, because they're not specific/different for each upload…) – JochenW Jul 8 at 4:45
  • Yeah that will be my next challenge — how do we let the user create default settings and persist those settings. Which could either be automatically, or by encouraging the user to check something to save them as their new default. I don't think there's too much issue with just having the setting be your "last used setting" so I'll be prototyping and testing this one first. Thanks again Jochen :). – Christian Dixon-McIver Jul 9 at 2:50

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.