Backup

The Backup Manager allows for saving myEquivalents data, stored in the currently configured back end.

The dump() method can be used to save mapping data (and information like services or repositories linked to the mappings) into an XML document, while the upload() method accepts a document in the same format, to save the information contained in it in the back end.

The methods require that you use an administrator user, as you can see in the unit tests.

As usually, such interface is available in different back end flavours, like the database back end, or the web services. Probably the most interesting version is the command line interface, which can be invoked this way:

# Backups data in myEquivalents onto a file
./myeq.sh backup dump -u admin -s admin.secret test.xml

# And then upload it
./myeq.sh backup upload -u admin -s admin.secret test.xml

If you use the provenance extension, the provenance register will be populated with entries of type 'backup.restore' when you use the upload() function. These records will be shown to the user currently invoking such function. Please note that backup() does not dump the users associated to a mapping bundle/equivalence class. This is a limit, due to the fact that computing this efficiently is not easy.