[MBLINKS-6] Export/import would be nice Created: 12/Dec/17  Updated: 15/Mar/21  Resolved: 15/Mar/21

Status: Closed
Project: Link Mapper
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: New Feature Priority: Neutral
Reporter: Zak Greant Assignee: Jan Haderka
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

It's difficult to validate links, review, etc. directly in the app. It would be nice to have a CSV-format import and export.



 Comments   
Comment by Jan Haderka [ 13/Dec/17 ]

what would make it easier than?

Export/import omission was on purpose. If this is the way you want to go, you can use GA directly and generate import files for Apache and save yourself hassle of going through Magnolia. I would be much more interested in curation features that would make it easier to use Magnolia rather than externalising task to other tools ... or realizing that we can't make it easier in-Magnolia and drop the effort altogether in favour of the other tools that are already much more convenient.

Comment by Zak Greant [ 13/Dec/17 ]

I don't think that it's so black and white. For many tasks, a GUI is the right choice. In other cases (eg. when launching a new site), it would be important to export all the redirects, massage them and import them back in for the new site.

In general, I do think that the tool is a good idea. However, if there is any volume of 404s, then it is challenging to use at the moment. The other feature requests (filter, flush, order, search and validate) all would make it more efficient. As it is, we're looking at 1-3 minutes per link to manage links and that doesn't work when we have 2k+ 404 links to wade through.

Comment by Jan Haderka [ 15/Mar/21 ]

No longer developed.

Generated at Mon Feb 12 02:22:07 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.