How is a UCS sound-effects filename built (CatID, FXName, CreatorID, SourceID, UserData), which fields are required, and what do open tools say about the separators?
Two independent open tools describe the same layout, CatID_FXName_CreatorID_SourceID_UserData, with the underscore as the block separator. They disagree on strictness: ucsrename (README) calls CatID, FXName, CreatorID and SourceID required with UserData optional, while ucs-tools (code docstring) says only a valid CatID at the head is a hard requirement. Neither is the UCS specification; the official filename text was not reachable. ucs-tools additionally documents optional '-UserCategory' after CatID and 'VendorCategory-' before FXName.
Two independent open tools describe the same layout, CatID_FXName_CreatorID_SourceID_UserData, with the underscore as the block separator. They disagree on strictness: ucsrename (README) calls CatID, FXName, CreatorID and SourceID required with UserData optional, while ucs-tools (code docstring) says only a valid CatID at the head is a hard requirement. Neither is the UCS specification; the official filename text was not reachable. ucs-tools additionally documents optional '-UserCategory' after CatID and 'VendorCategory-' before FXName.
Curator qualifications: With the vendor reproduction of the 8.2.1 text (JamSoft: CatID 'is the only requirement'; the rest 'completely optional'), the tool conflict resolves in favour of ucs-tools' reading. ucsrename's 'four required fields' is stricter than the convention as reproduced. Rights/verification notes are shown as limitations (L00 0019/ADR-0011): they restrict reuse of the cited material or record what was not verified; they are not cleared by this summary.
Limitations: [ambiguous] Resolution rests on a secondary vendor text; official document (Dropbox release archive) unread; item-level hold for primary confirmation.
Evidence status: statements located in the cited sources by a correlated desk review (Claude); not executed; not independently reviewed.
Structured fields
{
"citations": [
{
"url": "https://github.com/brettbuddin/ucsrename/tree/9fa454378d50076edc67370ce56f60b3bbf9c43a",
"note": "work/jamsoft.html JamSoft SampleSort UCS support page (implements 8.2.1, January 2024)"
},
{
"url": "https://github.com/jmrsound/ucs-tools/tree/2e307eb9aa4743a7a666426a9f70dcd08d393b40",
"note": "work/jamsoft.html JamSoft SampleSort UCS support page (implements 8.2.1, January 2024)"
},
{
"url": "https://universalcategorysystem.com/",
"note": "work/jamsoft.html JamSoft SampleSort UCS support page (implements 8.2.1, January 2024)"
}
]
}Evidence claims
- [sourced_fact] Two independent open tools describe the same layout, CatID_FXName_CreatorID_SourceID_UserData, with the underscore as the block separator. They disagree on strictness: ucsrename (README) calls CatID, FXName, CreatorID and SourceID required with UserData optional, while ucs-tools (code docstring) says only a valid CatID at the head is a hard requirement. Neither is the UCS specification; the official filename text was not reachable. ucs-tools additionally documents optional '-UserCategory' after CatID and 'VendorCategory-' before FXName. · locator: work/jamsoft.html JamSoft SampleSort UCS support page (implements 8.2.1, January 2024) source
Rights
| component | license | hosting | redistribution | modification | training | Evidence and notes |
|---|---|---|---|---|---|---|
| documentation | unknown | permitted | permitted | unknown | unknown | Applies to this original summary only, not to the cited sources. |