Setting up workflows

The following is a list of asset workflows and actions that the users can do in medialoopster. For each action you need to assign to the users various frontend permissions, device write permissions and production memberships, unless the users are superusers. 

WorkflowPermissions
Browser
  • read production membership (required overall)
Create assets of a type*
  • upload:
    • upload_<type>asset
  • ingest:
    • ingest_control
    • edit_viewer_options
    • see_viewer_status
    • see_viewer_logs
  • write production membership
Manage favorites lists
  • rough_cut_editing
  • rough_cut_editing_demo
Edit assets of a type
  • edit_<type>asset_metadata
  • write production membership

Additionally to change the asset's delete date via bulk edit in the user browser interface:

  • change_<type>asset_date_del 
  • write and delete production membership

Additionally for video assets:

  • annotate_asset
  • edit_sequence
  • change_rights_rnb
  • change_trip_id
  • change_shot_licensor
  • change_shot_license
  • change_shot_location_city
  • export_still_frame
Tag with keywords assets of a type
  • use_<type>keyword
Share assets
  • share_production_asset
  • read production membership on the target production 
Transfer HighRes from assets of a type
  • transfer_<type>_asset
  • write production membership on the target production 
Archive assets of a type
  • archive_<type>_asset
  • restore_<type>_asset

Approve/disapprove for editorial purpose assets of a type

  • approve_<type>_asset
Management interface
  • manage_medialoopster (required overall)

Change end date of share or withdraw a share

  • share_production_asset
Hold assets of a type (change their deletion date)
  • change_<type>asset_date_del 
  • write and delete production membership
Delete assets of a type
  • delete_<type>asset 
  • delete production membership

*the asset type can be audio, image, video or project.


Other workflows run automatically in the background for regular users, without the need to assign to the users special permissions. However, the worksflows require preliminary setup: