"Marked for deletion" vs "Marked for move/rename"

TeamSite 6.1 SP2
Solaris 8

I’m writing a script to clean up “deleted” files. The problem is that I can’t seem to find a programmatic method to distinguish between files that are “Marked for deletion” and “Marked for move/rename”. If you don’t know what I’m talking about, hover your mouse over the icon of a deleted or moved file and read the ALT text. Normally I’d use the “iwlistmod” CLT to give me a list of files deleted in the folder. However, iwlistmod doesn’t seem to distinguish between the two (i.e., both states return a code of “x+”).

Has anyone else had to do this? Clues? Suggestions?

Thanks in advance,

Dan Pike
Senior Consultant
Strategic Solutions Northwest
dpike@ssnwllc.com

Find more posts tagged with

Comments

Migrateduser

Dan,
What exactly do you mean by "cleanup deleted files"? You cant actually remove the files with the deleted icon. You'll have to submit the deletions at which point they wont be visible in the "All files" view. If you go to the "All and Deleted Files" view, you'll still see the item with a deleted mark next to it.

There is not clt that can give you this information but you can use the Content Services SDK. The method to use would be getCorrespondingFile which is part of the CSFile interface.

Shashi

Migrateduser

Shashi,

Thanks for responding. Sorry...I should have been more specific. In the "All Files" view, you see files that have been deleted from the workarea, but still exist in STAGING. However, as far as the CCPro is concerned, there are two types of deleted files: "Marked for deletion" or "Marked for move/rename". My Perl script needs to submit the deletions that are "Marked for deletion" to STAGING, but it needs to ignore the ones that are "Marked for move/rename". You may be correct that there is no CLT that can do this.

I've never used the Content Services SDK, but I'll take a look to see if that can solve my problem.

Dan Pike
Senior Consultant
Strategic Solutions Northwest
dpike@ssnwllc.com

Adam Stoller

While I'll admit that if the UI makes the distinction - the CLT should be able to do so too - I have to wonder - why does it matter?

If a file has been moved/renamed - it leaves behind a "hole" with the original name of the file in the original location - the same way that a deleted file leaves a "hole" in the place where it used to exist. In both cases - until you submit the deletion - the "ghost" of the file remains behind.

Why would you want to leave the "ghost" image behind for a file that was moved/renamed ?

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Migrateduser

Heya, Fish. Good question. I figured someone would ask at some point Smiley Wink

Here's why I need to figure out how to tell the difference from the CL:

Deleted files
- Submit to STAGING
- Delete from web servers (i.e., File list deploy the deletes using OpenDeploy)

Moved/Renamed files
- Leave alone for now because many users haven't published their moved/renamed files yet.

In short…I'm 100% sure I want to remove "Deleted" files, so I'd like to be able to separate them out (programmatically) from the "Moved/Renamed" ones.

I'll shoot this to IW support. I'm guessing that it'll have to be logged as a Feature Request.

Dan Pike
Senior Consultant
Strategic Solutions Northwest
dpike@ssnwllc.com

Adam Stoller

You might be able to use iwrlog to track the moved/renamed file - but I'm not sure that will work when referencing the ghost file.

The general solution we came up with at one of my customer sites was to add custom menu items for deleting, moving, and renaming files - which basically went through the whole process of performing the operation and then submitting the deleted ghost files and deploying both the new and deleted files (as deletions).

It takes a bit more effort, but it provides a cleaner start-to-end solution.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Migrateduser

we had to deal with moves/renames vs. deletes issue recently, as well, since they trigger different types of index updates/workflow validations...

For files that have previously made it to Staging, I’ve discovered the following behaviour:

1) old name shows up as a deleted file, and the “properties” contain the comment [moved to ]

Key info from File Properties for object_browser_callout.cgi (Deleted icon)

Name: object_browser_callout.cgi

Location: //deviw01/default/main/DIG_Admin/WORKAREA/dev/httpd/iw-bin

Version: 2+

Comment: [moved to /httpd/test_move.file]

2) the new name shows up as version “0+”, and no comment…if you look at “versions” for the file, though, it includes the full version list of the old name, and the previous version shows the old name (see below)

Version 0+

Path: httpd/test_move.file

Version 2

Path: httpd/iw-bin/object_browser_callout.cgi

Version 1

Path: httpd/iw-bin/object_browser_callout.cgi

this behaviour is applied identically for moves and renames, since TS treats a rename as a move…

for some reason, though, it doesn't seem to apply the comment on a 1st rename of a directory? but files are good to go...

so in summary, just look at the last file comment and see if it matches "^[moved to", otherwise it should be a delete instead of a move/rename...

cheers,
-Rori

Migrateduser

Rori - Great suggestion! I see exactly what you're talking about. This would work perfectly; however, at the risk of asking a dumb question...How do I return a file's "Comment" attribute from the command-line? I searched the forum and RTFM'd but no luck. “Iwattrib <file path> label” or “Iwattrib <file path> taglabel” on a moved/renamed file doesn’t return anything.

Fish - Yep, you hit the nail on the head. We've already implemented a custom menu item for "Delete", which invokes a workflow and carries the delete through the entire lifecycle. All of the "ghost" deletes are remnants from the pre-custom-menu-item days, and now I'm trying to clean them up.

Dan Pike
Senior Consultant
Strategic Solutions Northwest
dpike@ssnwllc.com

Migrateduser

not sure there is a CLT for getting the file comments Smiley Sad

any chance you're already using SOAP calls?

we're using the function getFileRevisionHistory in FileService.pm, and pull off the first returned value as the last comment...

if you've never used SOAP before, it's got a bit of a learning curve, up to you if you think it's worth your time, given that you said this is essentially a "one time cleanup" now that you have the custom menu item...

hope that helps,
-Rori

Migrateduser

Unfortunately no, we're not currently using SOAP. And you're right, it's probably not worth the effort just for doing cleanup.

Anyway...thanks for the help. I've submitted the case to IW Support. If there's a CLT solution, I'll be sure to close the loop and post it here.

Dan Pike
Senior Consultant
Strategic Solutions Northwest
dpike@ssnwllc.com

Migrateduser

good luck...if there's not a CLT way to do this, you can always file a Feature Request to get one...not very helpful for your short-term need, but might be useful to you (or others) in the future...

cheers,
-Rori

shanon

you can use CSSDK -- you can do it with a local client (JNDI) or SOAP. it's not too tough if you know java. if you want to do it all in perl, not sure.


..from CSClient's JavaDoc:

public CSFile getCorrespondingFile()
                            throws CSAuthorizationException,
                                   CSObjectNotFoundException,
                                   CSReadOnlyFileSystemException,
                                   CSExpiredSessionException,
                                   CSRemoteException,
                                   CSException
Gets the corresponding hole of the file if the file 
was created due to a rename or a move operation.
If called on a hole, the method returns the corresponding file.

Returns:
the file as a CSFile object, 
null if the file does not have a corresponding hole/file.

Throws:
CSAuthorizationException - if the user is not authorized to perform this operation
CSObjectNotFoundException - if the server cannot find this hole
CSReadOnlyFileSystemException - if the store is frozen
CSExpiredSessionException - if the user's session has expired
CSRemoteException - if the ContentServices SOAP or 
  JNI server has an error and cannot return the requested data
CSException - if the server cannot perform this 
  operation for any other reason

// how i'd get at it -- i have NOT compiled this...

// should be IWHOME/cssdk/cssdk.cfg
String configFilePath = "d:/iw-home/cssdk/cssdk.cfg";
Properties localProperties = new Properties();
       localProperties.setProperty("cssdk.cfg.path", configFilePath);
       CSLocalFactory localFactory=CSLocalFactory.getFactory(localProperties);

// this way if you've got a password.
       CSClient client=localFactory.getClient("me","master","secret",
                  locale.getDefault(),"TeamSite","TSServer");

// this way if you don't ( this only works on localhost )
//   CSClient client = localFactory.getClientForTrustedUser(
                                "user","master",Locale.US,"TeamSite",null);

// after you've got the client, you're home free...

String vpath = "/default/main/abranch/WORKAREA/wa/docs/afile.doc";

CSFile file = (CSFile)client.getFile(new CSVPath(vpath));
if( file != null )
{
  CSFile deletedFromMoveOrRename = file.getCorrespondingFile();
  if( deletedFromMoveOrRename != null )
  {
    // file was renamed.
  }
  else
  {
    // file was deleted.
  }
}

-shanon.
--------------------------
Sr. Solutions Engineer
shanon at interwoven dot com

Migrateduser

Thanks Shanon. Kailash also confirmed that the only way to accomplish this is through the CSSDK. I have filed a feature request for this to be available from a CLT.

Thanks to all for your responses.

Dan Pike
Senior Consultant
Strategic Solutions Northwest
dpike@ssnwllc.com