topic Re: Set default aspects for Document Library in Alfresco Archive

Set default aspects for Document Library

mike54 — Fri, 23 Oct 2009 10:37:07 GMT

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

Re: Set default aspects for Document Library

zoao — Fri, 23 Oct 2009 12:06:46 GMT

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

Re: Set default aspects for Document Library

mike54 — Fri, 23 Oct 2009 12:11:25 GMT

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

Re: Set default aspects for Document Library

mike54 — Fri, 23 Oct 2009 12:20:09 GMT

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

Re: Set default aspects for Document Library

mikeh — Fri, 23 Oct 2009 13:34:23 GMT

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

Re: Set default aspects for Document Library

mike54 — Fri, 23 Oct 2009 14:48:43 GMT

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"

Re: Set default aspects for Document Library

mikeh — Fri, 23 Oct 2009 15:32:51 GMT

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

Re: Set default aspects for Document Library

zoao — Fri, 23 Oct 2009 16:11:55 GMT

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.

Re: Set default aspects for Document Library

mike54 — Mon, 26 Oct 2009 08:39:49 GMT

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

Re: Set default aspects for Document Library

zoao — Mon, 26 Oct 2009 10:52:37 GMT

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.

Re: Set default aspects for Document Library

whispering — Wed, 13 Jul 2011 07:37:26 GMT

Hi

This is not a solution but a way to implement only one version of a document.

As a site manager, manage permissions on a document so that all the roles are set to "No Privileges".
This will create one version of a document which cannot be seen at all by others.

Alternatively, if the intent is for the document to be seen - as a site manager - do the following:
Create a folder where the manage permissions for all roles are set to consumer

If either of the above two paras is carried by any other lower role (other than the site manager) - all higher roles will override - impose their authority - i.e. the document may not stay as a single version

cheers
whispering