How "unique" is an autonamed DCR?

Hi,

We are using TeamSite 6.7 on Windows 2000.

Does anyone know how "unique" the unique DCR name is that is produced when one makes use of the dcr-autonaming="t" setting in templating.cfg?

Is it unique to the entire TeamSite installation? Or just to the workarea? Or just to the folder? Or just to that data type?

(The situation I am facing is that we have a large number of autonamed DCRs in a data folder, and would like to move some of them out to an archive folder because we have a script that loops through all the DCRs in that data folder, and we are starting to see some performance issues. However, we may need to bring some of those DCRs back into the data folder at some point. I'm concerned that if we move a DCR out, TeamSite might think it is ok to reuse that DCR name, which would hose us if we ever need to move the "old" dcr with that name back into the data folder).

Find more posts tagged with

Comments

Phanie

it depends on your autonaming criteria you follow. It would be nice if you enlist your autonaming convention being followed.

ISCBorisB

Hi,

We are using TeamSite 6.7 on Windows 2000.

Does anyone know how "unique" the unique DCR name is that is produced when one makes use of the dcr-autonaming="t" setting in templating.cfg?

Is it unique to the entire TeamSite installation? Or just to the workarea? Or just to the folder? Or just to that data type?

(The situation I am facing is that we have a large number of autonamed DCRs in a data folder, and would like to move some of them out to an archive folder because we have a script that loops through all the DCRs in that data folder, and we are starting to see some performance issues. However, we may need to bring some of those DCRs back into the data folder at some point. I'm concerned that if we move a DCR out, TeamSite might think it is ok to reuse that DCR name, which would hose us if we ever need to move the "old" dcr with that name back into the data folder).

You may want to double-check with IWOV Support. For what it's worth, my impression is that the name's suffix is some system-unique Id,
never to be reused regardless of Types, Submissions and whatnot. You probably know that you can create your own naming mechanism
using methods of IWNameFactory.

B80116

Thank you for the inputs.

We are using the default DCR name generation algorithm, which seems to be a date stamp consisting only of the hours and minutes appended to the day of the month (no month, no year), and also a single digit number which so far is always zero. This has me worried that indeed the system may re-use a DCR name if I move a DCR to a different folder.

I was not aware of the IWNameFactory.

I am going to look into using IWNameFactory to override the default algorithm with something which will not be duplicated, or at least much less likely to be duplicated.

Thank you again for your guidance.

Migrateduser

It should be pretty unique with respect to the naming convention as it uses the timestamp which I think is from the epoch time. So if two people don't save at the same time, you should be receiving different names. However, it might be difficult to distinguish the DCR from those names since all it is is iwDCR_timestamp.... It is better if you use the IWNameFactory.setAutoPathDCRGenerator(functionName) and have your functionName come up with a meaningful name.

Alyssa

Hi,

I'm using this auto naming function and if two users happen to save at the same time the number before the timestamp in incremented. so iwDCR0_281440 would become iwDCR1_281440.

A