Please enable JavaScript.
Coggle requires JavaScript to display documents.
Challenges Integrating Nuxeo w/ TSS - Coggle Diagram
Challenges Integrating
Nuxeo w/ TSS
Project Number is not included in the current Nuxeo Payload to TSS :!!:
Coordination with the LPMs is needed
Staffing Options
Dedicated person or team
Requests go to a que that Team Leads manage and assign as appropriate
LPMs require an issue in Workfront
(Requests create issues &
drop in the que to be managed)
:!!:
Nuxeo may be able to systematically make the request
Context
Create and Send a tokenized link to the asset for Translation :!!:
Data Structure
Packages for TSS :!!:
Metadata Only
Metadata + Binaries
Grouping of assets to be sent
By Project, send the original asset with the Language set thus on return Nuxeo will use the request ID to reverse look-up the translation derivative to be updated
Asset Structure
Caption Files
Format of Relationship to a related asset
vs Attached file (Status quo)
Requirements
language of the asset
assets specify language explicitly
vs using a 2 letter language code
in the filename is risky
assets are uniquely identifiable
vs multiple attachments
can exist on an asset
problematic if the language is more complex
(script, country region)
versioning
Required when there are edits to the captions
identifying
assets is more efficiently & specific as a data source vs
an asset's attachment(s)
relationships
audio/video source
Derivative assets like articles
Language derivatives
related assets can be explicitly delineated
vs attachments
The filenames of attachments are unmanaged
and essentially a wildcard.
Expand the Track Schema
(otherwise, a track is just a label w/o
any referenceable/useful data)
Text Tracks as related assets
audio tracks as related assets
Language Production
Approved Languages
Opt-In Model
Leveraging Church TM and MT Only!
Metadata Only
Metadata & Binary
More visibility to the List of Approved Languages in Nuxeo
Funding
Project Funding
Overhead Translation Account?
Overhead Asset Management Account?