You do not have permission to edit this page, for the following reasons:

This IP address has been blocked from editing Wikipedia.
This does not affect your ability to read Wikipedia pages.
Most people who see this message have done nothing wrong. Some kinds of blocks restrict editing from specific service providers or telecom companies in response to recent abuse or vandalism, and can sometimes affect other users who are unrelated to that abuse. Review the information below for assistance if you do not believe that you have done anything wrong.

The IP address or range 35.170.0.0/16 has been blocked (disabled) by ‪JJMC89‬ for the following reason(s):

The IP address that you are currently using has been blocked because it is believed to be a web host provider or colocation provider. To prevent abuse, web hosts and colocation providers may be blocked from editing Wikipedia.
You will not be able to edit Wikipedia using a web host or colocation provider because it hides your IP address, much like a proxy or VPN.
We recommend that you attempt to use another connection to edit. For example, if you use a proxy or VPN to connect to the internet, turn it off when editing Wikipedia. If you edit using a mobile connection, try using a Wi-Fi connection, and vice versa. If you are using a corporate internet connection, switch to a different Wi-Fi network. If you have a Wikipedia account, please log in.
If you do not have any other way to edit Wikipedia, you will need to request an IP block exemption.

How to appeal if you are confident that your connection does not use a colocation provider's IP address:
If you are confident that you are not using a web host, you may appeal this block by adding the following text on your talk page: ((unblock|reason=Caught by a colocation web host block but this host or IP is not a web host. My IP address is _______. Place any further information here. ~~~~)). You must fill in the blank with your IP address for this block to be investigated. Your IP address can be determined here. Alternatively, if you wish to keep your IP address private you can use the unblock ticket request system. There are several reasons you might be editing using the IP address of a web host or colocation provider (such as if you are using VPN software or a business network); please use this method of appeal only if you think your IP address is in fact not a web host or colocation provider.

Administrators: The IP block exemption user right should only be applied to allow users to edit using web host in exceptional circumstances, and requests should usually be directed to the functionaries team via email. If you intend to give the IPBE user right, a CheckUser needs to take a look at the account. This can be requested most easily at SPI Quick Checkuser Requests. Unblocking an IP or IP range with this template is highly discouraged without at least contacting the blocking administrator.

This block will expire on 05:20, 2 July 2025.

Even when blocked, you will usually still be able to edit your user talk page, as well as email administrators and other editors.

For information on how to proceed, please read the FAQ for blocked users and the guideline on block appeals. The guide to appealing blocks may also be helpful.

Other useful links: Blocking policy · Help:I have been blocked
Your IP address is in a range that has been blocked on all Wikimedia Foundation wikis. The block was made by ‪Jon Kolbert‬. The reason given is Open proxy/Webhost: See the help page if you are affected .
- Start of block: 05:38, 21 February 2024
- Expiry of block: 05:38, 21 February 2029
Your current IP address is 35.170.198.190. The blocked range is 35.170.0.0/16. Please include all above details in any queries you make. If you believe you were blocked by mistake, you can find additional information and instructions in the No open proxies global policy. Otherwise, to discuss the block please post a request for review on Meta-Wiki. You could also send an email to the stewards VRT queue at stewards@wikimedia.org including all above details.

You can view and copy the source of this page:

((More citations needed|date=July 2016))

((Use dmy dates|date=October 2023))

'''Content storage management''' ('''CSM''') is a technique for the evolution of traditional [[Media (communication)|media]] archive technology used by media companies and content owners to store and protect valuable file-based media assets. CSM solutions focus on active [[Content management|management of content]] and media assets regardless of format, type and source, interfaces between proprietary content source/destination devices and any format and type of commodity IT centric [[Computer data storage|storage]] technology. These [[digital media]] files (or assets) most often contain [[video]] but in rarer cases may be still pictures or sound. A CSM system may be directed manually but is more often directed by upper-level systems, which may include [[media asset management]] (MAM), automation, or traffic.

Typically, CSM systems are server-based [[software application]]s that reside between the media network, which connects the various broadcast or manipulation devices, and the [[storage network]], which connects the [[Nearline storage|nearline]] and archive storage tiers. The most basic function of CSM is the automated retrieval of high-resolution digital content (or essence) either from a data tape library (with the aid of a [[robot]]), or from a data server, and the delivery of that content either to a [[workstation]], playout or editing device. CSM also performs this process in reverse – moving content back to storage. In a given media operation, CSM may be used to facilitate content manipulation and repurposing; systems [[interoperability]] through high and low bit rate content [[transcoding]]; and/or site-to-site content replication for disaster recovery.

CSM solutions comply with the well known Reference Model for an [[Open Archival Information System]] (OAIS), which is fundamental to long-term archive and content preservation in file-based environments and are characterized by a set of application-specific [[wikt:function|functionality]], which can include:
*	Interfaces to proprietary media creation and consumption devices regardless of interface and storage topology
*	Transcoding and [[rewrapping]] technologies to ensure compatibility of content despite its source, format, [[encoding]] rates, aspect ratio, content container/wrapping standards
*	Direct integration to any type and format of storage device typically categorized as IT-centric storage devices allowing limitless or near limitless storage expansion
*	Integration with various network technologies including [[Ethernet]], [[Fibre Channel]], etc. and many protocols such as [[SCSI]], [[TCP/IP]], etc.
*	Full compliance with the well established OAIS model allowing combination of reference [[metadata]], media and any other key elements, which comprise an overall asset targeted to storage and preservation goals
*	Subjective content analysis for file-based audio/video content entering and exiting the system
*	[[Data integrity]] and validation checks such as checksums, etc.
*	Analytics engines for capturing, measuring and reporting on all internal aspects of the system including network bandwidth, read/write error rates, data storage profiles, etc.
*	Features for local and geographically distributed content storage for file-based distribution as well as disaster recovery applications
*	Extensibility through incremental addition of features and resources to allow limitless or near limitless expansion of the system

== History of CSM ==

The concept of CSM was first introduced in November 2006 by Brian Campanotti and Rino Petricola from Front Porch Digital Inc, one of the providers of CSM solutions. CSM solutions have their origins in archive management systems, but their functionality is considerably broader. Likewise, CSM systems resemble [[hierarchical storage management]] (HSM) systems in that both migrate among storage tiers, but they are distinct. For example, CSM software is media-specific, with internal decision-making models based on media-centric parameters, and with programmatic interfaces specific to control and management by broadcast business systems such as traffic, inventory, and automation. CSM groups related assets (typically video file and related multilingual audio files) into a single managed object for storage and retrieval. CSM does not use [[stub file]]s, which are pointers to files, but instead handles actual media files directly. CSM migrates files by copying them between systems rather than transferring them from system to system. And finally, by definition, CSM does not stand alone but functions as an [[abstraction layer]] between disparate systems including various storage devices, broadcast editing and playout devices and even end consumer devices such as set top boxes and Web streaming sites.

The most significant differentiator between CSM and HSM solutions is the difference between migration between tiered storage fundamental to HSM and the active [[Storage Resource Management (SRM)|storage management]] fundamental to CSM solutions. Conceptually, HSM solutions are used to age content to less expensive tiers of storage based on static policies examining parameters such as least recently accessed, file size, specific directories/paths, etc. and treat each file as a separate and unique entity. Although CSM solutions also manage tiered storage (although not specifically limited to any type, amount or storage technology) but do not rely on static policies but rather can be living policies that can be assigned dynamically to content entering the system and govern [[replication (computing)|replication]] policies, storage persistence, age-based migration as well as more advanced content aware processing steps such as transcoding, rewrapping, reformatting and subjective quality analysis.  In some cases, the content stored within the CSM system is intentionally different than the content that entered the system initially. As an example, content entering a CSM solution in a [[legacy media]] format such as Pinnacle MPEG2 may be intentionally transcoded to MPEG2 IMX50 and wrapped in an industry standard format such as [[Material Exchange Format|MXF]] to ensure longer term compatibility with other systems connected to the CSM solution. These media-centric workflows are not inherently supported by HSM solutions.

Based on the content centric focus of CSM solutions, they do not have legacy reliance on key HSM traits such as the use of stub files, which must remain on the original [[file system]] from where the file was migrated to cheaper tiers of storage. Although beneficial in some environments where HSM is being used simply as a "disk extender" for economic motivation, this feature is a significant limitation in active file-based content workflows typical in media, entertainment and preservationist applications where CSM solutions are key. Because of the inability for broadcast devices to maintain these HSM specific stub files on their internal (online) disk, the use of HSM systems in these advanced applications mandates a copy of the media content be made first from the online storage to some other tier of spinning disk prior to the HSM system taking ownership and migrating the content to other tiers of disk. As the HSM systems do not have the ability to directly interface to these various broadcast and media devices such as encoders, video servers, editing systems, etc. there is usually another software application responsible for this additional step such as a media asset management (MAM) system or other application specific utility.

CSM solutions extend the realm of content control and management directly from the internals of the content source and destination devices through any number and type of [[mass storage]] devices (disk, tape, optical, offline, etc.) all managed by configurable intelligent policies similar in concept to information lifecycle policies (ILM) but enhanced to become "content aware".

CSM solutions are not meant to age content into less expensive storage over time as its perceived value diminishes but rather actively play a part in a fairly symmetrical content lifecycle where content stored within the CSM system yesterday or five years ago is just as likely to be requested to be restored.  All content stored within a CSM storage [[infrastructure]] is equally viable for restore operations at any point of time and often no reliable predictability is possible.

Augmenting the overall content storage capacities by allowing the addition of less expensive storage technologies is an advantage of CSM solutions but preservation is also a key driver. In terms of preservation, high-value content (historical, cultural, monetary, etc.) can be assigned differing ILM policies that can govern the number of copies or instances of the content maintained by the system and also geographical distribution to other CSM solutions via [[Wide area network|WAN]] connectivity providing distribution as well as [[disaster recovery]] functionality.

Example of CSM in Broadcast
An example of the role of CSM within a broadcast setting is as follows: A movie is ingested into the content owner's [[workflow]] leveraging an encoding device and a control system such as [[automation]] or MAM. The control system instructs the CSM system to simultaneously analyze the content to ensure acceptable subjective quality, copy this original material into the archive library, make two copies or instances of it for protection and generate a low resolution [[Windows Media]] proxy version for Web access. An editor uses the MAM system to view the proxy generated by the CSM solution, and from his/her desktop workstation selects shots for use in a promo for the movie. The editor then sends his/her [[edit decision list]] (EDL) to the CSM system, which restores to the editing system only the desired broadcast-quality segments based on mark in and mark out [[timecode]] values defined within it. The CSM system then transcodes or rewraps the segments as necessary, so they can be used by the editor in the creation of the promo. Once the editor completes the promo, the editing system sends it via the CSM system (which can also repeat the replication and proxy generation process) to the on-air video servers for playout to air.

==See also==

* [[Content management]]
* [[Digital library]]
*[[Digital preservation]]
* [[Extensible Metadata Platform]]
* [[Information lifecycle management]]
* [[Hierarchical storage management]]
* [[Repository OSID]]

==References==
* Campanotti, Brian (2007). Content Storage Management in the Newsroom, National Association of Broadcasters (NAB) Proceedings
* Campanotti, Brian (2009). Decomposing Media Operations, SMPTE Proceedings, Hollywood, LA
* Campanotti, Brian (2007). Content Storage Management in Broadcast Applications, FKT
* Campanotti, Brian (2007). Emerging Trends in File Based Infrastructures, Broadcast Engineering
* Campanotti, Brian (2007). File Based Workflows, TV Technology América Latina
* Campanotti, Brian (2007). How to Buy an Archive Systems, TVB Magazine
* Campanotti, Brian (2006). Choosing a Storage Management System for Broadcast, Broadcast Engineering
* Campanotti, Brian (2006). Disaster Recovery through Archive Management, Broadcast Engineering
* Campanotti, Brian (2005). Digital Archive Software in Broadcast, Information Systems

<!--- See [[Wikipedia:Footnotes]] on how to create references using <ref></ref> tags which will then appear here automatically -->
((Reflist))

((DEFAULTSORT:Content Storage Management))
[[Category:Information management]]

Pages transcluded onto the current version of this page (help):

Template:Ambox (view source) (template editor protected)
Template:DMCA (view source) (template editor protected)
Template:Dated maintenance category (view source) (template editor protected)
Template:Dated maintenance category (articles) (view source) (template editor protected)
Template:FULLROOTPAGENAME (view source) (template editor protected)
Template:Find sources mainspace (view source) (template editor protected)
Template:Main other (view source) (protected)
Template:More citations needed (view source) (template editor protected)
Template:Ns has subpages (view source) (protected)
Template:Reflist (view source) (protected)
Template:Reflist/styles.css (view source) (protected)
Template:Use dmy dates (view source) (template editor protected)
Module:Arguments (view source) (protected)
Module:Category handler (view source) (protected)
Module:Category handler/blacklist (view source) (protected)
Module:Category handler/config (view source) (protected)
Module:Category handler/data (view source) (protected)
Module:Category handler/shared (view source) (protected)
Module:Check for unknown parameters (view source) (protected)
Module:Find sources (view source) (template editor protected)
Module:Find sources/config (view source) (template editor protected)
Module:Find sources/links (view source) (template editor protected)
Module:Find sources/templates/Find sources mainspace (view source) (template editor protected)
Module:Message box (view source) (protected)
Module:Message box/ambox.css (view source) (protected)
Module:Message box/configuration (view source) (protected)
Module:Namespace detect/config (view source) (protected)
Module:Namespace detect/data (view source) (protected)
Module:Ns has subpages (view source) (protected)
Module:Unsubst (view source) (protected)
Module:Yesno (view source) (protected)

Return to Content storage management.

Retrieved from "https://en.wikipedia.org/wiki/Content_storage_management"