Store workfiles information in the DB

[mkolar]

Is your feature request related to a problem? Please describe. Workfiles are currently completely untracked in avalon. This is not a problem from production standpoint, however as we are looking at implementation of a more robust remote workflow management with file sync in the background, but also other, more minor issue. it is becoming clear that we should at the very least be aware of what workfiles exists and deal with them accordingly.

Describe the solution you'd like We could store info about every file that passed through workfiles app in the DB. I imagine we'd simply use rootless path to the file as it's ID, as that by definition must be unique. This would then allow us to store metadata like which site it is available in, better commenting and artist notes on the files and better controls over storage requirements when working remotely.

Additional context Of course this whole thing bring various questions to the light of day. A few I can think of:

• What about potential auxiliary files that might be stored in the the work folder and loaded into the workfile, like unpublished references, textures and so on? tracking all of them might be an overkill, not tracking any, might make the workfile tracking a potentially useless.
• Should we maybe crawl work folder everytime we open workfiles and catch any files in there, to log them in the DB?

[mkolar]

Agent Milan Kolar linked Freshdesk ticket 34 for this issue.

[mkolar]

Some context related to this from client ticket: Is it possible to add a comment to a work file without it beeing added to the filename? It would be great if the comment would be visible in the work file window. Like the comments for published assets.

[create-issue-branch[bot]]

Branch feature/653-store-workfiles-information-in-the-db created!