Open BibhaT opened 3 weeks ago
Hi, @emmajclegg
We have created three variations of the revised workflow for the bulk import and within-activity import, each divided into four sections:
Variation 1: This variation features separate pages for each functionality, offering clear separation between steps.
Bulk Import: View Here
Within Activity: View Here
Variation 2: This variation focuses on distinct visual grouping of sections within the workflow, while maintaining a unified flow.
Bulk Import: View Here
Within Activity: View Here
Variation 3: This variation keeps all the functionalities on a single page, allowing users to complete the workflow without navigating through multiple pages.
Bulk Import: View Here
Within Activity: View Here
These screens are still a work in progress, and we would greatly appreciate your feedback. Please take a look at these options and share your thoughts.
Hi @asminashrestha - thanks for these, it's definitely useful to see options.
Variations 1 and 2 look more intuitive than 3 (where I think it's too complicated having all the steps on the same page)
My favourite is variation 1, as I think it's logical to read the steps left-to-right. That said, I think it makes sense to swap the "Upload your file" block with the "Templates" block, as the workflow would be: Choose an action >> Download template or existing data >> Upload your file , if I'm interpreting it correctly?
Under "Choose an Action", we'll need to make it clear that users can update existing data and add new data at the same time by selecting the "Update existing..." option, but we can include that in the subtext.
I'm highlighting what I'm referring to here, in case it's not clear:
Any questions - or different views - let me know.
@emmajclegg Thank you for your feedback! I completely see where you're coming from regarding the left-to-right flow. I’d like to clarify that our intention wasn’t to present these elements as sequential steps but rather as individual instances, each serving a distinct role in the workflow. Additionally, in some cases, users might not always download and then upload—these actions can vary depending on their needs at the time. With that in mind, we thought placing the main action at the center would create a more flexible and user-friendly experience. However, what you’re trying to say makes complete sense if we look into these as step wise series of actions. We’ll look into your suggestions and work accordingly.
Ok, thanks for the thoughts @asminashrestha.
A potential problem that comes to mind is users trying to upload a random data file (i.e. one not in the IATI Publisher template format), which I expect some people will do regardless of the guidance we provide. We sometimes see this in support queries. So I don't think it's a bad thing to make the template more obvious in a left-to-right flow.
I agree the upload feature is the main action and you've made this obvious from its size on screen.
@emmajclegg Thanks for your feedback. As you suggested we have decided to move forward with the left-to-right approach for the design. While doing so, we also realized that the previous design didn’t make it clear that the section with download and upload options changes when the user clicks 'Add New' or 'Update Existing'. To resolve this, we’ve created an updated design that not only incorporates the left-to-right flow but also provides a more logical and intuitive user experience. Additionally, we have created a screen to handle the case where an activity has no results.
Here are the links: Bulk Import: View Link Within Activity: View Link No Result Case: View Link
Hi @asminashrestha - ok thanks, I think this looks fine.
@emmajclegg please check the links above to see the full workflow design
@praweshsth @asminashrestha - thanks.
I've added comments in Figma for the "Bulk import" and "download flow".
Mainly,
Also - I'd like to review all on screen text so let me know when the best point is to do this (and whether collaborating directly on the GitHub file is easier than comments in Figma?). We'll be reviewing English text across the tool ahead of translation, though this may still be a while off with the dependencies on automated string extraction and reintegration
Initial issue: https://github.com/orgs/younginnovations/projects/3?pane=issue&itemId=61369915
New workflow: IATI Publisher Import Workflow.pdf
Explanatory video for the same: https://youtu.be/fbrz8th02so
Things to consider: (as commented by Emma in #1439 For the download step - for info - I had already started thinking about how we simplify exporting data as a future improvement here: https://github.com/younginnovations/iatipublisher/issues/1526 (there are a lot of steps currently)
I'm happy to progress with this design, and happy to help with instruction text for the interface if you need. The main thing I think is important to make clear to users is when an import is about to overwrite existing data in IATI Publisher, which can be factored into the in-tool instructions at the "change data and upload" steps in the workflow.