Remus Avram Posted March 9, 2015 Report Share Posted March 9, 2015 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 More sharing options...
Mattias Seebergs Posted March 9, 2015 Report Share Posted March 9, 2015 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 More sharing options...
Remus Avram Posted March 9, 2015 Author Report Share Posted March 9, 2015 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 More sharing options...
Mattias Seebergs Posted March 10, 2015 Report Share Posted March 10, 2015 Hi Remus, If you were able to manage the attributes directly on the project, would that be a good solution? Or would you be adding new values very often so a tagging system would be more suitable? Mattias Link to comment Share on other sites More sharing options...
Remus Avram Posted March 13, 2015 Author Report Share Posted March 13, 2015 Hi Mattias, managing the 'available only on the respective project' attributes directly from the project could be a solution.But a tagging system would be more suitable for doing this. Thanks,Remus Link to comment Share on other sites More sharing options...
Remus Avram Posted March 2, 2016 Author Report Share Posted March 2, 2016 Hi guys, are there any updates regarding Tagging System? Best, Remus Link to comment Share on other sites More sharing options...
Mattias Lagergren Posted March 3, 2016 Report Share Posted March 3, 2016 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 More sharing options...
Fredrik Limsater Posted May 30, 2016 Report Share Posted May 30, 2016 Hello, vote for this feature on our public roadmap: https://trello.com/c/Ne1Kng0i Cheers, Fredrik Link to comment Share on other sites More sharing options...
pierre Posted June 15, 2016 Report Share Posted June 15, 2016 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 More sharing options...
Remus Avram Posted August 3, 2016 Author Report Share Posted August 3, 2016 Hi F-track team, I was just wandering if there are any updates regarding topic? Cheers Link to comment Share on other sites More sharing options...
Mattias Lagergren Posted August 4, 2016 Report Share Posted August 4, 2016 17 hours ago, Remus Avram said: I was just wandering if there are any updates regarding topic? Nothing major. We've however been discussing tags internally the last few days. It could potentially solve a few use-cases for us regarding Planning. Link to comment Share on other sites More sharing options...
Remus Avram Posted August 4, 2016 Author Report Share Posted August 4, 2016 Thank you Mattias for your update! I would be awesome to have it in place sometime Link to comment Share on other sites More sharing options...
Remus Avram Posted December 20, 2016 Author Report Share Posted December 20, 2016 Hi Mattias! Any updates regarding this topic? Link to comment Share on other sites More sharing options...
Mattias Lagergren Posted December 21, 2016 Report Share Posted December 21, 2016 Hi Remus, I'm afraid that I do not have any updates about this feature request. It is still something that we're considering to solve use-cases for our new Studio Overview planning tools - but no decisions has been made so far. Link to comment Share on other sites More sharing options...
Remus Avram Posted January 31, 2017 Author Report Share Posted January 31, 2017 Hi Mattias, from our point of you tags will solve a lot of problems. Right now we create a new custom attribute for every categorize which makes the Info View really complex. Production wants to tag shots, assets, sequence everytime differently and in any project different. Link to comment Share on other sites More sharing options...
Erik Posted October 19, 2017 Report Share Posted October 19, 2017 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 More sharing options...
Mattias Lagergren Posted October 23, 2017 Report Share Posted October 23, 2017 I'm afraid there are no updates that I can share regarding the support of tags. The described workarounds are still valid @Erik Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.