Blender Kitsu: New Assset Tagging System #286

Nick Alberelli · 2024-04-30T03:08:44+02:00

Nick Alberelli commented

2024-04-30 03:08:44 +02:00

What's Changed?

Add new subpanel and operator to upload filepath & collection to Kitsu Asset Metadata
If Asset Pipeline Add-On is enabled user is prompted to confirm they want to use the latest publish as Asset
Shot Builder looks for filepath and collection name with in Kitsu Asset Metadata

Updated UI

Metadata in Kitsu Server

TODO

Add Logic for published files (maybe this should exist in the Asset Pipeline add-on instead seems weird for here)
Add Images to docs

## What's Changed? - Add new subpanel and operator to upload filepath & collection to Kitsu Asset Metadata - If Asset Pipeline Add-On is enabled user is prompted to confirm they want to use the latest publish as Asset - Shot Builder looks for filepath and collection name with in Kitsu Asset Metadata ## Updated UI ![image](/attachments/0187c5b4-2626-45ab-9db7-af969682985a) ## Metadata in Kitsu Server ![image](/attachments/3d4b0f84-6c4d-4d34-8f8a-e40e39fb6d45) ## TODO - [x] Add Logic for published files (maybe this should exist in the Asset Pipeline add-on instead seems weird for here) - [x] Add Images to docs

image.png

28 KiB

image.png

21 KiB

image.png

10 KiB

image.png

25 KiB

image.png

29 KiB

Nick Alberelli added 5 commits 2024-04-30 03:08:51 +02:00

Add Operator to Tag Kitsu Asset with Filepath and Asset Name c9979f52ca

Use Filepath relative to project in Operator to Tag Kitsu Asset b26369b7e6

Use Kitsu Asset Metadata in Shot Builder 1890693be3

Use Constants to Store Asset Metadata Keys f9c7a50d9f

Update Documentation 2e2ecf1531

Nick Alberelli commented

2024-04-30 03:14:41 +02:00

@fsiddi The only thing missing in this PR is the logic for published files, so if you are in a working file

So the use case is for an asset with the following structure

rain/
├── rain-modeling.blend # User opens this file
├── rain-rigging.blend
├── rain-shading.blend
└── publish/
    └── rain-v001.blend # Wants to mark this file as Asset

The question is how do we find the latest publish, do we assume the publish folder name and version conventions exactly match what we use in the Asset Pipeline Add-On, but put that logic in the Kitsu Add-On (creates redudant logic for finding publish in Kitsu and Asset add-ons)
Just call this operator from the Asset Pipeline Add-On (if Kitsu is enabled) which already has logic to find the latest publish, (I prefer this one)

@fsiddi The only thing missing in this PR is the logic for published files, so if you are in a working file So the use case is for an asset with the following structure ```bash rain/ ├── rain-modeling.blend # User opens this file ├── rain-rigging.blend ├── rain-shading.blend └── publish/ └── rain-v001.blend # Wants to mark this file as Asset ``` 1. The question is how do we find the latest publish, do we assume the publish folder name and version conventions exactly match what we use in the Asset Pipeline Add-On, but put that logic in the Kitsu Add-On (creates redudant logic for finding publish in Kitsu and Asset add-ons) 2. Just call this operator from the Asset Pipeline Add-On (if Kitsu is enabled) which already has logic to find the latest publish, (I prefer this one)

Francesco Siddi commented

2024-04-30 09:22:06 +02:00

Hi, thanks for the update on this. Option 2 is ok.
What happens if we don't use the asset pipeline? Is it possible to tag assets from any file?

Hi, thanks for the update on this. Option 2 is ok. What happens if we don't use the asset pipeline? Is it possible to tag assets from any file?

Nick Alberelli commented

2024-04-30 16:28:20 +02:00

@fsiddi Yes any file you open can be tagged as an Asset, that part of the system already works.

The only outstanding feature was how do we tag Published files from a working file, I will implement it in in the style of option 2.

@fsiddi Yes any file you open can be tagged as an Asset, that part of the system already works. The only outstanding feature was how do we tag Published files from a working file, I will implement it in in the style of option 2.

Nick Alberelli commented

2024-04-30 18:15:42 +02:00

@fsiddi After a second look, because this process requires the user to select a Kitsu context we should go with option 1 instead,

I will reach into the Asset Pipeline Add-On from the Kitsu add-on to get the logic for finding the latest publish to make the redudant code a non-issue.

So its more like option 2 but in reverse because the Operator will live in / UI will be drawn by the Kitsu Add-On, but there will not be duplicate code between the add-ons

@fsiddi After a second look, because this process requires the user to select a Kitsu context we should go with option 1 instead, I will reach into the Asset Pipeline Add-On from the Kitsu add-on to get the logic for finding the latest publish to make the redudant code a non-issue. So its more like option 2 but in reverse because the Operator will live in / UI will be drawn by the Kitsu Add-On, but there will not be duplicate code between the add-ons

👍 1

Nick Alberelli added 1 commit 2024-04-30 20:50:35 +02:00

Add Optional Feature to Publish Asset Pipeline Files 143b4d80ff

Nick Alberelli added 2 commits 2024-04-30 21:04:57 +02:00

Add Images to Docs 6e8acfc777

Add Check if Asset is using Asset Pipeline 30e864f525

Nick Alberelli merged commit ee7e3b9d8e into main

2024-04-30 21:43:07 +02:00

Nick Alberelli deleted branch feature/asset-tagging

2024-04-30 21:43:08 +02:00

Nick Alberelli referenced this issue from a commit

2024-04-30 21:43:09 +02:00