Tobi Stadelmaier

Syncing Content with Studio Hub

9. August 2018 / Tobi Stadelmaier / TechTalk

Did you make it to CoreMedia’s Developer Conference this year? If you didn’t, well, you definitely missed out. If you did, you might remember our little competition for our Labs platform: We asked the community for ideas for useful and cool features they’d like to see in Labs, and promised that the best idea would actually get implemented.

The winners are Daniel Stephan and Constantin Erckenbrecht from our much valued partner init, who were nice enough to point us to an issue that’s been a traditional headache in many projects: How can a casual user conveniently transfer content between CoreMedia environments (for example, from a Dev system to UAT, or the other way around)? Of course there’s always been server export/import, but that’s a developer tool, and as such pretty much keeps the “casual” users out of the game.

Enter CoreMedia Studio Hub.

If you’re not aware, Studio Hub basically lets you “mount” various data sources into Studio so you can work with them seamlessly, as if they were stored in CoreMedia itself. Currently, implementations are available for Amazon S3, Dropbox, YouTube, RSS Feeds, and local filesystems. You can configure any number of them in your Studio instance, and once you do, the data sources appear as separate tree nodes in the Studio Library. There’s an extensible preview and, of course, you can interact with the CoreMedia content repository by just dragging, say, an image stored in an S3 bucket into a CoreMedia folder, and a respective content item will be automatically created.

This is now also possible for other CoreMedia repositories. Syncing content works for single content items as well as for entire folders, which will then be copied recursively.

Of course, this implementation raises a few interesting questions with no obvious answers. For example, consider a situation where you transfer an entire subfolder to your primary repository, and one of the content items from the “source” repository links to an item outside of that subfolder. What should happen to this link once the respective content item is created in the target repository? One possible approach would be to check if the target repository has a content item with matching name and path than the original one, and then have the newly created document link to that one. But whether or not that is the right thing to do very much depends on your specific use case.

So why don’t you take it for a spin and tell us what you think? We’d love to get some feedback on this, and yes, we’re also open for pull requests.

 


Tobi Stadelmaier

Tobi Stadelmaier

Vice President Engineering

As VP Engineering, Tobias Stadelmaier leads CoreMedia’s engineering department, helping our highly motivated team of experts to develop great CoreMedia products. Responding swiftly to customer requirements and adapting nimbly to changes in the market, Tobias and his team are proud of their record of delivering customer-ready innovations. Tobias started his career at CoreMedia in 2001 as a Technical Consultant and worked for three years as a Delivery / Engagement Manager and Product Owner. After a detour into the games industry as a Senior Product Owner, he returned to CoreMedia in Summer 2016. Tobias Stadelmaier holds a degree in Political Science from the University of Bamberg, Germany.

More posts

Beating the Odds: Our Week at IBM Think

For CoreMedia, March means Vegas. Specifically the two major trade shows that take place there: Shoptalk and IBM Think. For our impressions of Shoptalk, see the post here. For impressions of IBM Think, read on! IBM Think, which took place March 19-22 in the Mandalay Bay Convention Center and MGM Grand Hotel in Las Vegas,...

Read More

Recommended Read #2: Small is the New Big

The increasing presence of "microservices" is having a major impact on online retail, including the ability to influence engagement, loyalty, and sales. But what exactly are microservices and why do they matter? We share two must-read posts that explain.

Read More

CoreMedia Labs Extensions

Introducing a simplified way of building extensions into your CoreMedia system from other sources: Just use our OOTB integrations and features to enhance your CMS without having to store or maintain the source code. All the configuration for CoreMedia Labs extensions is done via the settings in Studio, which means there’s no need to alter...

Read More

Post a comment

SIGN UP

Add your name and email address to sign up for our CoreMedia Blog and Industry Newsletter and we will keep you posted about upcoming events, product enhancements and news about CoreMedia.

We promise to keep your data safe and you can opt out at any time.