Page MenuHomePhabricator

Re-implement GWToolset ontop of FileImporter
Closed, DeclinedPublic


GWToolset is a maintenance burden, that no one really understands or works on...

It is duplicating a lot of the functionality that is being re-implemented in FileImporter...

I wonder, how much would work it be to reimplement the extra features ontop of FileImporter (probably still keeping it as a separate extension, but reusing Move-Files-To-Commons's file copying features etc

Event Timeline

thiemowmde added a project: patch-welcome.
thiemowmde subscribed.

GWToolset targets a very different audience with very different needs. It's true that the two projects share some technical requirements (transferring files including a lot of metadata to commons). But a lot of the code in the FileImporter extension does not apply. I would suggest two possible routes for a future project that might pick this idea up:

  1. Refactor the code responsible for file imports in core, so it's easier to use for everybody, including FileImporter and GWToolset.
  2. Possibly split useful library code from the FileImporter to a separate codebase, so it's easier to reuse in both projects.

You could also look at the FileImporter as an improved version of the upload a file from a URL already in core.
It would probably be possible to squish the extension into core? or perhaps it better stay as an extension but plug into the existing url upload functionality?
Ways to then extend the more advanced upload / import process provided by FileImporter could then be added?

Vvjjkkii renamed this task from Re-implement GWToolset ontop of FileImporter to lvdaaaaaaa.Jul 1 2018, 1:12 AM
Vvjjkkii raised the priority of this task from Low to High.
Vvjjkkii updated the task description. (Show Details)
CommunityTechBot renamed this task from lvdaaaaaaa to Re-implement GWToolset ontop of FileImporter.Jul 1 2018, 5:32 PM
CommunityTechBot lowered the priority of this task from High to Low.
CommunityTechBot updated the task description. (Show Details)