Admin tools: Legacy files migration

tool_legacyfilesmigration
Maintained by Picture of Céline Perves Céline Perves
This plugin is designed in order to migrate legacy course files to private files area for a choosen user
318 sites
302 downloads
30 fans
22 sites
2 downloads
4 fans

Legacyfiles migration admin tool for moodle 2.4 and above


Goal

This plugin is designed in order to migrate legacy course files to private files area for a choosen user

Author

Written for Université de Strasbourg(unistra.fr) by Celine Perves cperves@unsitra.fr 
Inspired from "Nicolas Can" script see https://moodle.org/mod/forum/discuss.php?d=210415 

Installation

Install the whole folder into admin/tool folder 

Use

Navigation

Under root navigation will appear a new admin category name legacyfiles migration 
this has 2 submenu : 
* Legacy files migration settings : for chaning folder name 
* Legacy files migration with the tool 

Migration

Legacy files migration will show a list of courses to migrate 
foreach of these you have to choose an editingteacher (if availabe) or fill a username 
The legacy files will be migrated into user selected private repository 

Test

For test use you can automaticaly select first user of owner lists and fill username with a username 

Features

migrate all legacy files into user private file areas 
change module resource references to files to the migrated files in user private area 
in case of folder referenced by a module resource, all the files and subfolders entries will automatically be created as module resource (in legacy files mode these were created at first consultation 

Licence

 http://www.gnu.org/copyleft/gpl.html GNU GPL v3 or later 
 http://www.cecill.info/licences/Licence_CeCILL_V2-en.html 
 
 Feel free to complete and improve this plugin 
 do not hesitate to fork and pull request 

Screenshots

Screenshot #0
Screenshot #1
Screenshot #2
Screenshot #3

Contributors

Picture of Céline Perves
Céline Perves (Lead maintainer)
Please login to view contributors details and/or to contact them

Comments RSS

Show comments
  • Picture of David Mudrák
    Thu, Feb 5, 2015, 6:11 AM
    Hi Céline. Thanks for sharing this plugin with the community. While trying to test the functionality, I encountered https://github.com/cperves/moodle-admin-legacyfilesmigration/issues/2 which is a blocker. Can we please get that sorted out (and eventually other issues I reported) before we continue with the review? Thanks in advance.
  • Picture of Céline Perves
    Thu, Feb 5, 2015, 4:14 PM
    David,
    I corrected all the issue you noticed to me and push them in reorganised git repository.
  • Picture of Céline Perves
    Thu, Feb 5, 2015, 4:15 PM
    Thank you for our help in my first contribution
  • Picture of David Mudrák
    Thu, Feb 5, 2015, 4:55 PM
    Hi Céline. Thanks for such a quick response. Please note, we are not automatically pulling from github. You have to use the "Add a new version" here at the plugin page and upload the new ZIP that we can then review and eventually approve. You can just download the ZIP from the Github and upload it here, or even better just use the Github repository in the ZIP filepicker that can fetch the ZIP for you. You will have to do this with every update of your plugin you want to release (as the diagram at https://docs.moodle.org/dev/Plugin_contribution#Overview illustrates). In this particular case, you will probably want to hide the currently uploaded version.
  • Picture of Céline Perves
    Thu, Feb 5, 2015, 6:51 PM
    thanks done
  • Picture of David Mudrák
    Thu, Feb 5, 2015, 9:13 PM
    Hi Céline. Much better now. Some more things caught my eye when reviewing the code and I reported the as individual issues in your tracker.
    There is one thing I encountered when testing the functionality of your plugin - and I am not sure it is expected behaviour. The name, the description and the UI of your plugin suggests that it's only legacy files that would be migrated/moved to the selected user's private files. But then I realized that also other files - most notably those embedded as the File activity (mod_resource) were migrated into the private area too - even if they were not legacy files. I can see the code in your locallib.php doing this but it's not clear to me why it should do that. Files embedded into the mod_resource are definitely safer in backup/restore operations. You turn them into symlinks/aliases of private files. That sounds like a step backwards to me. But I may miss something.
    I am marking this as needing more work to get these issues sorted out. Thanks for your patience with the review process.
  • Picture of Céline Perves
    Thu, Feb 5, 2015, 9:30 PM
    the itention was to migrate mod resource linked to legacy files and link them to new private user files.
    I realise thanks to your comment that I don't check if mod_resource is linked to legacyfile or other filearea. and so migrate all files.
    I'm gonnat try to filter mod_resources
    Thank you
  • Picture of Céline Perves
    Thu, Feb 5, 2015, 9:33 PM
    No problem for the review process, that's help me to improve the development
  • Picture of Céline Perves
    Tue, Feb 10, 2015, 10:06 PM
    plugin now filter resource to only migrate files linked to legacy files
  • Picture of David Mudrák
    Thu, Feb 12, 2015, 6:06 AM
    Thanks for the updated version and fixes of the issues reported in your github tracker. You are cleared to land now, welcome to the Plugins directory!
  • Picture of Céline Perves
    Thu, Feb 12, 2015, 3:53 PM
    Thank you very much for your help in this process.
Please login to post comments