nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Deleted items retention time and CIFS best pratices question

hikenboots

Is there a time limit on how long deleted items are stored or must users manually purge the deleted items store periodically to keep the size down?

Also, I have users who are working on documents directly through the CIFS interface. It is a little laggy but the real problem to me is that MS Word writes it's temp and recovery files into the working directory (CIFS) and the deleted items store is collecting a lot of junk in this manner. Is this a bad idea to work directly from within CIFS in this fashion?

TIA,
John

Find more posts tagged with

Comments

derek

Hi,

The contentstore.deleted store doesn't have a cleaner watching it. You can add a cleaner and trigger bean for it by copying beans content-services-context.xml#contentStoreCleaner and scheduled-jobs-context.xml#fileContentStoreCleanerJobDetail into an extension context.

You could also remove the contentstore.deleted store completely if you are sure that your backup mechanisms are adequate. The content wont' be reaped until it is at least 14 days old (by default). It is mainly there to ensure that we don't throw content away - if you want, you can delete contentstore.deleted after backing up.

MSWord does create loads of junk. It is not bad to use CIFS this way, though. If the disappearance of these files is not fast enough, then we could add some specific handling for content attached to nodes with the sys:temporary aspect.

Regards

dwild_hq

Derek,

Great! A timely thread….

I like that the content is not removed from contentstore for 14 days, configurable in content-services-context.xml?? and then moved to contentstore.deleted

However, from the perpestive of restoring content deleted by users inadvertently, i am yet to find if one exists a way of locating the deleted content without restoring the entire alfresco instance. Am i missing something?

A utility along the lines of recover deleted items would be nice!

Thanks in advance for any replies.

Dave Wild.

kevinr

Deleted Items for a specific user (or all users in the case of Admin) can be managed through the "Manage Deleted Items" in the "More Actions" menu of the main browse screen.

Thanks,

Kevin

dwild_hq

Kevin,

Don't I feel stupid

ops: It couldn't be much more obvious!

Thanks

Dave

hikenboots

The contentstore.deleted store doesn't have a cleaner watching it. You can add a cleaner and trigger bean for it by copying beans content-services-context.xml#contentStoreCleaner and scheduled-jobs-context.xml#fileContentStoreCleanerJobDetail into an extension context.

You could also remove the contentstore.deleted store completely if you are sure that your backup mechanisms are adequate. The content wont' be reaped until it is at least 14 days old (by default). It is mainly there to ensure that we don't throw content away - if you want, you can delete contentstore.deleted after backing up.

MSWord does create loads of junk. It is not bad to use CIFS this way, though. If the disappearance of these files is not fast enough, then we could add some specific handling for content attached to nodes with the sys:temporary aspect.

Hi Derek,
Sorry for the delay in reply; I've been traveling for a couple of days. Thanks for the tips, I'll try the cleaner extension this weekend. That should solve any potential storage space problem from a practical standpoint.

Is there much work involved in setting up handling for temp files? From watching clients work, I think that it is important from a usability standoint. I've noticed them clicking the save or close button multiple times; an impatient bunch.

This is definitely going to come up from a user standpoint.

The overall reception to Alfresco has been great to say the least. A quick one: I was training an Attorney in his office last week. He took a call and began looking for a document. From the context of his call I pulled up the correct document on my laptop via the search function before he could navigate his directory tree. They are really starting to get it.

Thanks,
John

hikenboots

….
MSWord does create loads of junk. It is not bad to use CIFS this way, though. If the disappearance of these files is not fast enough, then we could add some specific handling for content attached to nodes with the sys:temporary aspect.

Regards

Temp files are proving to a bit of a problem in everyday use of the system. I have a rule set up to send email to paralegals when a file is placed in the drafts subspace of a client's space. The problem is that if an attorney opens the file in drafts subspace, an email message fires that "~xxx.tmp" has been placed in this space. Also, work documents take too long to save directly from within CIFS. We need to be able to tag (aspect) files beginning with'~' or ending in ".tmp" as temporary and have them treated as non-content (they don't fire emails, are not indexed, do not go to contentstore.deleted, etc.). Anyone using the system via CIFS is going to run into this issue; May I request this enhancement? I wish I knew enough to contribute to the task, I think it is important. Thanks, John

derek

Hi,

It is on the list of issues to fix prior to the 1.4 Enterprise Beta comes out.
http://issues.alfresco.com/browse/AR-698

Thanks for the comments.

Regards