Typical Workflows for LVS-Enabled Solutions

LVS-enabled applications will necessarily vary in their use of specific API endpoints, according to their specific content and functionality requirements. However, there are some general patterns that you can follow when planning your solution.

Setting up and managing video content

1. To authorize your application to call LVS APIs, you must first generate an API token by using the Authentication endpoints + LVS credentials + tenant ID.
2. To generate new video content, use Discovery endpoints + video asset URLs to virtualize your assets to generate asset records within your LVS tenant's media library, and add asset-level metadata (e.g. video names, dates, tags, etc).
3. Generate searchable video clip metadata e.g. transcript, topics, faces, etc) using:
   - Search Data Management endpoints 
   AND/OR
   - Enrichment endpoints (which use LVS's default AI integration)
4. For ongoing updates to existing video content, use:
   - Asset Management endpoints to update asset-level metadata (e.g. update asset URLs, rename, etc.)
   AND/OR
   - Search Data Management endpoints (amend/correct transcripts, topics, etc).
5. To generate filtered lists of LVS assets (e.g. display a set of videos within a bespoke content management system), use Asset Management endpoints.

Presenting video content to end users

1. Use Search endpoints to enable end-users to run keyword searches of you media library and review their results. To enhance your search, you can also:
   - Use Asset Management endpoints to display additional content (e.g. thumbnails, asset names, dates, etc) within your search results.
   - Use Reporting endpoints to pre-populate search filter menus with most commonly occurring topics, faces, etc.)
2. When users trigger playback (e.g. clicks "Play All results":
    - Extract LVS Asset IDs and clip start/end time codes from the Search endpoint response
   -  Apply specific playback rules (e.g. minimum clip duration, merge adjacent or overlapping clips) and modify start/end time codes accordingly.
3. With the modified LVS Asset IDs and clip start/end time code data taken from the Search endpoint response, use the Assembly endpoints to select and sequence the relevant video clip, and generate a playable MP4 container or HLS stream.