Document Management System

[nwaughachukwuma]

Hi @sroutier, it would be nice if you added a document manager (with CRUD capabilities on Files) to the next release of this already awesome application. Just a thought anyway.

[sroutier]

Hello @nwaughachukwuma, sorry for the delay in replying to you. I have been pulled away with other activities but with the advent of Laravel 5.5 LTS fast approaching I am now thinking about upgrading this project.
With regards to your suggestion, it's a good one, a little document/file manager would be a great idea for a plugin. As full DM/RM or even ECM system may be out of scope.
Would you be interested in helping us add this module to our collection? I am sure that a lot of people would appreciate.

[nwaughachukwuma]

Hi @sroutier sorry this is coming late. What we have done is integrate this: https://github.com/UniSharp/laravel-filemanager into our application, and program it to behave in the way we want. Am open to working with you in whatever measures you intend to integrate or build a plugin that can achieve the same behavior. Thanks

[sroutier]

Hello @nwaughachukwuma, that file-manager package is pretty cool, integrating it within LESK would be a great addition.
If you do not mind I would have a couple of quick questions to try and better understand your point of view and requirements:

1. So the file-manager allows you to upload a file on the server, then what? How is that file used? Is it available through a route? Does that mean that routes to files are also dynamically created during each upload?
2. The file-manager plug-in also supports a fancy editor (CKEditor or TinyMCE), did you also create a page creation tool using this to allow users to dynamically create their own page? This may be where the files uploaded in question 1 could be used or referred to.
3. Finally, would you see this addition better placed in the core or in a plug-in? Personally, I would refrain from adding a whole bunch of new features and options in the core if it can be avoided. If would make the core easier to deploy and maintain; that being said I have not looked at the specifics of this feature.

It would be great if you could contribute that functionality and I will try to assist you as much as I can.

Cheers.
/s

[nwaughachukwuma]

Hi @sroutier, I will answer your questions in the other you have asked them:

1. The file-manager for us is a place to keep all the files in the organization (system), like a central archive. The system allows for sharing of files, which we achieved virtually. When a new file is uploaded, it seats on the file-manager, and added to a path in the project directory (public/doc/files...). And also an entry is created in the database.

2. We didn't use the CKEditor or TinyMCE for this purpose, in fact, we barely used both. Going by 1, users have their dashboards and when a file is shared they have access to it.

3. I think it should be made available as a plugin with an excellent documentation on how it can be used. While researching, we stumbled upon this other document manager which is very robust (https://github.com/sjarvela/kloudspeaker), and I think they implemented the system using plugins.

Let me know how you intend to use this info to improve Lesk. Thanks

[sroutier]

Hello, Very interesting. I have been doing some light research on the subject these last few days, to be better able to talk with you on the subject. When you create a new file and an entry is created in the database, is the entry an Eloquent model? I looked at these couples of projects, as well as the one you pointed me to: https://github.com/reshadman/file-secretary https://github.com/spatie/laravel-medialibrary Having an Eloquent model would be useful for manipulation handling later. What you are proposing is very interesting and I would love it if you could create a module to provide such functionality. It could then later either be further improved or another module could be created to add to the functionality of a page editor to allow the creation of new pages from the Web interface that could reference some of the files uploaded by your module. I am currently neck-deep in the work of upgrading LESK to Laravel 5.5 with new and updated packages but if I can help you with anything let me know. Cheers. /Seb.

…

On Tue, Aug 29, 2017 at 11:18 PM, Chukwuma Nwaugha ***@***.*** > wrote: Hi @sroutier <https://github.com/sroutier>, I will answer your questions in the other you have asked them: 1. The file-manager for us is a place to keep all the files in the organization (system), like a central archive. The system allows for sharing of files, which we achieved virtually. When a new file is uploaded, it seats on the file-manager, and added to a path in the project directory (public/doc/files...). And also an entry is created in the database. 2. We didn't use the CKEditor or TinyMCE for this purpose, in fact, we barely used both. Going by 1, users have their dashboards and when a file is shared they have access to it. 3. I think it should be made available as a plugin with an excellent documentation on how it can be used. While researching, we stumbled upon this other document manager which is very robust ( https://github.com/sjarvela/kloudspeaker <https://github.com/sjarvela/kloudspeaker>), and I think they implemented the system using plugins. Let me know how you intend to use this info to improve Lesk. Thanks — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#94 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AC30FsYqmaIUpT1oEUkyTWg4D_2wjOGIks5sdNSjgaJpZM4NopJ2> .