Dates in Project Naming Conventions

[KellyHa3]

Hi! My team is working on standardizing our project naming conventions. We're thinking of the following: 

CAMPAIGN_DELIVERABLE_ MMYY_DEPT_ REFERENCE 

For the dates, what do you typically do for your projects? The go-live date? The project conversion date?

Thanks!

[skyehansen]

asking out of curiosity -- why are you seeking to put a date into your project names, if you don't care which date you use? 

If it's just to distinguish between them, in cases where you have duplicate names, I would suggest making sure you use a date that never changes. For example, if your project go-live date frequently changes, your project owner might frequently forget to rename the project. So it might be better in that case to go with project conversion date, or even request date if it comes to that. Just one less thing to forget to do.

In order to help with the duplicate name thing, I'd also recommend you put the date first (e.g. YYMM_Campaign_etc.) so that users who are faced with similar-looking project names can immediately sort the names in a more helpful way.

[Kurt_Jones]

KellyHa3, we do Reference | Campaign | YYYY Deliverable.  So example, is 1234567 | Summer Binge | 2024 Paid Search #1.  We're not particular in the date but having the year info can help for reporting if you're wanting to see all work for a certain year.  The pipe made it a little easier to read according to our users so we stuck with it.

[Kiersten_K]

We do the following: custom project #_channel_go live date of campaign_name of campaign

Example: P240001_em_12-4_holiday_promo, P241005_dm_12-15_brand_mailer

The custom project number is generated using Fusion and the last 2 digits of the year are the first 2 numbers after the letter P.

We use these titles for our creative project file names and folders in our DAM system so we keep the naming pretty short and concise. We have acronyms for our marketing channels.