Enable exporting knowledgement database and be able to import it again.
Database operations may lead into store corruptions. It's a good practise to backup knowledge database and be able to recover your metadata again.
Export/Import operations only affects to metadata
Blueprint information
- Status:
- Started
- Approver:
- Tomás Vírseda García
- Priority:
- Essential
- Drafter:
- Tomás Vírseda García
- Direction:
- Needs approval
- Assignee:
- Tomás Vírseda García
- Definition:
- Drafting
- Series goal:
- Accepted for trunk
- Implementation:
-
Good progress
- Milestone target:
- None
- Started by
- Tomás Vírseda García
- Completed by
Whiteboard
Exports are necessary to keep the Knowledge Database safe. At this
moment, Vazaar does not handle SQLite misconfigured or broken databases.
There are two ways to export your Knowledge Database
+ Full backup
+ Export resource(s) manually
In both cases, a PIMO[PersonalIn
user behind that PIM can be guessed (a NCO['Contact'])
Full Backup Format
==================
The Knowledgement Database is serialized into a RDF file whose name is
USER_PIMO_URI. This make easy to know who is the 'owner'.
+ LPATH['
+ metadata/
+ repository/(vazaar resources uris) <- Files
+ etc/vazaar.conf <- Configuration file
+ data <- User data
+ css <- Custom stylesheets
+ icons <- Custom icons
+ plugins <- User plugins
+ reports <- Custom reports
The whole directory is compressed to a tar.gz file but renamed with
.vzr extension in order to specify that is a Vazaar package.
Resulting file looks like:
vazaar-
Exporting resources
===================
Same scheme as above but exporting only metadata and repository for
choosen resources.
Work Items
Dependency tree
* Blueprints in grey have been implemented.
