Binary Management

Overview

This section requires that Binary Management be enabled for a site via Setup > Sites > Optional Features > Enable Binary Management.

Binary files in OU Campus v10 can be managed directly on the staging server through Binary Management. In addition to the ability to perform various file operations and page actions (such as editing and saving), links to binary files can be managed and automatically updated by the Dependency Manager in a similar way to how Dependency Manager works with pages. Previously, files were not managed by Dependency Manager, which meant that if a file was renamed, moved, or deleted, all links pointing to it were broken until a site check was run or someone identified that the link was broken. Now, with Dependency Manager enabled, pages that link to a file are automatically updated if that file is moved, renamed, or published.

When Binary Management is disabled, files can be uploaded through the OU Campus interface, but are published immediately to the production server (giving users less control over when those files are publicly viewable). With Binary Management enabled, files are uploaded to the staging server and must be published in order to exist on the production server.

Many file types can be previewed in OU Campus, sent to another user for review or approval, published directly or along with a page publish, or can be scheduled for publish or expiration. Additionally, images can be seamlessly uploaded, edited, and inserted into a page while editing in the WYSIWYG Editor.

By default, Binary Management establishes the staging server as the default server for file choosers when inserting files onto a page. Images placed onto a page using file choosers will be linked via the staging server and transformed to the production server or publish target upon page publish.

Binary file types, just like pages in OU Campus, can also be controlled with access settings and sent through a workflow. Administrators can also include binary files in the reporting available through the Reports menu.

Binary Management is enabled at the account level by default. Administrators may enable Binary Management for each site within an account. Dependency Manager must also be enabled for each site using Binary Management.

Binary Management Features

Once Binary Management is enabled, the following features and functionality becomes available:

  • Binary files can be managed on the staging server. This includes photos, videos, PDFs, and other binary file types.
  • Images can be edited on the staging server.
  • Access settings for binary files include assigning an access group, approver, enforcing an approver, assigning a group that can bypass approval, and excluding from the search indexing and from sitemap. Properties can be modified.
  • Binary files can be previewed.
  • A version of a file can be saved, to which it can later be reverted.
  • An action log is kept and can be filtered, sorted, and reviewed in list format.
  • Files managed on the staging server can be published, and publishes can be scheduled.
  • Expire actions can be set for binary files, include expire and delete, replace, or redirect.
  • Scheduled reminders can be set for a file, with notifications that can be sent to individual users or groups.
  • Binary files can be submitted for approval, and once so submitted are shown in Workflow and the Pending Approvals report.
  • Binary files with a scheduled publish or other scheduled actions are available in the Scheduled Actions report, which can be exported.
  • Binary files can be renamed, moved, copied, and deleted.
  • Dependency Manager automatically tracks file operations within a site or among sites within an account. Links to renamed or moved files are updated.
  • Previously uploaded images can be dropped onto a page with the Images gadget.
  • Binary files are supported in gadgets, the File Navigation sidebar, the Pages list view, and the Page Actions toolbar.

Binary File Types

Binary file types include image files such as JPG, PNG, and BMP files, and other files such as PDFs. How the OU Campus CMS manages specific file types is dependent upon inherent user level permissions, assigned access settings, file type, location (i.e., staging or production target), account and site settings, and template design. The following file types are considered binary file types by OU Campus:

3g2

3gp

aac

ai

aif

aiff

amv

asa

au

au

avi

bin

bmp

cab

cgi

class

cnt

ctl

dat

db

dlz

doc

dmg

docx

ds_store

dwt

elm

emf

eot

eps

epub

exe

ext

fla

flac

flv

gif

gz

hqx

htx

ibook

ico

ind

jar

jbf

jp2

jpe

jpeg

jpg

ksc

lck

lst

m2v

m4a

m4v

mbi

mcw

mcw

mdb

mde

mde

mdx

mid

mkv

mno

mov

mp3

mp4

mpeg

mpg

mso

nb

odt

ogg

ogv

pdf

png

pps

ppsx

ppt

pptx

psd

pub

pwd

ra

ram

rcv

rm

rtf

sit

svg

swf

swz

tar

tgz

thn

tif

tiff

tof

ttf

vcs

vsd 

vsdx 

wav 

webm 

wfm 

wma 

wmv 

wmz 

woff 

wpd 

wrf 

xls 

xlsx 

z

zip

 

 

 

 

 

By default, the system detects the file type, and based on file type opens the file with the WYSIWYG Editor or the Source Editor. For example, HTML files are opened by default in the WYSIWYG Editor. TXT files are opened with the Source Editor. The following file types are considered non-image, non-binary, editable files by OU Campus:

asp

aspx

cfm

chtml

cshtml

dna

gdgt

gsp

htm

html

inc

jsp

mht

php

php3

phtml

shtm

shtml

ssi

xhtml

Binary File Behaviors and File Operations

  • Binary files uploaded to staging must be published to production to be available on the web server.

  • When Dependency Manager is on, content moved to a different location on the staging server, including directories, are silently republished to the production target and links are updated automatically, unless the content is locked with an action that would otherwise prevent auto-publishing (for example, a scheduled expire).

  • Moving, renaming, or deleting content on the production target is not reflected on staging.

  • When moving files in OU Campus, files of the same name are not allowed to be moved into the same directory; for example, moving an index.pcf from one directory to another would result in an error notification. In order to avoid this, first rename the file and then move it to the desired directory.

  • When dragging content that will take a lengthy amount of time to complete, the operation will continue even if the user has navigated to another area of the CMS, and a notification will appear when the operation has completed.

  • When dragging to insert content in source view of a page, the character encoding of some file types may not be valid.