Skip to main content
Skip table of contents

Create Item Placeholder Component [VF 21.4 IG]

Used for creating placeholder item with metadata. Add this tag "<pf-create-placeholder >" to html to use this component. Below are inputs and event of this component:

Input

Description

Sample Input

auth-service-url

The url to the identity server authentication service.

http://localhost:19081/Authentication/Core

auth-redirect-url

When the authentication service authenticated the user, the auth service will redirect to this url. Note: this url must be configured as "redirect url" of auth service.

http:// localhost:19081/MetadataEditor/

auth-logout-url

Logout redirect url of auth service.

http:// localhost:19081 /MetadataEditor/

auth-silent-refresh-url

The silent refresh html that oidc client use to refresh the auth token.

http:// localhost:19081/silent-refresh.html

metadata-editor-uri

Currently, the metadata editor does not directly access Vidispine or ConfigPortal api. Instead, requests are made to a proxy "metadata editor host" installed with VidiFlow which is then routed to Vidispine or ConfigPortal api. So this is the url of that proxy service.

http://localhost:19081/Platform.Clients/MetadataEditor/ (backslash needed.)

expected-media-type

The expected media type when creating placeholder item. Same with the query param "expectedMediaType" when accessing it via iframe.

video

image

header-text

Text to be shown in header of MetadataEditor.

Metadata
#

hide-search

Not yet implemented. Can be ignored.



Output

Description

Sample

saveClicked

Triggered when the save button is clicked.


placeholderCreated

When creating item placeholder, this will emit the result whether success or failed. The structure of the emitted event look like this

CODE
{
   success: boolean;
    id: string;
    errorMessage: string;
  }

{

success:: true,

Id: 'pf://system/item/VX-1'

}


{

success: false,

errorMessage: "some error"
}

metadataInitialized

Trigged when metadata is loaded




JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.