Add Bulk Upload Interface

[jjeffryes]

User Story

As a user, I want to be able to upload a file or paste text that will populate my listings. It would be ideal if this could also be used to update many existing listings at once. If something goes wrong, there should be a way to delete many listings easily.

Functional Requirements

• The bulk upload section should be in the settings store tab, or in it's own settings tab.
• It should have a file input that can upload a CSV file.
• The maximum size of the CSV file should be 256mb. If it is larger than that, a warning should be shown that it needs to be broken into multiple files and uploaded in pieces.
• There should be a static warning near the input that states the upload will overwrite any listings with the same title.
• There should be a static warning near the input that states the upload will not include variants, coupons, or more than 3 shipping options with 3 services each.
• After the upload is successful, a message should be shown with the number of successful new/updated listings.
• If one or more listings has an error, a message will need to be shown with details about the listings with errors. It should state what the error is, and what row it appeared on.
• If one or more listings has an error, the entire upload should be rejected, since the error may create malformed listings earlier in the upload than the detected error.
• There should be a delete all listings button, with a confirmation tool tip, in the same place the uploader input is.
• There should be a button or link that will download an example CSV file with dummy data, and/or show instructions on how to format the CSV.

Data

• There will be an API to send the comma delimited text data as a REST call.
• It should only be possible to send listing updates to your own node.
• The listings will have a subset of the full listing data, to avoid excessive complexity in the eternal CSV.
  • there will be a maximum of 3 shipping options, with a maximum of 3 services each.
  • there will be no variants.
  • there will be no coupons.
• The API will respond with the number of updated/added listings if the upload was successful.
• The API will respond with any errors. It should indicate which row the error was on.
• There should be an error message if the server runs out of memory during the operation.
• The server will store each image on disk as it is downloaded, and remove them after. If any images cannot be downloaded and/or processed, the server will return an error.
• There will be a column for a delimited list of urls for images.
• There will be a column for a delimited list of base64 image data.
• If a listing is uploaded with the same title as an existing listing the existing listing will be overwritten.

[morebrownies]

@jjeffryes I started working on designs for this feature this morning and I realized we probably forgot to account for something important. We'll need to educate users on how to format their CSV files, otherwise they'll be clueless.

I think we have 2 options:

1. We could include information on a page on OpenBazaar.org and link to it within the client
2. We could try to jam the helper information into the client.

I'm leaning towards 1 as I think the instructions could start to get very specific based on the platform you're attempting to export data from.

Thoughts?

[jjeffryes]

@morebrownies

There should be a button or link that will download an example CSV file with dummy data, and/or show instructions on how to format the CSV.

I thought of that after the call and added it in, but didn't ring the alarm bells.

[jjeffryes]

I think providing a sample CSV, and some minimal on-page instructions are ideal, with a link to more help that goes to our site. I'm hesitant to put too many links to outside resources into the client, since it's intended to keep working if our sites go down or we all give up on tech and go live on a mountain etc.