Project assets (projects)

medialoopster administration → medialoopster → Project assets

Management → Current assets → Project

Projects (project assets) are a generic way to group media files (as assets) and non media files together in a "bundle root". Each asset will be handled individually but remains part of the project. Projects have their own metadata.

Add a project

via the administration interface or via external tools by providing the following keyword arguments:

Name

Required

Description

name

Yes

Internal name of the project.

bundle_root

Yes

Folder where to group the project's files. There should already be a device allocated for the bundle root (or for a root path where the bundle root is included).

file_list

Yes

Final full path list of all files used in the project. It is assumed they are either non-media files, or media files of already created assets. The do not need to be part of the bundle root.

create_asset_file_list

Yes

Full path list of files to create assets for, while creating the project. They must be subpaths of the bundle root.

production_name

Yes

Name of the project's production.


then the following steps are automatically followed:

  • if the "file_list" argument is empty:
    • go recursively through the bundle root folder; if a file within the bundle root has its path in the "create_asset_file_list" argument:
      • create an asset from it
      • associate the bundle root device to the asset
      • add the asset to the project's "audio/image/video assets" field
      • add the file to the "file_list" argument
  • go through the "file_list" argument and fill the project's "Files" field with it in JSON format; 
    • if not already part of the bundle root, the files are not copied there.

More about deleting projects in the housekeeping, at "Deleting a project", and about archiving projects in archive. Existing projects can be managed as well in the management interface at "Current assets → Projects".

The "Audio/Image/Video assets" fields

  • after the project is created, you can add/remove assets to these fields via the project asset's administration page; 
    • their essence can be outside the bundle root as well
  • these assets only are visible in the user interface at "Assets used in project" and are affected via project actions (delete, send to archive, restore from archive, share with production), provided that their essence are in the "Files" field as well.

The "Files" field

  • does not get updated any more with added/removed assets via the "audio/image/video assets" fields
  • it gets however updated after archive activities
  • you can manually add files to it in JSON format
  • its list is visible in the user interface at "Files used in project"