Video Fingerprinting
In this post I want to share my experiments on how to generate video fingerprints.
Read moreAbout MetaLoom
Loom is a Headless Media Asset Management System which is still in early development. At the moment there are no public sources or binaries available for download. If you are however interested in the development process or have general question I recommend to checkout my blog.
Loom is a private project which is not backed by a company. The design, development is done by Johannes Schüth.
Assets
Assets of any sort can be feed into Loom. Stored assets will be processed and made available via S3 and REST API.
Contents
Additional contents (e.g. metadata, tags, ratings, text, numbers, free JSON) can also be stored in Loom along with your assets.
API
The REST and GraphQL API allows you to retrieve and update the assets and their connected contents.
Planned features
This list contains some of the key features which are planned for Loom.
Developer Centric
The whole architecture of loom has a developer centric design which makes it easy to adapt it to your needs.
REST API (planned)
The loom server provides you with a powerful REST API which can be used to manage all resources.
GraphQL (planned)
In addition to REST the server also provides a GraphQL API which allows you to fetch nested data in one step.
ACL (planned)
Loom comes with a powerful permission system. Permissions can be granted on a object level.
SSO (planned)
SSO IAM providers such as RedHat Keycloak, Auth0, Okta will be natively supported. No need for complicated plugins.
Asset Store (planned)
Existing assets can be referenced from disk or S3. Alternatively files can be uploaded and stored locally or in a configured S3 bucket.
Media fingerprinting (planned)
An extension can be attached which allows the generation of media fingerprints. These fingerprints can be used for asset blacklisting and similarly search using nearest neighbor search.
Image manipulation (planned)
Images can be resized and cropped. The focalpoint can be set on images in order to help generation of cropped images for responsive designs.
Video thumbnail generation (planned)
Thumbnails can be automatically generated from video content.
Search (planned)
The stored metadata can be indexed using Elasticsearch.
Tagging (planned)
Loom comes with a system which allows you to tag assets, namespaces and contents.
Metadata (planned)
Sometimes data can’t be structured using the provided models. Loom thus provides you with options to add custom metadata to any element it stores.
Import / Export (planned)
Selective data can be exported and re-imported in another instance.
Metadata extraction (planned)
Metadata from images, videos, documents will automatically be extracted and make accessible via REST or GraphQL API.
User Content (planned)
User specific content such as comments, taggings, ratings can be stored along with your assets or content elements.
Content Model (planned)
Content models can be used to provide a structure for metadata that can be stored in addition to assets.
Webhooks (planned)
The server provides webhooks that allow you to trigger other attached processes.
Devops Features
These various features help you to integrate Loom into your environment.
Multiple Storage Options (planned)
You can choose between different persistent modes. In-Memory, Filesystem, MariaDB, PostgreSQL
Monitoring (planned)
Monitoring data will be made accessible via a Prometheus scrape endpoint. You can thus track status of the instances via a Grafana dashboard.
CLI (planned)
The CLI can be used to run admin tasks and also trigger synchronization tasks for new assets.
Kubernetes support / Helm Chart (planned)
Loom fully supports Kubernetes and comes with a Helm Chart that helps you deploy it in your K8S cluster.
Extensions (planned)
Extensions can be registered in order to extend the functionality of Loom using Microservices or Serverless servies (e.g. AWS Lambda).
Clustering (planned)
Multiple instances of Loom can form a cluster in order to help you scale your API.
S3 (planned)
Assets can be referenced from an existing S3 bucket or you can choose to use a bucket to store newly uploaded assets.
Latest Post
Day4 - Vert.x jOOQ PoC
In this post I want to walk you through a PoC I created that covers database handling with Vert.x and jOOQ.
Read more
Day1 - Project Design
In this post I would like to share how I approach the design for Loom.
Read more
Contact Us
Contact Details
If you want to know more about MetaLoom you can get in touch via Email.
Vienna, Austria
Email: hello@metaloom.io