SuccessFactors Learning best practices for file naming conventions and version control

[Teresa_W]

Hello, 

I am searching for best practices related to file naming conventions and versioning in SuccessFactors Learning. Is there any type of documentation that addresses this information or is this mostly left up to users to determine for their own business needs?

Thanks! 

[Kristian_Unell]

Hi Teresa,

We have defined a strict naming convention for items, content objects that work fine for us.

All objects have the same logic: ABC-1234

Each unit in our company has their own "three letter acronym": eg LGL for Legal department, MKT, SLS, HRD, CPL. 

Then each unit is free to set up a range for their courses. For the LGL courses, we use range 0000-0999 for International law, the above 1000 for each country law...

Content objects are the same as the ItemID with an appropriate suffix:

LGL-1001-FR-01  here is for a content object in French, and we simply increment the numbers if there are multiple content objects in the same item. And versions would be LGL-1001-FR-01.1.

Since the folder on iContent uses there content object name, here we are safe to avoid any overwrite. Within the folder, we don't impose anything in the naming convention. We are on SF LMS now since 8 years, and have never cleaned up our iContent server, something I think about it, and then I prefer thinking about any other problem I would actually be able to solve... 

And in the same logic, we use the ItemID for the curricula and assignments profiles, as except for the New Hire stuff, most curricula we assign contain only one item.

This whole logic works well for use as:

• it is easy to retrieve any relationship between objects.
• each training unit has their own course object names.

We use a single domain for all admins, and since our LMS admins usually succeed in using this naming convention, life is great !

HTH,

Kris

[JAndreoni]

Kris, I agree with your naming convention! The 3 letter acronyms work very well and help to identify either a department, category or function. As you've suggested, LGL for legal, FIN for finance, SAF for safety, ONB for onboarding. LMS uses many entities together such as a class, content object, item, program, quiz so it's helpful when entities can be correlated or banded together. It makes it easier for everyone. I've also seen where each year a course is updated from the previous year. Rather than reversion the course, the course was copied and renamed the same name, but by year. Example, LGL 101 2024, LGL 101 2025 and so forth. When versioning is used, it generally starts with 1 and goes up in increments, version 1, version 2, version 3. It's always best to add comments, author, contact info as well.

[PL1]

@Teresa_W, trying to contribute, if you'd like to review the auto-generated IDs for certain entities, here you can find additional details: Forcing System Generated IDs.

[subramaniiyer]

There is no best practices for naming conventions unless you have multiple Domains and restrictions So to keep the check ex A Company- AITEM,Aclass

Hope this helps