Close
Next
Prev

 

    Loading...

Pluck Galleries provides a unique source of rich media content, increasing visitor engagement and enabling dramatic page view growth. It promotes user sharing, increases contributions, and engages and entertains through rich content generation, and can also be used for citizen-journalism, live event coverage, and education and instruction.

Pluck VideosVideos

Pinterest syndication integrated in the galleries application helps drive traffic back to your site. The Pin It () button is available on Pluck's photo and video detail pages and on the Persona Photos photo detail page, both on the first and third person views. If the user's persona is private, the Pinterest button does not appear.

Features

  • Video support
  • Public galleries
  • Voting and Reactions
  • Social Sharing and Syndication
  • Advanced moderation
  • Rewards
  • Personal galleries
  • Integrated Comments
  • Tagging
  • Integrated Discovery
  • Robust gallery management

Works With

Comments
  — Add Comments to Galleries and enable your users to share their opinions and offer feedback.
Persona
  — Users can create their own personal galleries.
Shares
  — Distribute gallery content to social bookmarking sites.
Connection
  — Syndicate gallery content to Pinterest.
Reactions
  — Engage users and identify quality content.
Discovery
  — Highest shows which photos and videos are the most recommended or most highly rated, which can be useful for contests and rewards.
Forums
  — Allow community members to create conversations and provide feedback on the content provided by other users, creating a more vibrant community experience.

Implementation Tips

Pluck encodes uploaded videos to Flash Video format, so video playback is only supported on devices that support Flash.

Details

Pluck Gallery Videos offers a rich mechanism for video sharing that can be integrated into any community experience. Engineered to drive participation and interaction around contributors’ submissions, Pluck Galleries lets community members upload and display their favorite videos.

  • MailVideoApprovedSubjectText

    Description: Subject text that will be sent on a video approved notification, assuming user has email enabled in persona profile settings.

    Default Value:

    Applications: Video Email

    Preference Type: SiteSpecific

    Import: YES

    Value Range:

  • SendEmailWhenVideoApproved

    Description: If true, an email notification will be sent when video is approved, assuming user has email enabled in persona profile settings.

    Default Value: true

    Applications: Persona Email

    Preference Type: Global

    Import: YES

    Value Range: true false

  • ApprovedSitesForEmbeddedContent

    Description: A list of urls that are approved hosts for embedded html for user-generated content. This is the list of domains (e.g. youtube.com) for which embedded video content will be allowed in via Tiny. If the embedded video references a site not listed here (by url) then the embed will be disallowed in the UI.

    Default Value:

    Applications: System

    Preference Type: SiteSpecific

    Import: YES

    Value Range: string

  • CMWDisplayOriginalVideoUrl

    Description: This pref determines whether or not the URL to the original (pre-transcoded) video will be displayed in the CMW

    Default Value: false

    Applications: System

    Preference Type: Global

    Import: NO

    Value Range: true false

  • VideoStoragePath

    Description: This is the path where the inital video is copied (before uploading to ems)

    Default Value: C:\pluck2\videos\

    Applications: System

    Preference Type: Global

    Import: NO

    Value Range: string

  • VideoWatcherEnabled

    Description: This controls whether or not the video watcher thread runs. For sites that do not require video, the thread should be disabled. For sites that do use video, the thread must be enabled.

    Default Value: false

    Applications: System

    Preference Type: Global

    Import: NO

    Value Range: true false

  • EmsTranscodeTimeoutMS

    Description: This is the amount of time allowed (in milliseconds) before the EMS watcher will abort a transcode and send the video file back to the raw folder (eg. Vidavee) 2 hours

    Default Value: 7200000

    Applications: Photos

    Preference Type: SiteSpecific

    Import: NO

    Value Range:

  • FFMpegThumbnailDelay

    Description: When using FFMpeg for Video processing, the video thumbnail is taken (x) number seconds into the video. This only affects newly uploaded files, not existing files already on the system.

    Default Value: 3

    Applications: Video

    Preference Type: Global

    Import: YES

    Value Range:

  • FFMpegThumbnailSizeLarge

    Description: When using FFMpeg for Video processing, the video thumbnail large size. This only affects newly uploaded files, not existing files already on the system.

    Default Value: 440

    Applications: Video

    Preference Type: Global

    Import: YES

    Value Range:

  • FFMpegThumbnailSizeMedium

    Description: When using FFMpeg for Video processing, the video thumbnail medium size. This only affects newly uploaded files, not existing files already on the system.

    Default Value: 200

    Applications: Video

    Preference Type: Global

    Import: YES

    Value Range:

  • FFMpegThumbnailSizeSmall

    Description: When using FFMpeg for Video processing, the video thumbnail small size. This only affects newly uploaded files, not existing files already on the system.

    Default Value: 60

    Applications: Video

    Preference Type: Global

    Import: YES

    Value Range:

  • FFMpegVideoBitRate

    Description: When using FFMpeg for Video processing, the bit rate setting that is passed to the FFMpeg processor. This only affects newly uploaded files, not existing files already on the system.

    Default Value: 2500

    Applications: Video

    Preference Type: Global

    Import: YES

    Value Range:

  • FFMpegVideoFrameRate

    Description: When using FFMpeg for Video processing, the frame rate setting that is passed to the FFMpeg processor. This only affects newly uploaded files, not existing files already on the system.

    Default Value: 30

    Applications: Video

    Preference Type: Global

    Import: YES

    Value Range:

  • FFMpegVideoQuality

    Description: When using FFMpeg for Video processing, the quality setting that is passed to the FFMpeg processor

    Default Value: Standard

    Applications: Video

    Preference Type: Global

    Import: YES

    Value Range:

  • FFMpegVideoSize

    Description: When using FFMpeg for Video processing, the video size setting that is passed to the FFMpeg processor. This only affects newly uploaded files, not existing files already on the system.

    Default Value: 608x342

    Applications: Video

    Preference Type: Global

    Import: YES

    Value Range:

  • OriginalVideoUrlBasePath

    Description: Defines the path under the sitelife application at which we will mount the original videos virtual. This shouldn't need to change and this pref is only as a fail safe which we don't expect to be overriden generally.

    Default Value: Content/Videos/Store/Main

    Applications: Blogs Comments Forums

    Preference Type: SiteSpecific

    Import: YES

    Value Range:

  • OriginalVideoUrlBasePathIsOverridden

    Description: Flag that is set if the value is overriden - changed per request (pck vruntime setting)

    Default Value: false

    Applications: System

    Preference Type: SiteSpecific

    Import: NO

    Value Range:

  • VidaVeeVideoPlaybackUrl

    Description: VidaVee video playback url.

    Default Value: http://prod.publish.vidavee.net:80/vidad/publish.vidavee.com/pluck/Pluck/

    Applications: Blogs Comments Forums

    Preference Type: SiteSpecific

    Import: YES

    Value Range:

  • VideoGalleryDetailWidgetPath

    Description: This is the video path on the customer's website, where a specific video will be. The path is relative as it's built by prepending ClientBaseUrl. This was never implemented as a widget, but this path is used in the RecentActivity and Discovery Calls to indicate where on the customer's site to display videos.

    Default Value:

    Applications: Photos

    Preference Type: SiteSpecific

    Import: YES

    Value Range: string

  • VideoGalleryDetailWidgetPathIsOverridden

    Description: Flag that is set if the value is overriden - changed per request (runtime setting)

    Default Value: false

    Applications: System

    Preference Type: SiteSpecific

    Import: NO

    Value Range:

  • VideoGalleryWidgetPath

    Description: This is the video gallery path on the customer's website, where a video gallery will be. The path is relative as it's built by prepending ClientBaseUrl. This was never implemented as a widget, but this path is used in the RecentActivity and Discovery Calls to indicate where on the customer's site to display the video gallery.

    Default Value:

    Applications: Video

    Preference Type: SiteSpecific

    Import: YES

    Value Range: string

  • VideoGalleryWidgetPathIsOverridden

    Description: Flag that is set if the value is overriden - changed per request (runtime setting)

    Default Value: false

    Applications: System

    Preference Type: SiteSpecific

    Import: NO

    Value Range:

To set up Pluck Videos using REST

  1. Before you can install Pluck applications on your pages, your Pluck Application Server environment must be set up.
  2. Determine which page(s) you want to add a Videos to.
  3. Make sure any preferences are set. Your Pluck representative can help you determine if any preferences are relevant to your implementation and what settings should be made for Videos.
  4. Load the Pluck Libraries. Give your site access to the applications on the Pluck Application Server by including the following somewhere in the <head> tag:
    <script type="text/javascript" src="http://yourPluckServer.com/ver1.0/Content/ua/scripts/pluckApps.js"></script>

    where yourPluckServer is the domain of your Pluck server.

  5. Include the Pluck Applications CSS. In the <head> tag, link to the Pluck Application CSS:
    <link rel="stylesheet" type="text/css" href="http://yourPluckServer.com/ver1.0/Content/ua/css/pluckAll.css" />

    where yourPluckServer is the domain of your Pluck server.

  6. Make The REST Call. Call the Videos response with the appropriate URL:
    http://yourdomain.com/ver1.0/pluck/publicVideos.app?plckVideoPage=Video&clientUrl=http%3A%2F%2Fwww.yourdomain.com%2Fpageyouareon%3Fquerystring

    where yourdomain is the domain of your Pluck server.

    Note:

    When installing REST applications, you must pass the SiteLifeHost and AT cookies in the REST call. The AT cookie is case sensitive and is lowercase by default. Depending on your environment setup you may be required to pass additional cookies. The clientUrl is also required and should be passed in as the current page being requested with the full querystring. URLencode the entire value when adding it to the above URL. Don’t URLdecode the requesting URL prior to encoding it or you can end up with invalid URLs. For more information, ask your Pluck Representative.

Supported Codecs For Pluck Video

Pluck currently supports the following video codecs for uploading and transcoding video:

  • 4xm
  • 8bps
  • VMware video
  • aasc
  • adpcm_4xm
  • adpcm_adx
  • adpcm_ct
  • adpcm_ea
  • adpcm_ima_dk3
  • adpcm_ima_dk4
  • adpcm_ima_qt
  • adpcm_ima_smjpeg
  • adpcm_ima_wav
  • adpcm_ima_ws
  • adpcm_ms
  • adpcm_sbpro_2
  • adpcm_sbpro_3
  • adpcm_sbpro_4
  • adpcm_swf
  • adpcm_thp
  • adpcm_xa
  • adpcm_yamaha
  • alac
  • asv1
  • asv2
  • atrac 3
  • avs
  • bethsoftvid
  • bmp
  • c93
  • camstudio
  • camtasia
  • cavs
  • cinepak
  • cljr
  • cook
  • cyuv
  • dca
  • dnxhd
  • dsicinaudio
  • dsicinvideo
  • dvbsub
  • dvdsub
  • dvvideo
  • dxa
  • ffv1
  • ffvhuff
  • flac
  • flashsv
  • flic
  • flv
  • fraps
  • g726
  • gif
  • h261
  • h263
  • h263i
  • h264
  • huffyuv
  • idcinvideo
  • imc
  • indeo2
  • indeo3
  • interplay_dpcm
  • interplayvideo
  • jpegls
  • kmvc
  • liba52
  • libamr_nb
  • libamr_wb
  • libfaad
  • libgsm
  • libgsm_ms
  • loco
  • mace3
  • mace6
  • mdec
  • mjpeg
  • mjpegb
  • mmvideo
  • mp2
  • mp3
  • mp3adu
  • mp3on4
  • mpc sv7
  • mpeg1video
  • mpeg2video
  • mpeg4
  • mpeg4aac
  • mpegvideo
  • msmpeg4
  • msmpeg4v1
  • msmpeg4v2
  • msrle
  • msvideo1
  • mszh
  • nuv
  • pam
  • pbm
  • pcm_alaw
  • pcm_mulaw
  • pcm_s16be
  • pcm_s16le
  • pcm_s24be
  • pcm_s24daud
  • pcm_s24le
  • pcm_s32be
  • pcm_s32le
  • pcm_s8
  • pcm_u16be
  • pcm_u16le
  • pcm_u24be
  • pcm_u24le
  • pcm_u32be
  • pcm_u32le
  • pcm_u8
  • pcm_zork
  • pgm
  • pgmyuv
  • png
  • ppm
  • ptx
  • qdm2
  • qdraw
  • qpeg
  • qtrle
  • rawvideo
  • real_144
  • real_288
  • roq_dpcm
  • roqvideo
  • rpza
  • rv10
  • rv20
  • sgi
  • shorten
  • smackaud
  • smackvid
  • smc
  • snow
  • sol_dpcm
  • sonic
  • sp5x
  • svq1
  • svq3
  • targa
  • theora
  • thp
  • tiertexseqvideo
  • tiff
  • truemotion1
  • truemotion2
  • truespeech
  • tta
  • txd
  • ultimotion
  • vc1
  • vcr1
  • vmdaudio
  • vmdvideo
  • vorbis
  • vp3
  • vp5
  • vp6
  • vp6f
  • vqavideo
  • wavpack
  • wmav1
  • wmav2
  • wmv1
  • wmv2
  • wmv3
  • wnv1
  • ws_snd1
  • xan_dpcm
  • xan_wc3
  • xl
  • xsub
  • zlib
  • zmbv

Drop Videos On a Page

  1. Load the Pluck libraries. In the <head> tag, add:

    <script type="text/javascript" src="http://yourPluckServer.com/ver1.0/Content/ua/scripts/pluckApps.js"></script>

    where yourPluckServer is the domain of your Pluck server.

  2. Build the parameter string:

    The parameter string is a comma-delimited list of required and optional parameters meant to format the widget. For example:

  3. Place the Videos JavaScript call on the page where you want the app to appear:

  4. Save and reload. The Pluck Videos application appears on the page where you put the PAS call.

    6.0.11 Release        © 2014 DemandMedia                                   Teacher’s Edition