How to save folders!?!?!

[Kriger_Bendt]

Dear Support Forum!

Collanos Workplace (CW) is a great tool to share files, better than any other software out there, being cvs svn clients or ms groove. The only problem is this:

I am not able to save whole folders am i? I need to do this since my projectgroup is writing projects in LaTeX and reports consists of 200-400 files, and i do not wish to save them all manually...then svn clients are better at version control. The reason for my project group to use WC is because it runs on both windows and osx, is there any way you can save multiple files at once, and why are shared files not stored automatically in a folder instead of the cryptic datafolders?

hope you can answer my questions!

[Peter Helfenstein]

Hello,
many thanks for your positive remarks on Collanos Workplace. We love to hear success stories from active users! Collaboration is a very abstract term, real use scenarios are much more interesting and telling.

Saving content from workspaces to the file system or to reuse it in other applications is indeed a need coming up very often. We actually started to work on a prototype for file system integration of Collanos Workplace content. We expect to see this feature in one of the next releases. In the next couple of weeks Franco Dal Molin, Collanos CTO and Founder, will blog on the Collanos Workplace roadmap and file system integration will be for sure a prominent topic there.

For the moment the only help to store files from Workspaces is to select them manually and drag and drop them to the right place in the file system of your computer. Only files will be moved that way, no notes, discussions, nor tasks.
We are for sure over time also going to address storage of those elements.

Please keep in mind that the content of Collanos Workspaces is stored in an ecrypted binary form. This is done deliberately to assure that only people who know Collanos Name and password can access the content of Workspaces (or member invited). Also all data being replicated is encrypted. Together with the fact that no workspace data is stored outside of users computer Collanos Workspace data is stored and transmitted securely. For this reason we are not just going to store data locally in the file system.

I look forward to provide you with more news on that subject soon through release notes or our blog.
Cheers
Peter

[Kriger_Bendt]

Thank you for the answer Peter.

We will have to do with groove until a new release of CW is available then.

Looking forward to this!

Cheers,

Marcus

[fredson]

I totally do agree that there is a need to save folders on the file system.I have just started trying Collanos two days ago. I am evaluating it for possible use in my department. Ability to save folders will be a plus and will make it very easy for me to convince my staff. Additionally saving in binaries leads to duplication of files and therefore double the disk space is required for a any file that is saved in Collanos and on the files system. If this feature is implemented I am sure I will do all my work from Collanos. This will also enable local access to the files and folders should Collanos crash or during system upgrade taking into account that I install every new version of Fedora on my system (that is every six months)

Cheers

Fredson

[cdgeorge]

I have to agree with the concern about recovery of the encrypted data when something like an upgrade could risk losing everything - thus allowing for maybe a   file server to take responsibility of converting to native file format to facilitate easy archiving and restore of lost files or a corrupt database.

I would still keep the data encrypted on other workstations as Collanos correctly points out; this data must remain encrypted for security reasons. but to have them converted to native format on an appointed central file server (perhaps better known as the 'super team member perhaps) - would put my mind more at ease - and allow me to use standard backup and recovery procedures in place without the added complication or worry of proprietary encryption.