A user of a storage system can upload files for a media asset, which can include a high quality media file and various related files. As part of the upload process, the storage system can extract metadata that describes the media asset. The user can specify one or more lifecycle policies to be applied for storage of the asset, and a rules engine can ensure the application of the one or more policies. The rules engine can also enable the use of simple media processing workflows. A filename hashing approach can be used to ensure that the segments and files for the asset are stored in a relatively random and even distribution across the partitions of the storage system. As part of the lifecycle for the asset, the high quality media file can be moved to less expensive storage once transcoding of the asset or another such action occurs.

The described embodiments set forth techniques for preserving clone relationships between files at a computing device. In particular, the techniques involve identifying clone relationships between files in conjunction with performing operations on the files where it can be beneficial to preserve the clone relationships. The operations can include, for example, preserving clone relationships between files that are being copied from a source storage device (that supports file cloning) to a destination storage device that supports file cloning. Additionally, the operations can include preserving clone relationships when backing up and restoring files between a source storage device (that supports file cloning) and a destination storage device that does not support file cloning. In this manner, the various benefits afforded by the clone relationships between files can be retained even as the files are propagated to destination storage devices that may or may not support file cloning.

An electronic apparatus is provided. The electronic apparatus includes a camera, a storage, and a processor configured to store an image photographed by the camera and metadata of the image in the storage, the processor is further configured to identify whether first information related to the image is obtainable, based on the first information not being obtainable, generate metadata related to the first information based on second information, and store the generated metadata as metadata of the image.

Determining a name for a given file using file naming convention techniques based upon the context of the given file. The given file can include digital data and media content. In some instances, the context of the digital data and media content can be determined by using Natural Language Processing (NLP) to extract the substantive content of the digital data and Artificial Intelligence (AI) to properly classify the substantive content.

A recording medium stores a communication program executed by communication devices and causing: a first computer of a first communication device, on a side of providing data, to register first metadata including the data and attribute information; a second computer of a second communication device, on a side of using the data, to register second metadata including a processing service when processing and using the data and attribute information; the first computer to determine whether or not to approve the processing service based on the first and second metadata; and when the determination of whether or not to approve is to approve, a third computer of a third communication device, on a side of processing the data, to execute data processing based on the processing service in a data processing environment that disapproves access from the first and second communication devices to the data and the processing service.

An information processing apparatus includes: a determiner that determines an area including a handwritten figure from image data; a recognizer that recognizes a handwritten character from the handwritten figure; an acquirer that acquires a file name; and a file generator that generates a file with a file name based on a handwritten character when the recognizer recognizes the handwritten character based on the image data and generates a file with the file name acquired by the acquirer when the recognizer does not recognize a handwritten character.

A computer-implemented method is provided for managing data stores. The method comprises performing a discovery process to discover a plurality of data stores. Each data store is identified, metadata associated with each data store is determined, and the metadata associated with each data store is stored in a configuration database. A user interface is operable to select at least one discovered and identified data store and initiate a change request to modify the selected data store. The change request is executed, based on an instruction received via the user interface, to modify the selected data storage set, and, upon execution of the change request, an update of the metadata in the configuration database associated with the selected data storage set is triggered.

One example method includes receiving a request from a user to access data stored in a filesystem, in response to the request, retrieving metadata of the data and metadata of the user, validating the metadata of the data and the metadata of the user against a data access rule, and granting the user access to the data upon successful validation of the metadata of the data and the metadata of the user.

A verification architecture described according to embodiments of the present invention validates changes made to metadata and may comprise one or more subsystems and phases. According to some embodiments, the “mkfs” volume creation utility works in cooperation with the device driver to create a file system volume by means of reservation and initialization space for metadata structures inside the device's partition that is reserved for the specific file system volume. The storage device uses a verified area legend when checking write requests after the file system volume has been created. The verified area legends may be stored in a dedicated partition or inside the master boot record (MBR) or Globally Unique Identifier (GUID) partition table (GPT) or special memory chip (NAND flash, for example). Write requests that overlap with any extent of reserved metadata area must be verified to prevent metadata corruption.

A plurality of computing devices are communicatively coupled to each other via a network, and each of the plurality of computing devices is operably coupled to one or more of a plurality of storage devices. A plurality of failure resilient address spaces are distributed across the plurality of storage devices such that each of the plurality of failure resilient address spaces spans a plurality of the storage devices. The plurality of computing devices maintains metadata that maps each failure resilient address space to one of the plurality of computing devices. The metadata is grouped into buckets. Each bucket is stored in a group of computing devices. However, only the leader of the group is able to directly access a particular bucket at any given time.