Data Protection and Site Exports


Data Protection

Metro Publisher systems team works hard to keep your data secure. 

We are constantly upgrading and maintaining our systems. This includes periodic complete back ups combined with maintenance of a continuous point in time recovery (PITR) log stored in Amazon’s S3 storage service.


Content Export

You may wish to complete a full website export at some time, so we have compiled the options you have for downloading your website here.


1. Simple Content Export


To do a simple export of your Content you can use the "Add" button at the bottom of the Content Exports admin page here:

That will not export your content with images; it will export as XML/HTML (e.g. for InDesign) or a spreadsheet file.

Your Locations can be exported in the same manner here:

For Files, there is a "download" link at the bottom of the Files overview page:

That requires multi-selecting the files you wish to download.

2. Full-Content RSS Feed

We recently introduced a new full-content RSS feed option:

You can use that feed for importing content into other CMSs/databases in some cases - it's just a question of generating the feed links.

However, the feeds only pull published articles and don't include tags.

3. Full Export via the Metro Publisher API

You can also export your entire database if you have your own developer at hand using our API:

This is the script we use:

We can also do that for you as a custom service (1-2 billable hours). This API export would include everything the API provides: content, files, locations, section (data), redirects, and comments in a format that a developer can work with.

The format of any API export isn't legible with standard word- or image-processing programs. It is in the .json file format, so you would need a developer to create a new site from the format your database would be in.


Please note that an article isn't just a single JSON file; it is made up of a JSON file and subfolders with files for media and tag JSON.

Here is an example for just the tags of an article:

[{"url": "", "predicate": "describes", "uuid": "0279f18e-8b09-11e6-940c-0a161eac8f79", "title": "omaha public library"}, {"url": "", "predicate": "authored", "uuid": "e65ee893-ca46-5ce2-a75c-17127aecd1b8", "title": "Ryan Syrek"}, {"url": "", "predicate": "describes", "uuid": "0587aaa6-8b09-11e6-940c-0a161eac8f79", "title": "fundraiser"}, {"url": "", "predicate": "describes", "uuid": "34c093de-6ff7-11e4-9795-14109feab130", "title": "Film"}]

API information about media (images etc.) on content is listed here:

Exporting via the API for the .json version of your site will only supply slot-tags for your content since .json is a text-only file. The connection between content and images has to be made separately.

A sample JSON file is uploaded here (and attached to this article):

When we generate this file, the content will contain something like this:

<slot id="aaaaaaaa-aaaa-aaaa-aaaa-111111111111" /> 
<p>In May, it was time to plan for this year's vacation.</p> 
<p>I've always wanted to visit Rome, so I decided now would be the right time for a trip there.</p>
<slot id="aaaaaaaa-aaaa-aaaa-aaaa-222222222222" /> 
<p>The view from my hotel room was amazing.</p>
<p>All in all, I had a fantastic time.</p> 
<slot id="aaaaaaaa-aaaa-aaaa-aaaa-333333333333" />

Then there is a media.json file for the content:

[{"thumb_mimetype": null, "slot_uuid": "78667b01-e1e3-4f20-df4d-fcf6eb458a64", "image_mimetype": "image/png", "title": null, "thumb_uuid": null, "content": null, "image_url": "", "image_uuid": "5e6d6e5a-d26f-11e6-9c81-0aea2a882f79", "thumb_url": null, "type": "file"}]

That file has a 5e6d6e5a-d26f-11e6-9c81-0aea2a882f79.json with:

{"credits": null, "modified": "2017-11-16T19:44:28.377600", "title": null, "filename": "300x100.png", "description": null, "download_url": "", "byte_size": 128, "uuid": "5e6d6e5a-d26f-11e6-9c81-0aea2a882f79", "created": "2017-01-04T11:17:24.863838", "mimetype": "image/png"}

And there is a file, which is the actual file.


Have more questions? Submit a request


Powered by Zendesk