Backup with Metadata

[srloomis]

both the human readable and non-human-readable omit the metadata (comments,keywords, etc)

HR: generate HTML for navigating which includes the metadata

Non-HR: generate text files (or xml?) including the metadata for later import

Note that if the metadata was exported, the HR/non-HR distinction could be removed,as all backups could be made human readable, and machine readable given the metadata.

[steinm]

both the human readable and non-human-readable omit the metadata (comments,keywords, etc)

HR: generate HTML for navigating which includes the metadata

Non-HR: generate text files (or xml?) including the metadata for later import

Note that if the metadata was exported, the HR/non-HR distinction could be removed,as all backups could be made human readable, and machine readable given the metadata.

I agree, that we need some kind of export/backup function which is better than the current one. I personally prefer an export as xml with the ability to export just parts of the dms and import them into a second dms.

Uwe

[srloomis]

both the human readable and non-human-readable omit the metadata (comments,keywords, etc)

HR: generate HTML for navigating which includes the metadata

Non-HR: generate text files (or xml?) including the metadata for later import

Note that if the metadata was exported, the HR/non-HR distinction could be removed,as all backups could be made human readable, and machine readable given the metadata.

I agree, that we need some kind of export/backup function which is better than the current one. I personally prefer an export as xml with the ability to export just parts of the dms and import them into a second dms.

Uwe

well they are different purposes. xml for archival, html for users. I am very interested in clustering/replication to other dms'es