AY-2212_Make project code not unique

[ynbot]

Please describe the enhancement you have in mind and explain what the current shortcomings are?

Another quick question, is there a usage difference or distinction between setting the project name (not unique) and the project code (unique) in ftrack? For example, the project code would be the unique identifier (ex. used as root project folder etc.) vs. the project name is used to display and is also part of the published file names?
11 replies

Milan Kolar:incoming_envelope: 5 hours ago
at the moment Project name must be unique and project code doesn't from OP persperctive. They can both be used as part of filenames though, that depends purely on templates.

Milan Kolar:incoming_envelope: 5 hours ago
Really the code is there just to have something shorte

client 5 hours ago
Ok, good to know that this is configurable.

client 5 hours ago
But shouldn't the code be unique, at least from ftrack 's point of view? I can not have 2 projects with the same code but I can have multiple projects with the same name. If I set the project code to a taken code I get project name must be unique (very confusing as it is the code). ftrack made a mess here (same with name and full name), but from this the name is the display name (anything) vs. the code is unique. What makes it more confusing is ftrack UI vs API where code (UI) is the name (API) and the name (UI) is the full_name (API).

Milan Kolar:incoming_envelope: 4 hours ago
To be honest that is one of my pet pieves in ftrack. They call things differently in the code and in the UI.

Milan Kolar:incoming_envelope: 4 hours ago
OpenPype mapping to that is a bit different. Project name has to be unique in OpenPype, without exceptions. Project code though is just and attribute of the project document so it doesn't matter to us if it's not unique>
That being said, due to working with ftrack on your site, You're forced to have both of them unique. Project because of OpenPype restriction and Code due to ftrack restriction.

Milan Kolar:incoming_envelope: 4 hours ago
The project name is directly related to a root project folder for us as well, so that's one of the reasons why it's uniques, it's alos a colleciton in Mongo.

client 1 hour ago
Ok, but this means we can not have a short form that may not be unique over time. Ideally, we would like to have a short name for displays, burnins and file names but the root folder or project uniqueness would be a long name. To avoid clashes with short names (2-3 characters). Or would we have to set the name and code the same and have a third attribute like display name or so? Maybe makes it more confusing.

Milan Kolar:incoming_envelope: 1 hour ago
Well that's unfortunatelly a bit of an ftrack issue at the moment. That being said. I'd say it's reasonable for us to decouple that attribute from ftrack completely and use custom attr as you suggested. That would allow non-unique project codes, quite easily
heavy_tick
+1
heavy plussymbol

New

client < 1 minute ago
Yes, that sounds good. Would be great to be able to set a non-unique short/display name.

Milan Kolar:incoming_envelope: < 1 minute ago
Making a ticket for that, shouldn't take long.

How would you imagine the implementation of the enhancemenent?

No response

Describe alternatives you've considered:

No response

Additional context:

()
(might be a private channel)

This issue was automatically created from Clickup ticket AY-2212