Jump to content

Working with Tags


Remus Avram

Recommended Posts

Hello F-Track,

 

we would like to have a tag system in f-track.

The workflow should look like this:

Project manager defines a couple of tags per project -> assign the tags to the shots -> filter shots by clicking one tag

 

Do you think this could be possible to be implemented?

Or how could be the best practice to do this?

 

Best,

Remus

Link to comment
Share on other sites

Hi Remus,
 
You can add a custom enumerator attribute with your own options in System settings > Advanced > Custom attributes, and then filter the spreadsheet by any of those options. I did a quick screen recording showing this.

 

As an option to adding the attribute globally you can add it per project by clicking the cog wheel above the main spreadsheet on a project and select Attributes > Create attribute. Attributes added to the spreadsheet can also be saved into the view and shared across the studio.

 
If you want more control over the options in the drop down, you can also use dynamic enumerators which populates the drop down through a server script. This solution is especially useful when you want options to be available from another system, or options that differs over time.
 
We will look into more implemented ways to tag objects in the future.
 
Let me know if you have any questions on these solutions.
 
Thanks,
 
Mattias

Link to comment
Share on other sites

Hello Mattias,

 

thanks for your answer and for the video!

 

I was looking into custom enumerator attribute, but we would like to add more values during the project by production/coordinators. Unfortunately they don't have access to system settings to do that.

 

Best,

Remus

Link to comment
Share on other sites

  • 11 months later...

The best solution is still an enumerator / dynamic enumerator to handle a tag like system. With a dynamic enumerator you can populate the available values from a remote python script. In theory you can have a custom attribute "Available tags" on the project with a comma separated list of tags, then having the dynamic enumerator display those as options in a "Tag" custom attribute dropdown.

Link to comment
Share on other sites

  • 2 months later...
  • 3 weeks later...

hey, juste voted +1

 

The important thing is the way you'll display it ( with colors/icons)
typically we would use tags to mark different achievements of a version to bring more accurate status than just the simple status( that has no history)
for example, we could store the info that a version was approved by supervisor and boss but waiting for approval of client, and was delivered to editing (each of the things would be a tag).

today we can make it with custom attributes but the way it can be displayed makes it barely readable at a glance.

Link to comment
Share on other sites

  • 1 month later...
  • 4 months later...
  • 1 month later...
  • 8 months later...

I'm digging up this old thread as well.

We are making a new asset library and wanna tag versions with things like maya,maya_2017,vray,vray_3.5,character,fur,projectname and then be able to do a reasonably fast query against this through the API.

Would modifying a custom enum attribute and add more values as we go along still be the best or only option? Feels like that attribute would get pretty crazy pretty quickly.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...