Binary Management expands web content management to binary files including photos, videos, and PDFs. One can manage binary files directly from the OU Campus staging server by scheduling future publishing times, setting binaries to expire, versioning, and setting up approval systems. In addition, Dependency Manager handles the renaming of binaries across the entire website, making it easy to apply site-wide changes from a single location.
Prior to the introduction of Binary Management, binary files were uploaded directly to the production server, offering no direct control over when they were made available for public viewing. Binaries 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. This had to be performed on a page-by-page basis. With the introduction of Binary Management, binary files are treated like all other files managed by OU Campus, offering many advantages to both users and administrators.
About File Choosers and Binary Management
In previous versions of OU Campus, including version 9, the default behavior was to access the production server when using a utility to choose a page or file.
OU Campus version 10 now has Binary Management enabled for an account, and it can be turned on for each site. The default for Binary Management to use the staging server, so that files, pages, and images will always default to staging, and the location that is linked to is the staging instance for all file choosers.
It is possible to override the default and switch to the production server, auxiliary site, or publish target, and choose from any of those locations.
When linking to an instance on staging, upon transformation, the Dependency Manager works behind the scenes to provide the appropriate link to the corresponding instance of the item on the production server or publish target.