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; } } }

File rename - ECM Connector

iwTech

Hi ,

I am using ECM Connector (ver 2) to import files from mediabin (ver 4.5.3)
to teamsite (ver 6.7.1.0) But before downloading the file to TS server ,
I want to rename the selected File ( The selected file grayed out),

How I can Achieve this ?

Thanks
Vin

Find more posts tagged with

Comments

Bill Klish

Did you try using the Open in MediaBin option visibile in the properties view of the asset inside of the ECM connector?

iwTech

Thanks ,
I tried this ,but it will rename the asset in mediaBin.
My requirement , download the file to TS with a new name ,
but the orginal asset remains the same in mediaBin
I mean the same asset with different name in mediaBin and TS

Vin

cliff1

If you are using the "immediate import" (file imported as soon as user closes the selection dialog), there is no way to change the name of the imported file -- by the time the user sees the selection dialog in your screenshot, the file will have already been downloaded.

If you are using a presentation template to trigger the import (deferred import), you can define the area-relative-path (including filename) of the imported asset. You can use whatever logic you desire to construct the path (including reading some of the DCR fields) The perldoc in the import perl module has examples of all of the arguments control.

The "selection" field in the form is designed to give the user some feedback that the correct file was selected. I'm fairly sure that changing it (or allowing the user to change it) won't change the default presentation import behavior. If you want the end user to control the name (which may be a bad idea because of filename collisions, etc.), you can probably remove the read-only flag via formapi and then use the field when constructing the path in your PT.

I hope this helps.

iwTech

Thanks for the detailed explanation.
Vin

the_greg

Related query:

Is it possible to not have the retrieval task name appended to the filename? Am I missing something simple?

iwTech

Please explain your situation little more detailed .
We implemented the rename by using the methods explained by [color=black]Cliff McBride[/color]
-Vin

cliff1

If you use the "immediate" import option, the ECM Connector choose the filename. We wanted to make sure it was unique so we append the retrieval task information. If you download a different rendition of the same file we didn't want a collision situation -- several customers will download various size renditions for the same file, so this is a real situation.

If you use the "deferred" import, you have complete control of the filename and location. Your presentation template can have whatever logic is appropriate to build an area-relative-path for the imported file.

I assume the previous post is talking about renaming the file after it is downloaded, which you can do. Your question led me to believe you want to change the name before it is downloaded.

the_greg

If you use the "immediate" import option, the ECM Connector choose the filename. We wanted to make sure it was unique so we append the retrieval task information. If you download a different rendition of the same file we didn't want a collision situation -- several customers will download various size renditions for the same file, so this is a real situation.
.

I think this is the information I was looking for. Now I know why this you have the ECM connector choose the filename in the immediate import, and am I to understand that this functionality cannot be switched off? Ideally we don't want to have to make the user have to manually rename the file ( removing the task name) but it looks like that's what we're looking at f we wnat to use the immediate import function.

Thanks for the information

cliff1

There is no way to switch off the auto-naming behavior in ecm connector for direct import. If you rename the file, you should make sure the path inside of the DCR is also updated (assuming you are using the dialog-param to save the path). It may be less error prone to write a workflow task to handle the renaming.

If this could be designed to meet your exact needs, would you want the ecmconnector dialog window to prompt the user for the teamsite filename and path?

Out of curiosity, why does the filename matter? Generally speaking the imported file(s) is referenced from a webpage and the href can provide a human readable description instead of relying on the filename.

Adam Stoller

There is no way to switch off the auto-naming behavior in ecm connector for direct import. If you rename the file, you should make sure the path inside of the DCR is also updated (assuming you are using the dialog-param to save the path). It may be less error prone to write a workflow task to handle the renaming.

If this could be designed to meet your exact needs, would you want the ecmconnector dialog window to prompt the user for the teamsite filename and path?

Out of curiosity, why does the filename matter? Generally speaking the imported file(s) is referenced from a webpage and the href can provide a human readable description instead of relying on the filename.

(This is not one of the forums I usually frequent - hence I'm about a month late in adding my $0.02)

I fully understand the reason for augmenting the base filename with information about how it was transformed, etc. so that one person's fetching of a particular image for one purpose doesn't mess up someone else's fetching of the same image for another purpose... but I'm a bit concerned about the formatting of that information that gets imbedded into the filename.

E.g.:

some_img_name -- JPG (320x0).jpg

issue and want to find out if there is (or soon will be) a means of tweaking this.

cliff1

Hi Adam,

Thanks for the suggestion, I'll file a Feature Request but no promises about when we can make this available (TS 6.7.2 is in beta and the branch is tightly controlled).

We haven't run into the situation yet where the auto-generated names are causing problems, but I understand your point and agree it could happen (or at a minimum violate naming standards). If you want fine grained control with the current solution, you have two options:

1) Use a PT: you can generate the filename (and area relative path) for ECM Connector in your PT. We call this "deferred" import because the download of the MB rendition happens when the PT is executed instead of when the user selects the file.

2) Workflow programming (I'm sure you already thought of this). This is a little bit of a pain since you have to update the DCR data to point to the renamed file; but should be trivial for a rock star (how does the comment about flattery go...).

Cheers,
Cliff

Adam Stoller

Hi Adam,

Thanks for the suggestion, I'll file a Feature Request but no promises about when we can make this available (TS 6.7.2 is in beta and the branch is tightly controlled).

We haven't run into the situation yet where the auto-generated names are causing problems, but I understand your point and agree it could happen (or at a minimum violate naming standards). If you want fine grained control with the current solution, you have two options:

1) Use a PT: you can generate the filename (and area relative path) for ECM Connector in your PT. We call this "deferred" import because the download of the MB rendition happens when the PT is executed instead of when the user selects the file.

While that might work in most cases - we have at least one DCT for which there is no PT, i.e.: content goes directly into a database. Besides, in general, I like the idea of "immediate" importing (though I can see arguments for both sides)

2) Workflow programming (I'm sure you already thought of this). This is a little bit of a pain since you have to update the DCR data to point to the renamed file; but should be trivial for a rock star (how does the comment about flattery go...).

Cheers,
Cliff

Ah, flattery will get you far ;-) But in this case, I don't have the time to try to do that. Although it is a thought, if I should happen to become involved with this kind of integration effort in the future, but hopefully by then there'll be an SP that provides the functionality :-).

Thanks for the response...