Open
Description
Many users create unique import JS for specific templates such as 'blogs', 'news', 'events', etc. They keep a list of those URLs in files and then copy/paste them into the URLs field and then change the Transformation file URL field to match those templates (i.e. blog.import.js, or news.import.js).
That is awkward.
Expected Behaviour
Matching the list of URLs (templates) to the JS script could be done many ways. For example:
- For "Transformation file URL", the user enters: http://localhost:3001/tools/importer/blog.import.js
- A new "Load URLs" button is clicked.
- The script reads http://localhost:3001/tools/importer/blog.import.txt which contains 1 URL per line.
- In Workbench view: load the first (or a random one if CTRL is held with the click)
- In Bulk view: load the entire list into the field
- If successful, the URL field is populated with the valid URLs found in the txt file.
- If not, it leave the URL field as is.
FUTURE
- Could crawling help set up the TXT files?
Actual Behaviour
There is a lot of copy/pasting and manual typing and awkwardness when managing/matching URLs and scripts.
Reproduce Scenario (including but not limited to)
Steps to Reproduce
Platform and Version
Sample Code that illustrates the problem
Logs taken while reproducing problem
Metadata
Metadata
Assignees
Labels
No labels