Setting dates and ownership on nodes

Hello,

In EWS is there a way, once you create an object, to change its ownership, its owner group, and things like its creation and modify date (need these for regulatory compliance). So far, I don't see a way to do this. I thought perhaps the Node object's features property might do it, but when you create an object using CreateFolder or CreateDocument, these are empty. Also, in the document creation, when I set a different create date in the FileAtts object, the creation call didn't seem to respect it. BTW this is all in CS 10 update 10.

Could someone advise the correct (i.e. supported) way to modify ownership, create dates, etc on a newly created object?

Thanks in advance

-Hugh

Find more posts tagged with

Comments

Kyle_Swidrovich

I may be mistaken, but I think even in LAPI, this was not possible.

There was a defined set of metadata fields that could not be set by the client. I’m pretty sure the create/modify dates were a part of that set.

I’m not sure if this changed with web services.

@Jason?

Hugh_Ferguson

If one uses Object Importer, one is allowed to specify creation and modify dates that are different from the date of import (whether it actually works or not is another story, but you are allowed to specify these in the OI ICF). For many clients, this is very important from an audit perspective (they wish to preserve the document's original creation date and make it appear that Content Server was the repository all along, all while preserving the audit trail).

I have advised my client that in some instances, the intelligent thing may be to have a legacy category that preserves information such as the original create date, and perhaps each modify date that they have but setting the owner and owner group is something they will need to be able to do as well.

I'm going to have a look at the Service object in the DocManService Ospace to see if I can shed a bit more light.

-Hugh

Jason_Smith

You cannot change the creation/modify dates of the node. These properties are set/updated automatically when creating or modifying a node.

You can change ownership though. Take a look at the AddNodeRight(), GetNodeRights(), RemoveNodeRight(), SetNodeRights(), and UpdateNodeRight() calls.

You can also see the current user's permissions on a node by looking at the Permissions property of a Node object.

Jason_Smith

If you want to preserve the original create/modify dates of a document, I think you can set these properties on the Version object, just not the Node object.

Hugh_Ferguson

I was curious so I did a little test with Object Importer. I decided to test the notion that the create date cannot be set to something other than the current date (maybe that's not what you meant, but anyway...). Using Object Importer, I can create a folder (a versionless node) and set its create date to a date well before the current date. In this particular case, I created the folder on June 21st 2013 and set the create date to be Jan 1st 2012.

So you can't do this with a node create call in Web services? I'm asking because my clients are going to ask.

-Hugh

Chris_Shiell

There are differences in business logic between WebServices, Object Importer, WebUI, LAPI, XML Importer/Exporter. This is partially intentionally and partially due to the fact that they do not share a common business layer.

While we know there are difference there is no current plan to align these. These differences need to be logged and evaluated on a case-by-case basis.

Hugh_Ferguson

These methods may not share a common business layer but they all call $LLIAPI.Node.NodeCreate() to create the object.

For partners who wish to do data migration, what is the Open Text recommended technology to use? We had been leaning towards Web Services due to the fact the OI has a 1000 item per file limitation which can become an issue when your migration is > 1 million objects.

I know that OTIC makes use of the web services layer. Does it use the core Web Services or does it append its own services?

-Hugh

Kyle_Swidrovich

As of today, I'd say go with web services. I'm not familiar with the OTIC integration method.