The current iteration of the File Manager in Admin Refresh does not have the full set of functionality as the previous version, this limits the ability to do the following: -Rename files -Centralize file management -File re-use
Commenting on this two year old thread in support of the many concepts that were raised for file management that are not easily available in the 'new' file manager that exists today. All of the details in the comments are valuable and should be reviewed in detail by the dev team
When bringing back the filemanager, pls include an option, so that system admins can choose/assign according to a department/country, sub-department structure, who can see/edit/change what files in the filemanager; e.g., German Marketing and German Sales departments can only see and/or access/edit specific files in the filemanager. Another country, e.g. Poland can only see and edit their own files etc. .... If possible, also included the possibility to choose specific admins (admin drop down?). This functionality should be independent of the users that have been assigned to an admin/that the admin can manage, specified in his/her user account (not like the current course visibility list functionality, which only works on a department level but not subdepartment level because of this.
This idea is indicated as Currently On Roadmap. Is there an ETA for this? The reduction of features from the previous file manager continues to prove inefficient and exponentially more time consuming.
I would like to see the functionality of the previous (pre-A5(AR)) file manager return.
I agree that the new version is extremely limited with the reduction of all its features. Not being able create folders, organize, rename, and upload files, or zip files of a course that contain various supporting files to unzip and use is very restrictive.This is critical to us as we have multiple and independent contracts using the LMS.
Our courses are built as packages and these packages contain a number of individual files and folders contain the course material that the index_tincan.html launch file depends upon. These are typically uploaded to our LMS in an organized filed structure we have created and then unzipped in its on course folder location. The course itself then points to the launch file located with all its others dependencies.
This new file manager is practically useless. Having to choose a single file from the course page directly may seem like a good idea on the surface but is impractical. The course does not upload zip files and if it did, you cannot unzip or choose the launch file. Attempting to upload the launch file itself is just as useless as the course will not launch without all the supporting files its missing.
These changes to the file manager were a huge step in the wrong direction.
The changes to the file manager have drastically curtailed our ability to locate and manage course content, including clearing out old files and determining exactly which files are being used in a course.
Duplicating a course now means, as far as I can tell, duplicating all the files associated with the previous version. We release new courses using an evolving template with additions/replacements to the previous content, so this presumably means that the total memory requirement increases each time we do so and may now run into multiple GB.
The file manager was particularly useful for:
deleting old/unused files, including those created when several versions of a SCORM file were uploaded to check/fix technical issues (or just course updates)
using the same base file in different version of a course (we have many clients who want personalized versions, so we change the name/thumbnail/category but use the same SCORM files)
with the addition of video transcription (a useful feature) it is sometimes not possible to locate the VTT files in the file manager so that we can download, edit and re-upload them (meaning we're stuck with the AI's version; the single line editing feature is painful when dealing with a 1 hour video and, as stated, we have different versions of a course so it would have to be done for each version)
The above reduced functionality and inefficiencies (rework, duplication) that result threaten content launch timelines and hurt the reputation of our team and the LMS within the company. I hope these can be addressed by Absorb in the near term.
We shared this with our CSM, but the file manager as it stands in the Refresh is far inferior to the file manager in legacy. The ability to upload multiple files, organize and reorganize, and re-use files is integral to our process and adds hours to our development time. Open to sharing our experience on a call if applicable, but please prioritize the configuration of the file manager.
File manager in the legacy form is not returning as it was brittle, difficult to navigate, and inaccessible. The solution we are currently developing makes all of the functionality below possible in a workflow centric manner.
Just want to highlight this idea and underscore how essential it is to the LMS.
I'm just starting in Absorb (still in implementation) and this File Management capability is absolutely critical to the current and future use of our LMS.
The current limited functionality of file management I'm experiencing in Admin Refresh isn't sustainable for system admins, creates a huge potential risk in file management and reliability of course content, and ultimately will impact the user experience.
We need a single file source in the LMS (ideally the file manager/resources). Then for courses to be able to use that single file source via hyperlink (or via pulling it in a file already loaded in the file manager as an object - similar to how scorm/tin cans can be resused) in both the course and the course resources.
When we have an update to that file we would want to be able to replace the file in the single location (in file manger/resources), have the name stay the same or be able rename, but then have all instances of that file and the links of that file to show that replacement automatically.
(Additionally, having admin permission capabilities for file management/folders would be a plus so not all admins have access to ALL files in the site).
This is so critical to the success of our LMS. Please let me know if I can share scenarios or use cases that would be helpful in order to get this implemented into the Admin Refresh. Thanks!
Commenting on this two year old thread in support of the many concepts that were raised for file management that are not easily available in the 'new' file manager that exists today. All of the details in the comments are valuable and should be reviewed in detail by the dev team
Please put this at the front of the roadmap, is there any idea on an eta?
When bringing back the filemanager, pls include an option, so that system admins can choose/assign according to a department/country, sub-department structure, who can see/edit/change what files in the filemanager; e.g., German Marketing and German Sales departments can only see and/or access/edit specific files in the filemanager. Another country, e.g. Poland can only see and edit their own files etc. .... If possible, also included the possibility to choose specific admins (admin drop down?). This functionality should be independent of the users that have been assigned to an admin/that the admin can manage, specified in his/her user account (not like the current course visibility list functionality, which only works on a department level but not subdepartment level because of this.
This idea is indicated as Currently On Roadmap. Is there an ETA for this? The reduction of features from the previous file manager continues to prove inefficient and exponentially more time consuming.
I would like to see the functionality of the previous (pre-A5(AR)) file manager return.
I agree that the new version is extremely limited with the reduction of all its features. Not being able create folders, organize, rename, and upload files, or zip files of a course that contain various supporting files to unzip and use is very restrictive.This is critical to us as we have multiple and independent contracts using the LMS.
Our courses are built as packages and these packages contain a number of individual files and folders contain the course material that the index_tincan.html launch file depends upon. These are typically uploaded to our LMS in an organized filed structure we have created and then unzipped in its on course folder location. The course itself then points to the launch file located with all its others dependencies.
This new file manager is practically useless. Having to choose a single file from the course page directly may seem like a good idea on the surface but is impractical. The course does not upload zip files and if it did, you cannot unzip or choose the launch file. Attempting to upload the launch file itself is just as useless as the course will not launch without all the supporting files its missing.
These changes to the file manager were a huge step in the wrong direction.
The changes to the file manager have drastically curtailed our ability to locate and manage course content, including clearing out old files and determining exactly which files are being used in a course.
Duplicating a course now means, as far as I can tell, duplicating all the files associated with the previous version. We release new courses using an evolving template with additions/replacements to the previous content, so this presumably means that the total memory requirement increases each time we do so and may now run into multiple GB.
The file manager was particularly useful for:
deleting old/unused files, including those created when several versions of a SCORM file were uploaded to check/fix technical issues (or just course updates)
using the same base file in different version of a course (we have many clients who want personalized versions, so we change the name/thumbnail/category but use the same SCORM files)
with the addition of video transcription (a useful feature) it is sometimes not possible to locate the VTT files in the file manager so that we can download, edit and re-upload them (meaning we're stuck with the AI's version; the single line editing feature is painful when dealing with a 1 hour video and, as stated, we have different versions of a course so it would have to be done for each version)
The above reduced functionality and inefficiencies (rework, duplication) that result threaten content launch timelines and hurt the reputation of our team and the LMS within the company. I hope these can be addressed by Absorb in the near term.
We shared this with our CSM, but the file manager as it stands in the Refresh is far inferior to the file manager in legacy. The ability to upload multiple files, organize and reorganize, and re-use files is integral to our process and adds hours to our development time. Open to sharing our experience on a call if applicable, but please prioritize the configuration of the file manager.
Amazing! Thank you so much Paul for the follow up and additional information about the solution the team is working on. I'm looking forward to it!
File manager in the legacy form is not returning as it was brittle, difficult to navigate, and inaccessible. The solution we are currently developing makes all of the functionality below possible in a workflow centric manner.
Hi there!
Just want to highlight this idea and underscore how essential it is to the LMS.
I'm just starting in Absorb (still in implementation) and this File Management capability is absolutely critical to the current and future use of our LMS.
The current limited functionality of file management I'm experiencing in Admin Refresh isn't sustainable for system admins, creates a huge potential risk in file management and reliability of course content, and ultimately will impact the user experience.
We need a single file source in the LMS (ideally the file manager/resources). Then for courses to be able to use that single file source via hyperlink (or via pulling it in a file already loaded in the file manager as an object - similar to how scorm/tin cans can be resused) in both the course and the course resources.
When we have an update to that file we would want to be able to replace the file in the single location (in file manger/resources), have the name stay the same or be able rename, but then have all instances of that file and the links of that file to show that replacement automatically.
(Additionally, having admin permission capabilities for file management/folders would be a plus so not all admins have access to ALL files in the site).
This is so critical to the success of our LMS. Please let me know if I can share scenarios or use cases that would be helpful in order to get this implemented into the Admin Refresh. Thanks!
Julie