Embedded Files
Pain: Our newsroom was struggling to publish breaking news and event results as quickly as our competitors.
Pain: Our newsroom was struggling to publish breaking news and event results as quickly as our competitors.
Pill: MediaDropBox
Description: By switching our image inflow to Iceman Media’s cloud based MediaDropBox our editors were able to begin working with images in seconds after being taken, instead of the often 10-15 minutes delay caused by our legacy servers.
Proof: Being able to work with sports and event images in real time dramatically increased our ability to publish as fast or faster than our largest competitors.
MediaDropBox -> Openstore -> MediaHub -> CMS -> Openstore
MediaDropBox -> Openstore -> MediaHub -> CMS -> Openstore
Keywords: MediaDropBox, OpenstoreAPI, MediaHub, CMS, Content sharing, Image reports
New content are added via MediaDropBox to Openstore
Openstore send MediaHub messages of new content
CMS systems subscribes for Openstore messages
CMS Systems fetches content via OpenstoreAPI and use in production
CMS Systems adds publish information to Content via OpenstoreAPI
Openstore generates image reports for published content
Pain: We needed a fast, almost real time, and easy way to automatically translate all of our digitally published information and news into languages selected by our rapidly diversifying customer base.
Pain: We needed a fast, almost real time, and easy way to automatically translate all of our digitally published information and news into languages selected by our rapidly diversifying customer base.
Pill: MediaHub, Google Translate
Pill: MediaHub, Google Translate
Description: Iceman’s MediaHub is able to integrate with any external text translation service to provide exactly the speed and quality we require.
Proof: In less than a day we were able to integrate MediaHub, Google Translate and our CMS platform into a smooth and dependable translation workflow. The feedback so far has been very positive and as a result we are offering additional language services on our other publications as well.
CMS -> MediaHub ->Translation Service ->MediaHub ->CMS
CMS -> MediaHub ->Translation Service ->MediaHub ->CMS
Keywords: CMS, MediaHub, Google GCP
Article needs to be translated x languages, CMS system sends MediaHub message "translate to english and french"
Translation Service gets message and send Article to Google Translate
Translation Service sends MediaHub message "translated versions of article"
CMS system gets the translated versions and updates article with languages
Pain: It took us so much time and manual effort to identify and tag incoming images from sports events that we could only afford to do this in real time for a few of the most important events each year. Even when being prepared in advance it was a slow and inefficient process that required a huge effort. Because of this, our image metadata was minimal at best for all but the top-tier events meaning we were missing out on a lot of the long tail of value of both our current image inflow and our historical image repositories.
Pain: It took us so much time and manual effort to identify and tag incoming images from sports events that we could only afford to do this in real time for a few of the most important events each year. Even when being prepared in advance it was a slow and inefficient process that required a huge effort. Because of this, our image metadata was minimal at best for all but the top-tier events meaning we were missing out on a lot of the long tail of value of both our current image inflow and our historical image repositories.
Pill: MediaHub integration with best-in-class AI image recognition from AWS to provide seamless metadata enrichment of both real-time and archived images and assets.
Pill: MediaHub integration with best-in-class AI image recognition from AWS to provide seamless metadata enrichment of both real-time and archived images and assets.
Description: Using MediaHub’s ability to seamlessly integrate best in class AI micro services into both real-time and on-demand digital workflows.
Proof: By using MediaHub’s ability to integrate AWS’s AI micro services into our real-time and on-demand digital workflows we are now able to consistently publish top-tier events faster with high quality and lower costs than ever before. We are also now delivering expanded coverage of local and regional events which we believe is reducing churn and strengthening connections with our subscriber base.
MediaDropBox ->Openstore ->MediaHub ->ImageAnalyse ->MediaHub ->RaceInfo ->MediaHub ->Openstore
Keywords: Openstore, MediaHub, MediaDropBox, Chain of events, AWS Rekognition Image, Google GCP
Photographer send images direct from WiFi Camera via MediaDropBox to Openstore
Openstore send MediaHub message "new images"
ImageAnalyse service gets message and sends images to AWS Rekognition Image / Google GCP for "numberplate detection"
ImageAnalyse enriches image metadata with start numbers found on image and send MediaHub message
RaceInfo service gets message and use the GeoJson and Image metadata part in message do detect competition arena and race, enriches message with race info and send MediaHub message with enriched information
Openstore Application gets message about "updated image metadata" and updates database with race info for competitors found on image
Pain: We are struggling post-merger because all of our processes and legacy systems are heavily siloed, making it slow and difficult to share information and content between departments without losing control over usage rights and auditability. We are discussing migrating everything to a unified platform but this is a long-term project and we need to find a way to effectively share real-time information and collectively purchased content.
Pain: We are struggling post-merger because all of our processes and legacy systems are heavily siloed, making it slow and difficult to share information and content between departments without losing control over usage rights and auditability. We are discussing migrating everything to a unified platform but this is a long-term project and we need to find a way to effectively share real-time information and collectively purchased content.
Pill: MediaHub integration with AWS CMS S3 Storage
Pill: MediaHub integration with AWS CMS S3 Storage
Description: By using MediaHub to non-destructively incorporate all of the publisher’s image and content inflow streams into a single high-performance AWS S3 cloud based storage solution, the entire organization gains immediate access to all content inflows in real time with faster access speeds and significantly improved rights control and auditability
Proof: Though initially planned as an interim solution, using MediaHub and cloud based S3 has been tremendously successful and we are expanding how we use these services. By providing transparent, secure and auditable image and content access to our entire organization we have been able to improve our editorial responsiveness and even reduce some of our overhead costs.
Keywords: Amazon S3, CMS, MediaHub, Content sharing, Mail input
Cloud storage service connects to SMPT server, FTP catalogs and folders
When contents is available, Cloud storage service writes content to S3 extracts metadata (XMP/IPTC/EXIF/etc..) and send MediaHub message "new content available"
Subscribing services/applications get messages and fetches desired content from one place (S3)
Multiple CMS systems / services / apps get access to same Content in real time
Pain: We are an organization with a long and proud history of editorial and brand independence. Unfortunately this has led over time to entrenched systems and ways of working which are almost completely incompatible. We don’t have the budget or resources for a complete overhaul but we are in dire need of a way to share information and content between departments without losing control over where it originated, how and where everything has been used, GDPR & legal rights, auditability, etc. We are not currently planning for any major changes to our IT infrastructure so the solution must be very secure, easy to use and manage, and robust enough for us to confidently incorporate it into our core workflows for quite some time to come.
Pain: We are an organization with a long and proud history of editorial and brand independence. Unfortunately this has led over time to entrenched systems and ways of working which are almost completely incompatible. We don’t have the budget or resources for a complete overhaul but we are in dire need of a way to share information and content between departments without losing control over where it originated, how and where everything has been used, GDPR & legal rights, auditability, etc. We are not currently planning for any major changes to our IT infrastructure so the solution must be very secure, easy to use and manage, and robust enough for us to confidently incorporate it into our core workflows for quite some time to come.
Pill: Openstore
Pill: Openstore
Description: To meet this need without disrupting either ongoing operations or their existing legacy systems, the decision was taken to migrate each department’s legacy data stores into a single Openstore installation. Not only was the migration process seamless for their existing systems, but it was also invisible to end users and has the additional benefit of simplifying a number of the organization’s data security and disaster recovery needs.
Proof: By migrating data from each department’s legacy data silos into Iceman Media’s Openstore each of our departments now have the ability to share information and content easily, securely and with a significantly reduced risk of accidental rights violations.
Keywords: Openstore, Departments, Content sharing
Three different offices/media producers share one Openstore
All three have own parts in Openstore for their users wich only they can se
Users with permissions to share content can share objects to other departments
Pain: Manually adjusting images or performing reprographic work (e.g., color correction, scaling, resolution enhancement) can be time-consuming and prone to errors, especially if it's done repeatedly for multiple images with limited time available.
Pain: Manually adjusting images or performing reprographic work (e.g., color correction, scaling, resolution enhancement) can be time-consuming and prone to errors, especially if it's done repeatedly for multiple images with limited time available.
Pill: Indesign and Openstore integration
Pill: Indesign and Openstore integration
Description: By integrating Openstore with InDesign via the IcemanMedia Openstore ID Plugin, users can quickly search, retrieve, and place content directly into their design software. This eliminates the need to manually search for files, improving productivity and reducing errors from using outdated or incorrect assets.
Additionally, automating the scheduling and execution of repro workflows helps maintain a high production tempo while accommodating for higher-quality work when needed, providing both flexibility and efficiency.
Proof: By taking advantage of Openstore’s APIs and InDesign plugin we have been able to automate the majority of our repro workflows. The key result from this project has been an increased efficiency and feeling of improved collaboration between our teams, as well as a noticeable reduction in overall operational friction due to the improved repro version controls and automated image usage reports.
Keywords: Openstore, Indesign plugin, Autorepro, Manual repro, Image reports
User searches Openstore for content
User drag selected content into Indesign
IcemanMedia Openstore ID Plugin fetches content data via OpenstoreAPI and mount it on page
If Content is a Image type, user can adjust image on page and when ready order Automatic Repro or Repro for manual work (Photoshop)
If manual repro is ordered appointed user is notified that new job is in queue
When the print copy (profiled, scaled, enhanced ...) is ready on fileserver OS ID Plugin automatically replaces the "draft image" to the print ready copy
Page is published and Openstore automatically generates image reports for external images
Pain: Publishing and editing workflows have become inefficient due to the need to search for and copy files between local hard drives, external image agency websites and an overly complex collection of legacy filesystems which currently cannot be changed
Pain: Publishing and editing workflows have become inefficient due to the need to search for and copy files between local hard drives, external image agency websites and an overly complex collection of legacy filesystems which currently cannot be changed
Pill: Openstore
Pill: Openstore
Description: Implementing Openstore and the Openstore ID plugin as the universal interface for users to search for and access all available images regardless of the file’s original location eliminates the need to manually search for and document the location of files, improving productivity and reducing errors from using outdated or incorrect assets.
Proof: By using Iceman Media’s Openstore and InDesign plugin we were able to streamline what had been a cumbersome process without having to change any of our backend systems which was precisely what we wanted.
Keywords: Openstore, Indesign plugin, Image reports
User searches Openstore for content
User drag selected content into Indesign
IcemanMedia Openstore ID Plugin fetches the Original image and writes it to designated file server (or local disk)
IcemanMedia Openstore ID Plugin let user open it in Photoshop if it is necessary or if the original image is already print ready in Openstore the work is done...
Page is published and Openstore automatically generates image reports for external images
Pain: When content is sourced from external suppliers, there's often a time lag in getting the right images to the right teams for different types of projects (e.g., print vs. web). Without automated processes, this can create delays.
Pain: When content is sourced from external suppliers, there's often a time lag in getting the right images to the right teams for different types of projects (e.g., print vs. web). Without automated processes, this can create delays.
Pill: Openstore integrated with FTP servers
Pill: Openstore integrated with FTP servers
Description: Implementing Openstore to automate and provide real-time content ingestion, routing, and indexing ensures that critical content is immediately available to users once it's uploaded by external bureaus. This helps streamline workflows, as internal teams can access and use images immediately without waiting for manual processes. This reduces lead times in content delivery and makes the process more agile.
Proof: By automating all of our external content intake processes with Openstore we were able to dramatically shorten the time it took for our editors to receive real time event- and breaking news imagery.
Keywords: Openstore, External image suppliers, Large intake, Automation
External bureaus uploads content to FTP servers connected to Openstore via Openstore FTP Inqueues services
Openstore Routes, Index and Store images using XMP/IPTC & EXIF data
Users with access to External content in Openstore can use images in print or web etc..
When images is used image reports are automatically generated for each supplier of content (bureau)
Unused images is deleted (if Openstore is configured to do so)
Used images is archived (if Openstore is configured to do so)
Pain: Providing external users with easy access to content (images, videos, text) can be a complex process, especially when managing large libraries of assets or dealing with varying customer needs. Manual access methods or inefficient systems can lead to delays and frustration for external customers.
Pain: Providing external users with easy access to content (images, videos, text) can be a complex process, especially when managing large libraries of assets or dealing with varying customer needs. Manual access methods or inefficient systems can lead to delays and frustration for external customers.
Pill: Openstore and Openstore Content Sales (Websale)
Pill: Openstore and Openstore Content Sales (Websale)
Description: By allowing external users to log in to a Websale interface, Openstore simplifies the process of content search, selection, and download. External customers can easily find the content they need without relying on internal teams to manually fulfill requests. This reduces delays, lowers operational overhead, and improves the customer experience in a secure environment.
Proof: Introducing the Websale interface to our professional users has been the first step in our journey to gain greater value from our extensive historical archives and large numbers of associated freelance journalists and photographers. So far we have been very happy with how well the Websale interface has performed, allowing external professional users to easily search, select, and purchase or download content directly from our content repositories. Furthermore, the automated reporting is a tremendous help as it ensures that every transaction is properly tracked reported and charged for.
Keywords: Openstore, Openstore Images Sales (Websale) External users, External customers, External access to content
Content (images / videos) are added to Openstore
Openstore built in and configurable rules for which images to be shown external in Openstore Websale automatically kicks in
External users log in into Websale (public web gui for image search and selection and download)
External user downloads image and logged in user can use image in their production
Openstore generates download information for each external user and creates reports
Pain: Our editors have to navigate a mix of custom-developed and legacy CMS system interfaces and third-party software to work with and manage our content. Integrating these systems has proven to be difficult, costly and time-consuming, particularly when dealing with proprietary or poorly documented APIs
Pain: Our editors have to navigate a mix of custom-developed and legacy CMS system interfaces and third-party software to work with and manage our content. Integrating these systems has proven to be difficult, costly and time-consuming, particularly when dealing with proprietary or poorly documented APIs
Pill: Openstore, OpenstoreAPI
Pill: Openstore, OpenstoreAPI
Description: By using the OpenstoreAPI to roll out custom user interfaces and by taking full advantage of Openstore’s API interfaces, all connected legacy systems will be able to have an efficient, consistent and streamlined flow of content between themselves, the CMS and all production environments. These APIs provide for the possibility of seamless integration with other business applications as well (e.g., e-commerce platforms, marketing systems, or publishing tools), reducing data silos across the company and increasing operational efficiency.
Proof: Installing Openstore as our primary image search and retrieval interface and connecting it with our legacy CMS was straightforward and has helped increase our newsroom’s efficiency. Openstore’s ability to non-disruptively connect third-party software with legacy systems is also being used to enable internal test users to explore the potential of AI-enabled tools in selected parts of their daily workflows without having to pre-configure extensive test environments.
Keywords: CMS, OpenstoreAPI, Third party software
Develop own user interfaces with OpenstoreAPI to full integration in own systems
Search, View info, Fetch, Update content etc...
Online documentation to OpenstoreAPI
Online TEST bench for API calls within OpenstoreAPI dokumentation
Easy to use API, used by many different third party developers
150+ API calls, and still adding new ones to fully support all third party developers building more and more applications...
Pain: We have been a leading provider of news, media and information for more than 50 years. During our journey certain of our information domains have become siloed and increasingly specialized over time. This is causing a number of challenges for us, particularly as much of our content is stored across multiple new and legacy systems (e.g., CMS, DAM, video repositories, knowledge management systems, etc.) and risks becoming fragmented or outdated. This complexity and potential for fragmentation makes it difficult for our teams to confidently locate the content they need, leading to inefficiency, missed opportunities, and wasted time spent searching in different systems.
Pain: We have been a leading provider of news, media and information for more than 50 years. During our journey certain of our information domains have become siloed and increasingly specialized over time. This is causing a number of challenges for us, particularly as much of our content is stored across multiple new and legacy systems (e.g., CMS, DAM, video repositories, knowledge management systems, etc.) and risks becoming fragmented or outdated. This complexity and potential for fragmentation makes it difficult for our teams to confidently locate the content they need, leading to inefficiency, missed opportunities, and wasted time spent searching in different systems.
Pill: MediaHub, Centralized searching for content
Pill: MediaHub, Centralized searching for content
Description: MediaHub centralizes content management by aggregating updates, new uploads, and deletions from various systems (System A, B, C, D) into a single repository. By doing so, it eliminates the need to manually search through legacy systems individually, providing a single point of access for all content types (images, videos, articles, pages, etc.). This centralization streamlines content discovery and usage, improving efficiency and reducing frustration.
Proof: Introducing MediaHub for centralized content searching, sharing and access has helped us to reign in issues we were experiencing related to fragmentation, duplication, and trying to find and manage content across multiple systems. By centralizing access and providing a unified search, MediaHub helps to ensure our teams always have access to the most up-to-date, relevant content.
Keywords: CMS, MediaHub, Content sharing, Content Access, Central search for content
System A, B, C and D all holds content of different types, images, videos, articles, pages etc
Systems sends MediaHub messages when new content is available
Systems sends MediaHub messages when content is updated
Systems sends MediaHub messages when content are deleted
Application developers can develop search dialoges for searching content regardless where is is stored
Pain: As a large regional news agency we require the ability to securely and flexibly share urgent and time-sensitive material with external actors (e.g. for comment, legal review, collaboration & confirmation, etc.) and can’t afford to be limited by traditional sharing methods which are often slow, inflexible and insufficiently secure.
Pain: As a large regional news agency we require the ability to securely and flexibly share urgent and time-sensitive material with external actors (e.g. for comment, legal review, collaboration & confirmation, etc.) and can’t afford to be limited by traditional sharing methods which are often slow, inflexible and insufficiently secure.
Pill: Openstore, MediaDropBox, AWS S3
Pill: Openstore, MediaDropBox, AWS S3
Description: Taking advantage of Openstore and MediaDropBox’s highly efficient integration with Amazon S3 storage services. This integration enables any Openstore or MediaDropBox content to be reliably and securely shared via individual, time-constrained links to the material.
Proof: As we have quite a bit of experience with S3 containers it was straightforward to configure our Openstore and MediaDropBox installations to place any sensitive materials which require external sharing there and to automatically send time-limited links to each of the required recipients. So far everything is working as intended and we are satisfied with the installation.
Keywords: Openstore, Video, MediaDropBox, Amazon S3, Amazon AWS, Content sharing (external links)
Users in Openstore or MediaDropBox uploads content (images/videos etc)
Openstore (if configured to store videos on S3) stores original video on S3
Users with permission to share S3 links selects one video, and creates a public link to that object
Public (External links) kan when sharing in Openstore be set do be available for a certain time, 5 minutes, 1 hour, 7 days, etc etc...
Notifications to external users can be made by for example e-mail, containing the created public temporary link
Pain: When working with external photographers or suppliers, managing the intake of content, especially high-volume images and videos, can be cumbersome. It often requires manual intervention to upload files to the appropriate systems, or worse, content might accidentally be sent to the wrong destination, leading to delays, confusion, or errors.
Pain: When working with external photographers or suppliers, managing the intake of content, especially high-volume images and videos, can be cumbersome. It often requires manual intervention to upload files to the appropriate systems, or worse, content might accidentally be sent to the wrong destination, leading to delays, confusion, or errors.
Pill: MediaDropBox, MediaHub, in-camera WiFi
Pill: MediaDropBox, MediaHub, in-camera WiFi
Description: Iceman Media’s MediaDropBox acts as a central hub for file intake and automates the delivery of content to multiple systems simultaneously. Each photographer can send images directly from their camera via Wi-Fi, and these images are automatically routed to the specific systems relevant to their job’s workflow. This eliminates the need for manual uploads, dramatically speeding up the delivery time of newly captured images and reducing the risk of files being sent with missing, wrong or incomplete file information, significantly improving efficiency and accuracy.
Proof: Switching from our FTP-based workflows to the MediaDropBox and MediaHub services has been like night and day. Images now arrive in almost real-time which has been a real boost especially for national event coverage. And the improved metadata has been very useful in helping us take advantage of this speed. Overall, this has been an impactful project, the results of which we have been sharing with our sister publications.
Keywords: External suppliers, Photographers, Image / Video intake, Share jobs, Coworkers, Delivery routing, Delivery Copies
Image editor with permission to add new tasks/jobs to MediaHub create job for photographer and one coworker
External photographer takes photos and sends them directly to MediaDropBox via Camera WiFi
Job that the External photographers Camera send images to is set to deliver content to 4 different systems
Each system get the images at the same time
Image editor can change destination setting on external photographers job whenever wanted
Image editor can add keywords, descriptions, department in CMS system etc in job info, photographer don't need to edit job info (if the photographer don't want to do that, or lacks permission to do so)
Pain: Like most relatively large media houses, we have survived and participated in multiple rounds of industry consolidation, individual acquisitions and the rapid introduction of new digital technologies. As a result of these rapid and often overlapping changes our workflows, processes and IT environments have had a hard time keeping up. As a result many of our content assets such as images, articles, and published pages have become siloed in different systems, most of which were stored with insufficient interlinking. This made it difficult for different teams to easily find and access related assets, leading to inefficiencies in relevant content discovery and retrieval.
Pain: Like most relatively large media houses, we have survived and participated in multiple rounds of industry consolidation, individual acquisitions and the rapid introduction of new digital technologies. As a result of these rapid and often overlapping changes our workflows, processes and IT environments have had a hard time keeping up. As a result many of our content assets such as images, articles, and published pages have become siloed in different systems, most of which were stored with insufficient interlinking. This made it difficult for different teams to easily find and access related assets, leading to inefficiencies in relevant content discovery and retrieval.
Pill: Openstore
Pill: Openstore
Description: By coupling different assets (such as images, articles, and pages) together within Openstore, the company is able to create an efficient, centralized and robustly interconnected content ecosystem. Via Openstore’s ability to make the entire ecosystem’s content accessible, available and searchable regardless of where it physically resides, users gain the ability to quickly and easily navigate between related content—whether it's an article, an image, or a page layout - allowing for efficient access to all associated assets.
Proof: Using Openstore to automatically couple related assets with each other has made it significantly easier to review, update and build upon our previously published content. It has also opened interesting new avenues for exploring our extensive archives and for gaining insights into how our coverage and narratives have evolved over time.
Images are stored in Openstore and published in different papers / media
Papers are published and stored as PDF in Openstore
Articles are written, published and stored in Openstore
Due to joint publishing information, the different assets are coupled to each other
Users can now go from page to published images on that page, or from article to pages the article is published on, or from images to articles published on same page etc...
Pain: Managing relationships with multiple external bureaus and sales channels has been very complicated for us, especially since we haven’t been able to develop effective and streamlined processes for updating content, managing inventory, and maintaining consistent metadata across all of our systems.
Pain: Managing relationships with multiple external bureaus and sales channels has been very complicated for us, especially since we haven’t been able to develop effective and streamlined processes for updating content, managing inventory, and maintaining consistent metadata across all of our systems.
Pill: Openstore
Pill: Openstore
Description: Openstore enables image agencies to efficiently manage multiple external bureaus and sales platforms by establishing a separate, centralized repository of images in Openstore and ensuring that updates are automatically reflected across all systems. Whether it's a change in metadata, an image being taken down, or a price update, the agency can easily maintain a fine-grained control over its assets and ensure consistency across all external sales channels.
Proof: By improving the efficiency and accuracy of managing image sales across multiple third-party platforms, Openstore has enabled us to expand our sales activities into new markets without increasing headcount. It has automated and improved our export, metadata update, and synchronization processes, it has helped to reduce manual errors, improved rights tracking, and improved our potential scalability for future sales channel expansion.
Images in Openstore for sale in third party external system are put in export queue
Images exported to third party system with OS unique id
If third party systems updates image info, they sends XMP file with new updated image info/meta data
Openstore info updater updates the image with new info
External bureau sales images to their customers
This solution is currently in production with TT News Agency (https://tt.se/en/about-us/)
Pain: Over the past several years we have had to allocate more and more of our staff time towards the timely distribution and exporting of our recently produced content to external systems, clients, and various other publishing and archival platforms depending on the nature of the content. However, as this work is generally considered to be a low priority and assigned to new, temporary and/or junior staff, the quality and timeliness of these activities can be inconsistent. This has led to missed deadlines, delayed publications and significant frustration of the intended recipients.
Pain: Over the past several years we have had to allocate more and more of our staff time towards the timely distribution and exporting of our recently produced content to external systems, clients, and various other publishing and archival platforms depending on the nature of the content. However, as this work is generally considered to be a low priority and assigned to new, temporary and/or junior staff, the quality and timeliness of these activities can be inconsistent. This has led to missed deadlines, delayed publications and significant frustration of the intended recipients.
Pill: Openstore
Pill: Openstore
Description: Openstore’s ability to smoothly automate the majority of important and/or regularly occurring content export requirements make it possible for both publishers and recipients to feel confident that all agreed upon content will be delivered in a timely and consistent manner. Whether scheduled at specific times or triggered immediately by a user, the system ensures that the right content is delivered to each of the correct destinations on time. This type of automation helps to improve production workflows and to reduce errors, which is crucial for organizations with high volumes of content and tight deadlines.
Proof: Automating our content export workflows with Openstore has saved us quite a bit of effort, almost eliminated simple errors, and improved the scalability and timeliness of our content distribution capabilities.
Content can automatically be exported from Openstore
Several services is available for export, image exports, pdf exports, article exports, video exports
Exports can be scheduled or instant
Exports are made with FTP to destinations
Exports can also be triggered by permitted users within OpenstoreWeb GUI
Pain: Due to our recent merger it has become apparent that our existing tools are inadequate for managing and coordinating the expanded relationships, requirements and tighter deadlines of our new organization. As a result we have run into a number of delays due to system and administrative problems encountered when coordinating tasks and assigning and managing responsibilities across former organizational boundaries.
Pain: Due to our recent merger it has become apparent that our existing tools are inadequate for managing and coordinating the expanded relationships, requirements and tighter deadlines of our new organization. As a result we have run into a number of delays due to system and administrative problems encountered when coordinating tasks and assigning and managing responsibilities across former organizational boundaries.
Pill: MediaHub, MediaDropBox, Openstore
Pill: MediaHub, MediaDropBox, Openstore
Description: The process technologies and technical infrastructures contained within IcemanMedia’s MediaHub, MediaDropBox and Openstore enable the creation of deep, seamless and highly automated links to be created between organizational planning and task management systems, the Iceman Media platform and most legacy and 3rd-party systems. All without requiring significant reprogramming or restructuring of API capable systems.
Proof: As a result of our ‘quick fix’ decision to purchase Iceman Media’s cloud-based Media Hub, MediaDropBox and Openstore solutions we have been able to resolve our most pressing issues and are no longer at risk of unnecessary issues and delays due to poor task visibility, coordination and communication.
A task is added in the planning system, and assigned to User
Planning system Service sends MediaHub message "new job for user x"
MediaDropBox MH subscriber application gets message and creates job to User x
User X adds images to job and MediaDropBox inserts images in Openstore via OpenstoreAPI and send MediaHub message "new image in Openstore to job"
Planning system subscriber application gets messages of new images to job, and updates job information in planning system adds images to job with Openstore links to images (shows thumbnails of images)
Pain: Our legacy CMS has limited options for adding custom data to images or assets. This has been very limiting for us, especially when working to integrate 3rd-party solutions such as AI-based image analysis, rights management and archival system add-ons.
Pain: Our legacy CMS has limited options for adding custom data to images or assets. This has been very limiting for us, especially when working to integrate 3rd-party solutions such as AI-based image analysis, rights management and archival system add-ons.
Pill: Openstore, Openstore APIs
Pill: Openstore, Openstore APIs
Description: Openstore’s APIs offer an easy way for third-party developers to add custom information and data to images throughout their workflow. This flexibility allows developers to store context-specific metadata with each image, such as custom tags, editorial notes, or other relevant details that provide more insight into the image's usage or context. Since Openstore imposes no limit on the amount of custom data that can be associated with an image, it becomes much easier to track, categorize, and personalize images based on their specific use cases. This capability enhances the organization and accessibility of images within the system.
Proof: By providing new ways for both our in-house and third-party developers to add custom metadata to images based on their specific characteristics and usage, we believe that Openstore and its APIs will enhance our ability to discover content accurately, improve our workflow integration, and foster better collaboration with our third-party developers.
Third party developer needs custom data on images when placed in article
API call UPDATE_IMAGE_EXTRA_DATA to add key/value of choice
Adding "placed in article"
API call GET_IMAGE_INFO returns standard image info + extra data key/values list, third party developer can make necessary actions with extra data
Images can have unlimited numbers of extra data, keys are unique
Pain: Due to a lack of resources (staff) we are not often able to create interactive applications for significant social events (elections, royal weddings/funerals, etc) even though such services have been shown to help lift our customer retention programs.
Pain: Due to a lack of resources (staff) we are not often able to create interactive applications for significant social events (elections, royal weddings/funerals, etc) even though such services have been shown to help lift our customer retention programs.
Pill: Openstore, MediaHub
Pill: Openstore, MediaHub
Description: Automatically generating dedicated content for targeted applications and interactive web pages has become dramatically easier through Iceman Media’s native microservices–based architecture. This makes it possible to quickly develop and deploy in a matter of hours interactive applications and websites containing complex constellations of highly coordinated image-, data and other internally- and externally-sourced content streams with complete branding consistency and simplified controls to download images, wallpapers and other valued content.
Proof: Using Openstore and MediaHub, our existing teams were able to create in less than a day a fully-interactive application explaining in detail what was happening in the American presidential elections, including numerous infographics updated in real time, image galleries and real-time feeds as well as a breaking news ticker and indicators of momentum based on social media sentiment and activity. Before Openstore and MediaHub this would have been impossible for us to manage without employing expensive consultants. As a result we are planning new campaigns for the upcoming year which will take strategic advantage of these capabilities more strategically.
Keywords: Openstore, External users, Share images, Public access , Website
Permitted user selects images in Openstore
User tell Openstore to generate new (or modify existing) website
User sets time limit for the site to exist on web
Openstore generates a new website with a HTML template of choice
When website is generated by Openstore user gets the URL to website
User mails the URL to trusted external users and they can browse and download images of choice
Websites can also be generated by third party developers via API call GENERATE_WEBSITE_ON_CLOUD
Pain: Our legacy CMS is limited in its ability to work with or make use of non-standard metadata fields which has always been a pain but it has been something we have learned to work around - even using creatively structured file names as a last resort. Unfortunately, our needs are becoming too complex to rely on these sorts of last-minute workarounds. What we have realized is that a single set of standardized metadata fields, no matter how well designed, will always be too limiting as our systems and capabilities continue to grow.
Pain: Our legacy CMS is limited in its ability to work with or make use of non-standard metadata fields which has always been a pain but it has been something we have learned to work around - even using creatively structured file names as a last resort. Unfortunately, our needs are becoming too complex to rely on these sorts of last-minute workarounds. What we have realized is that a single set of standardized metadata fields, no matter how well designed, will always be too limiting as our systems and capabilities continue to grow.
Pill: Openstore, Custom data fields
Pill: Openstore, Custom data fields
Description: The ability to incorporate unlimited custom data fields into Openstore’s existing metadata structure enables your teams to capture and organize your content using customer-specific and context-specific information that is otherwise not supported by your legacy platforms’ metadata fields. This forward-looking flexibility ensures that you will always be able to tailor the metadata system to suit the unique needs of your customers and content types, improving both data accuracy and relevance which is especially important as exploding AI capabilities continue redefining the boundaries of what it means to be the best.
Proof: By removing the limitations on how we could use our metadata we’ve been able to fix issues we’ve had to previously work around with older software packages which is already having an effect on the accessibility and searchability of our content repositories. Looking forward, we are testing AI solutions which would use the open metadata structures to even greater effect. Overall we feel this relatively small change of removing our metadata limitations will have an outsized effect when we’re called on to adapt to new and rapidly changing additional business needs.
Is used when standard fields are not sufficient for customer-specific metadata requirements
Added to Openstore standard metadata fields
Can be used for, search, indexing and info
Added via OpenstoreWeb GUI by users with system admin permissions
Also called extra data, available via OpenstoreAPI calls
Pain: Traditionally our workflows when preparing images for print involved several manual steps, including image selection, adjustments, and sending the images to our prepress teams for final handling. This could be time-consuming and prone to errors but was required to ensure quality and consistency. Individual handling of images through InDesign was not a complete solution for this as we still encountered issues which had to be corrected before production which caused delays and increased costs.
Pain: Traditionally our workflows when preparing images for print involved several manual steps, including image selection, adjustments, and sending the images to our prepress teams for final handling. This could be time-consuming and prone to errors but was required to ensure quality and consistency. Individual handling of images through InDesign was not a complete solution for this as we still encountered issues which had to be corrected before production which caused delays and increased costs.
Pill: Openstore Autorepro, AWS S3
Pill: Openstore Autorepro, AWS S3
Description: By automating the repro process through Openstore's Autorepro mission, the company streamlines the process of preparing images for print. This workflow automatically converts images into print-ready versions, removing the need for manual image adjustments and ensuring consistency in quality and format. This can significantly improve your image workflow efficiency, reducing time spent on manual tasks and minimizing errors in the print preparation process.
Proof: This greatly improves workflow efficiency, reducing time spent on manual tasks and minimizing errors in the print preparation process.
This project has improved both our image and workflow automation and been a real boost to our production scalability. By automating our image preparation for most images we have been able to reduce the workload on our repro team while ensuring consistent image quality, and streamlining collaboration. Integrating all this with our Amazon S3 cloud storage has made everything simpler to manage, improving efficiency and helping us to keep pace with increasing production demands while maintaining production quality, meeting deadlines and maintaining our current headcount.
User selects image and place image (not print ready) in document
User orders Openstore autorepro mission within Indesign
Openstore Autorepro creates print ready copy of image and place it on Amazon S3 storage
Openstore notifies Indesign that the image is ready and Indesign replaces temporary (not print ready) image with print ready image
Openstore can via AI summarize a text and use this to give users suggestions for images that might fit the text they are writing.
User edits article/text in CMS system
CMS system sends article text to OpenstoreAPI
Openstore uses AI to obtain an *embedding vector for the article
The embeddingas vector is then used to get images with similar embeddings vector via Openstore image search
The suggestions of images is presented to the user and user place the image of choice to the article
*) Text embedding (the same as word embeddings) is a transformative technique in natural language processing (NLP) that has improved how machines understand and process human language. Text embedding converts raw text into numerical vectors, allowing computers to understand it better.
Images can come in with insufficient or missing description, this can be remedied by using AI to describe the images better, which increases the searchability of them in the system.
Images are added to Openstore
Openstore timer function send new images to AI analyse via OpenstoreAPI
OpenstoreAPI gets result from AI and adds the enriched description to images
OpenstoreAPI also updates the image *embeddings to enable Text search of images
What information AI should focus on is set in the configuration file to Openstore
*) Text embedding (the same as word embeddings) is a transformative technique in natural language processing (NLP) that has improved how machines understand and process human language. Text embedding converts raw text into numerical vectors, allowing computers to understand it better.
Keywords: Openstore,AI, Article, Audio, Translate, MP3, WAV
Regardless of the language article is written in, Regardless of the language article is written in, Openstore can translate articles into another language and then convert the text into speech.
User search articles in Openstore
User select one article, and clicks on "Get audiofile in french"
OpenstoreAPI Compiles the article, and asks the AI to translate it into French, then Openstore asks the AI to make an audio file of the translated text.
Page updated
Report abuse