Bug 182278 - Allow to create secure semantic vaults
Summary: Allow to create secure semantic vaults
Status: RESOLVED INTENTIONAL
Alias: None
Product: nepomuk
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: unspecified
Platform: openSUSE Linux
: NOR wishlist
Target Milestone: ---
Assignee: Sebastian Trueg
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-29 11:29 UTC by Aaron Digulla
Modified: 2019-02-23 22:37 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Aaron Digulla 2009-01-29 11:29:17 UTC
Version:            (using KDE 4.2.0)
OS:                Linux
Installed from:    SuSE RPMs

I'd like to be able to create secure "vaults" while working with some nepomuk-aware application. For example, when I'm working in accounting for several customers, I do not want information from customer A to pollute the vault of customer B.

When I'm working on something private, I might not want to see this data show up in my work vault.

Note: This bug is for tracking the ground work - just being able to create and maintain vaults. When this is done, there will be a new bug to track how to use this feature in the UI (switching vaults, maybe creating virtual vaults or joint vaults).
Comment 1 Vishesh Handa 2013-06-10 12:16:43 UTC
Marking this as WONTFIX.

While this feature seems like a nice feature, the Nepomuk development is not going in a direction where you can have multiple databases and each database can be used to store separate information. That's just not something we ever plan to do.

You can possibly write an application to store customer data in Nepomuk, but each customer will have to be stored in the same database. Or you could choose not to use Nepomuk and just run your own database via Soprano.