Asset Management Terminology #82015
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#82015
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Motivation
Current terminology for the Asset Browser isn't complete and not very well thought out. It's important to clearly define the terminology and apply it consistently. This is needed for a helpful UI language, but also non-ambiguous developer documentation (e.g. API docs for asset manager systems).
It would further be nice to have a language scheme to take names from, rather than a bunch of loose, often rather technical terms (proposal at the end).
Definitions
These are our own definitions for the context of Blender asset management.
Missing Terms
** "Preset" (assets that are applied, like brushes, matcaps or poses)
** "Primitive" (assets that are appended or linked, like objects, images or node groups)
[...]
UI Language Scheme Proposal
A simple metaphor for asset browsing is a library visit. Let's brainstorm how we could use that as a naming scheme:
Some items may go too far, this is really just an idea.
i) The term Library is already used in Blender (the source file of linked data-blocks). Could this be confusing? In a sense, asset repositories are also the source "files" of assets, so maybe just Asset Libraryis reasonable. If in doubt we can differentiate between Data-block Library and Asset Library
ii) No existing term. This list is generated by the asset manager system and is what the Asset Browser needs to display a list of items that represent the assets.
Added subscriber: @JulianEisel
Added subscriber: @Beryesa
Added subscriber: @lichtwerk
Added subscriber: @BukeBeyond
I would suggest "Mark as Asset" and the symmetric "Unmark as Asset". The current term "Mark Asset" sounds like there is already an asset. "Clear Asset" sounds like deleting the contents of an asset, very misleading...
Another suggestion is "Declare Asset" & "Undeclare Asset".
If there was a way to show a checkmark, it would simplify the bipolar phrases to just one.
Added subscriber: @Harley
The more I think about it “Clear” is problematic. It is not just a confusion with removal and deletion. It is more that “Clear” is generally not a negative state but a positive one, one that does not have restrictions, regulation, or obstacles in the way. A runway is clear for take off. A document might be cleared for publication. So in this case “ Clear Asset” might certainly be that you have approved its availability, not the opposite.
Rather than struggle with terminology to describe the action of changing the state of the object, it might be more straightforward to simply list the states. For example a submenu called “Asset Status” or “Asset Library” which opens to show you that this one is “Not an Asset”, next to other items like “Shared Asset”, “Public”, “Private”, Reserved, Hidden, Available, Disabled, or whatever.
I think we can close this now, the terminology is well established at this point. We went a bit in the direction of the proposed scheme, but not fully.
I'm also not the biggest fan of Mark Asset and Clear Asset, but for now we stick to it. At least it's not worth keeping this open just for that.
Thanks for the feedback everyone.