Publish a workflow instantly: we will store it forever
When your workflow is ready for publishing, simply click the Publish permanent public archive menu option, and confirm. You will then redirect to a permanent link to a snapshot, with the URL format:
https://archive.metapage.io/mp/<id>
Keep this link, it’s where your snapshot is stored.
You cannot unpublish: these workflows are stored forever in our public database
To search for archived pages, search with the word: archive:
Provenance
When you clone or publish a metapage, it creates a copy of the existing page. A link to the original page is stored (at [origin]), and displayed next to the page title:
You will be able to run metapage workflows forever
Our commitment to our FAIR principles.
We need two parts to run metapage forever: the website, and the worker agent to power the workflows.
1. The application website forever
- The website that serves archived metapages is served from a different URL and server:
https://archive.metapage.io
- It is published and built from a separate, public, open-source repository:
This means that anyone can fork and deploy the viewer.
Coming soon: viewing zip archives of full metapages and file states.
Coming soon: viewing metapages from URL encoded definitions
2. Compute workers forever
Your archived (and non-archived) metapage workflows still need to run docker containers. By running your worker agent in local mode, and setting your queue in the container metaframes to local mode, there is no server API needed, all your workflows run completely local to your computer running web application.
The worker agent is open source, and published in a public repository
The road ahead: Digital Object Identifiers
We aim to partner with an organization to provide DOIs, connecting permanent metapage snapshots to permanent Digital Object Identifiers.
This will connect researchers workflows to the ecosystem, metapages provide easy digital access to both the metapage workflow content and the associated metadata.