PDA

View Full Version : RBA file naming convention


mmorlan
09-09-2010, 07:10 PM
Would like to talk to users who have adopted a file naming convention for their customers to follow that allows them to utilize RBA to its fullest.

NDanger
03-05-2013, 04:25 PM
What would you like to know?

mark_jetzer
03-05-2013, 07:19 PM
Glad to share anything we have learned.

NDanger
03-12-2013, 01:42 PM
Here is a screen shot of our filenaming conventions...

They take place at the end of filename preceded by an _(underscore) prior to the extension...

ie <filename>_LR.pdf

denotes a different process plan that bypasses Lo resolution failure...

suec@foresightgroup.net
03-15-2013, 03:34 PM
How acceptable were the customers to adapting these naming conventions? Do you offer incentives to customers that work with you to achieve an automated workflow.

What happens if they inadvertently name the file wrong and it picks up the wrong process, who is responsible?

Can you give us some background on those logistics.

Thanks, Sue

NDanger
03-15-2013, 03:51 PM
Actually, they are very receptive.

I just tell them that if they want to print PMS, they need to include this in the name.

A lot of times with lorez, InSite will flag and will either rename or call and ask to identify. If they don't want to get the 'proverbial' call @ 0200 about something that looks lorez, then label the file this way. This shifts the burden to the Customer with them agreeing that the files is bad.

We are not involved in pricing, so nothing is ever mentioned.

With processing thousands of pages a month, it has helped us out tremendously. I even set up a rule that when the Customer selects Reject, it auto-deletes in 5 seconds. This was always an issue that when they uploaded a page with an _lr, it wouldn't delete the original because of the name change. Then thru the pipeline, word would come down for us to delete...

NDanger
03-15-2013, 05:05 PM
How acceptable were the customers to adapting these naming conventions? Do you offer incentives to customers that work with you to achieve an automated workflow.

What happens if they inadvertently name the file wrong and it picks up the wrong process, who is responsible?

Can you give us some background on those logistics.

Thanks, Sue

Actually the filenaming possibilities are far enough apart, that this isn't an issue as far using the wrong process plan. The bigger problem is to get them to name it correctly...:mad: