Set default aspects for Document Library

[mike54]

I have seen several posts related to Aspects and Versioning but I still don't know how to disable default versioning aspect for Document Library?

I have noticed, that versioning is enabled by default (or aspect Versionable is added).
And even when I remove this aspect and upload new version it is back on and new version is created. I want to simply replace some documents.

So there is no way to disable it just like in Explorer - when I enable Versioning its there and cannot be removed.
Therefore I need to disable it as a default and enable only for documents that actually need it.

Regards,
Mike

[zoao]

The aspect Versionable is automatically placed by webscript in Alfresco. At this moment I can not say exactly where, but it will be something like:
alfresco/web-inf/org/alfresco/…/templates/repository/upload /…post.js

[mike54]

How about creating a Rule for all items - Remove aspect 'Versionable' ?
Is that the proper way to do it?

[mike54]

Thats so annoying! eggghhh
I have created this rule - It works and removed this Versionable aspect.
When I go to Explorer, versioning is disabled.
But Share does not have Update - it has only Upload new Version - so after that operation the version is enabled again and I end up with two versions….

Please tell me it is possible to upload documents without versioning using Share

Mike

[mikeh]

Please tell me it is possible to upload documents without versioning using Share

No, not currently by config or rules alone. We've learnt that the vast majority of Share users are confused when something *isn't* versioned, therefore versioning is added on file upload.

You just need to override org/alfresco/repository/upload/upload.post to remove the forced versioning.

Thanks,
Mike

[mike54]

ok MikeH,
thanks for the explanation

I'm sure you have a bigger experience with all this, but I believe system administrator should have ability to disable Versionning for a specific site or space, by simply creating a rule as I did. When custom rules don't take effect as expected because some other behavior is forced it can be confusing…
Thats my opinion, but I might be wrong…

Now it is like "we know what is best for you. You will use versionning whether you like it or not"

[mikeh]

I agree - we need to expose the behaviour through config. That's certainly true for many Global and Site parameters… we'll get there eventually!  :wink:

Thanks,
Mike

[zoao]

The Versionable aspect, can not be added to a folder and say that applies to all children?

If this is possible, the default behavior, could be adding this aspect to the DocumentLibrary root folder, when a site is created. In this way can then be removed by the administrator, or can remove the aspect  only in a subfolder.

[mike54]

zoao - the problem is that Share code checks upon document upload if it has Versionable aspect.
If it does not - it is added by default.
So even if you remove this aspect it will be added automatically.

Or do you mean future solution?
As MikeH said it will be configurable somewhere in the future

Regards,
Mike

[zoao]

Yes, I mean for future solution.
Because a configuration per site, may not be enough, because I think it should be possible to set Versionable default on a site and just not having a sub-folder of the site Versionable.