faq
flatforty
contribute
subscribe
configure
search
rdf
main
parent
thread
|
Re: Nepomuk use case
by Martin on Saturday 09/Feb/2008, @12:29
|
Is there some thinking on how to migrate NEPOMUK data?
Data that is automatically scraped from files or email messages is one thing; you can just redo the scaping. But the other type of data is that which cannot be recreated if the database is lost; for instance user entered tags, and the history of files (where they came from).
For me at least, I would neither manually enter any tags if they will be lost when I switch machines, nor would I make myself dependent on such metadata that cannot be synchronized or at least migrated between machines. Also, I would like control over the synchronization/migration process; I might not want the metadata for my private stuff on my work machine.
Any plan for this? Of course, a prerequisite is that files etc. are primarily identified by checksums rather than paths, which I am assuming to be the case?
Thanks in advance for any info! |
|
|
The Fine Print: The following comments
are owned by whomever posted them.
( Reply )
|
Re: Nepomuk use case
by Lee on Sunday 10/Feb/2008, @13:16
|
There's a command line tool, sopranocmd, which you can query for anything related to a particular file. Tools like star (a modern tar replacement) have long-since supported file attributes. Patching star (or KDE's ark) to support asking Nepomuk/soprano for this data before archiving shouldn't be too hard at all. Worst case scenario, you can manually run the query, save it along with your files, and import it on a new machine. But there's really no excuse for archivers not supporting this stuff as standard. File attributes have been around for AGES in the unix world, and star has no issue with it. They also work fine on other platforms like BeOS, Mac OS, etc.
|
[
Reply To This | View ]
|
The Fine Print: The previous
comments are owned by whomever posted them.
( Reply )
|
|