topic Re: Age-Off Unaccesed Files in Alfresco Archive https://connect.hyland.com/t5/alfresco-archive/age-off-unaccesed-files/m-p/285277#M238407 <HTML><HEAD></HEAD><BODY><SPAN>Hello,</SPAN><BR /><BR /><SPAN>cm:accessed exists in the data model but is not maintained by default to avoid performance overhead for something that most people won't use. Also, the meaning of cm:accessed can be quite different (accessed metadata vs. accessed content; user access vs. system access) depending on user / customer requirements, so it is difficult to come up with an efficient way to track this that can cater to all potential parties. As long as cm:accessed is not maintained you can't query for it. You could write custom functionality that does maintain that property using your semantics of "accessed".</SPAN><BR /><BR /><SPAN>That covers #1…</SPAN><BR /><BR /><SPAN>The URL / path in a content store may not belong to exactly one node, so it can not always be translated to a single, unique node. Also, some paths in the content store may be in the "orphaned" stage where not a single node claims ownership of it. A reverse lookup of path to node is possible via the database, but there isn't an API / service operation to do that which might be accessed from an addon.</SPAN><BR /><SPAN>Due to the non-uniqueness of path-to-node relations, you might also end up in the situation where accessing one node in Alfresco keeps the other one alive despite it not being accessed at all. Additionally, the access time in the file system may be updated by any process that runs on your server, i.e. backup &amp; recovery processes, messing up the evaluation from the user perspective.</SPAN><BR /><BR /><BR /><SPAN>Personally, I would go with option #1 and implement the various hooks / extensions to maintain the cm:accessed property. But this is something that is not at all trivial due to the special features of all the various interfaces Alfresco provides. So for any casual user / customer of Alfresco, I would not advise to tackle that without professional support (you could sink a lot of time).</SPAN><BR /><BR /><SPAN>Regards</SPAN><BR /><SPAN>Axel</SPAN></BODY></HTML> Thu, 18 Feb 2016 09:29:25 GMT afaust 2016-02-18T09:29:25Z Age-Off Unaccesed Files https://connect.hyland.com/t5/alfresco-archive/age-off-unaccesed-files/m-p/285276#M238406 We have about 1 million files in our Alfresco that have not been &lt;strong&gt;accessed&lt;/strong&gt; (aka viewed in share/explorer) in over a year. We want to remove these files. Even more we want to implement a age-off policy that removes files automatically when they haven't been accessed in a y Wed, 17 Feb 2016 15:59:29 GMT https://connect.hyland.com/t5/alfresco-archive/age-off-unaccesed-files/m-p/285276#M238406 jsb 2016-02-17T15:59:29Z Re: Age-Off Unaccesed Files https://connect.hyland.com/t5/alfresco-archive/age-off-unaccesed-files/m-p/285277#M238407 <HTML><HEAD></HEAD><BODY><SPAN>Hello,</SPAN><BR /><BR /><SPAN>cm:accessed exists in the data model but is not maintained by default to avoid performance overhead for something that most people won't use. Also, the meaning of cm:accessed can be quite different (accessed metadata vs. accessed content; user access vs. system access) depending on user / customer requirements, so it is difficult to come up with an efficient way to track this that can cater to all potential parties. As long as cm:accessed is not maintained you can't query for it. You could write custom functionality that does maintain that property using your semantics of "accessed".</SPAN><BR /><BR /><SPAN>That covers #1…</SPAN><BR /><BR /><SPAN>The URL / path in a content store may not belong to exactly one node, so it can not always be translated to a single, unique node. Also, some paths in the content store may be in the "orphaned" stage where not a single node claims ownership of it. A reverse lookup of path to node is possible via the database, but there isn't an API / service operation to do that which might be accessed from an addon.</SPAN><BR /><SPAN>Due to the non-uniqueness of path-to-node relations, you might also end up in the situation where accessing one node in Alfresco keeps the other one alive despite it not being accessed at all. Additionally, the access time in the file system may be updated by any process that runs on your server, i.e. backup &amp; recovery processes, messing up the evaluation from the user perspective.</SPAN><BR /><BR /><BR /><SPAN>Personally, I would go with option #1 and implement the various hooks / extensions to maintain the cm:accessed property. But this is something that is not at all trivial due to the special features of all the various interfaces Alfresco provides. So for any casual user / customer of Alfresco, I would not advise to tackle that without professional support (you could sink a lot of time).</SPAN><BR /><BR /><SPAN>Regards</SPAN><BR /><SPAN>Axel</SPAN></BODY></HTML> Thu, 18 Feb 2016 09:29:25 GMT https://connect.hyland.com/t5/alfresco-archive/age-off-unaccesed-files/m-p/285277#M238407 afaust 2016-02-18T09:29:25Z