Library exhibit packs need accession notes without overloading display or shading attributes. Where should those notes go?
Select an answer to reveal the explanation.
Short Explanation
Accession notes are catalog text, not roughness or point counts. Park them in customData so display attributes stay honest. Materials should look like exhibits, not filing cabinets.
Full Explanation
Library exhibit packs need accession notes that must not overload display or shading attributes. Those notes belong in customData (custom metadata) separate from geometric display attributes so catalog text remains queryable while materials continue to mean materials. Separating civic descriptive metadata from geometric attributes preserves both curation and visual fidelity in the twin and in DCC round-trips.
Pushing notes into displayColor and roughness makes catalog text drive shading and destroys look-dev. Encoding notes into point counts on exhibit meshes abuses topology metrics and breaks under decimation. Smuggling notes through camera aperture as a side channel ties curation to a camera prim and fails for deliveries that omit cameras.
Exam caveat: long-form prose sometimes lives in external CMS with only an accession ID in USD; when notes are authored in-USD, customData is still the correct separation from display/shade attributes. Prefer string fields under a documented customData key.
Operational check: place accession notes in customData on exhibit roots, confirm displayColor/roughness unchanged in the viewer, export a catalog CSV from customData, and reject any importer/exporter that copies notes into material channels.