There are many ideas on how to improve the Nepomuk system or on how to use it. This is the place to list them all.

+

−

+

−

Feel free to add your own ideas. Please leave your name in case someone wants to contact you for details or a discussion of the idea.

+

−

+

−

+

−

+

−

=== Use Nepomuk in the KDE Menu ===

+

−

One could think of using nepomuk search in the KMenu to look for applications or even files or persons.

+

−

+

−

=== Remember Usage of movie/sound files ===

+

−

Media players such as Dragonplayer or Amarok could remember when movie/sound files have been watched/listened to. The last time is interesting but maybe also a history.

+

−

+

−

In any case, it allows to quickly access unwatched episodes.

+

−

+

−

=== Tool to gather annotation statistics about selected files ===

+

−

Quoting [http://trueg.wordpress.com/2009/05/21/your-our-nepomuk-ideas/#comment-303 blog comment] as an example: ''"I am using Nepomuk to tag/rate schoolwork from my students. For every paper/file I tag it with seen/unseen and rate it with the actual grade I want to give (0-5). When I have seen them all, I collect the results into a spreadsheet. It would make my life (even) easier if, by selecting a bunch of file I could have a summary (one I could save in some text form) of all ratings/tags for each file in the selection."''

+

−

+

−

One could think of an action in Dolphin (for a first prototype this is always a good idea) which triggers a collection of all metadata which is then layed out according to the user's wishes: html, plain text, odt, whatever.

+

−

+

−

=== Add support for qualified links/relations ===

+

−

+

−

This is a somewhat low-level idea with no visible results as long as applications don't use it, but I think that having it implemented would allow for some nice possibilities.

+

−

+

−

Basically, the goal is to have some generic way of attaching a "quality" to any “thing -- property” assignment, in order to cope with the varying credibility/certainty of different meta-data collection methods such as user input, heuristic algorithms, circumstantial guesses, etc. in a transparent and unified way.

+

−

+

−

This would among other things allow implementing many automatic-data-collection ideas like NLP-support in a more user-friendly (that is: non-intrusive) fashion.

+

−

+

−

For more details & discussion see [[Projects/Nepomuk/Qualified Relations Idea]].

+

−

+

−

=== Folder Cloud in Dolphin/KDirOperator ===

+

−

Using information from the Nepomuk DB about usage frequency of folders (or the files within) it would be nice to have the folders be presented in a cloud. More often used or more important folders would appear bigger.

+

−

+

−

This is a nice idea originally posted on [http://www.kde-look.org/content/show.php/Folder+Cloud?content=101521 kde-look.org].

+

−

+

−

+

−

+

−

=== Nepomuk based backup system ===

+

−

Nepomuk has a huge potential for an intelligent backup system. The point here is that Nepomuk could "know" that a certain file on a certain device is the backup of a local file. Then, when the device is available it would trigger an automatic update of the backup.

+

−

+

−

The user could, for example, just tag a folder with "Backup" (better use a dedicated ontology) and the system would ask where to back it up and perform all the necessary tasks. Backup history and recovery could then be done inside the Nepomuk resource. The key point here is really the fact that the system would "know" what a backup is, recognize one when it sees it and know what to do with it.

+

−

+

−

=== Nepomuk based versioning system ===

+

−

This is partly related to the backup system. User should be able to tag a version of a file, a bit like in svn. When opening a file, there could be a list of saved versions, in case user wants to revert changes or something like that.

+

−

+

−

This could even be combined with automatic detection. For example in email: somebody sends you the second version of a paper which is then saved. It would be great to remember that the new file is the second version of the first one. Then the system could warn if one opens the older version.

+

−

+

−

=== File Boxes ===

+

−

There is a nice idea about file boxes which allow to temporarily group files to perform some actions on them here: http://bugs.kde.org/show_bug.cgi?id=200461

+

−

+

−

This could be done using Nepomuk. I am not sure, however, if Nepomuk is really the correct choice here. Maybe a simple kded service and a KIO slave nicely integrated into Dolphin and the file dialog would be sufficient.

+

−

+

−

=== Categorize new files ===

+

−

'''We already have the fileannotation service in [http://websvn.kde.org/trunk/playground/base/nepomuk-kde/fileannotationservice/ playground]. This is the basis for the idea below as it already implements parts of it.''

+

−

+

−

Let Strigi emit a D-Bus signal on new files (only after the initial indexing so we do not get signals for all files) that appear in typical document folders (so we do not get signals on temp and log files and the like).

+

−

+

−

When a new file appears propose to relate it to the current Nepomuk context (the context service is in playground: a very simple one only maintaining one URI which is the current context and can be any resource. Typically, however, it would be a project or task or event).

+

−

+

−

Also use the information extracted by Strigi (mostly nie:plainTextContent and nie:description and nie:name) to generate annotation suggestions through Scribo and propose them to the user, too. This could be done via notifications (in a first version) and later in a nicer plasma GUI.

+

−

+

−

Here rating of the suggestions is important. Nepomuk::Annotation already provides a relevance() method but most plugins' relevance generation code is rather simple and could use improvement.

+

−

+

−

'''''Hints:'''''

+

−

* If the above "''Add support for qualified links/relations''" idea were implemented, the user would not have to be bothered to confirm the relation of the new file to the current context. You could just add it as a weak relation ('found by circumstancial evidence'). The user could always confirm it at a later point (e.g. in dolphin) to turn it into a strong relation.

+

−

+

−

=== FIXME: add your own ideas ===

+

−

+

−

==== Linking between documents ====

+

−

I usually deal with lots of scientific papers in the form of searchable pdf's.

+

−

My idea is twofold:

+

−

1) Have a 'Google scholar' type search that allows me to see the relations between papers and retrace an idea to its original author.

+

−

2) Each paper refers to a few other that I might have already on disk. My idea is to have okular integration such that when I click on a reference it opens the respective file based on author, date, journal, etc.

+

−

+

−

==== Push tag clouds on the web ====

+

−

+

−

I'd like to save my tag cloud on the web so that when I change computers, I still have my tags. There should also be serveral projects which wikify tag cloud creation and which would serve updates via some kind of RSS feeds. Think of it as some sort of Digg for both online and offline desktop items.

+

−

+

−

=== Augment menu toolbars with semantic search ===

+

−

Ideally, eliminate the use of menu toolbars, rather have a powerful semantic search to query for a given functionality/action etc.

+

−

+

−

=== Pure semantic desktop environment ===

+

−

A minimalistic desktop environment solely based on semantic search. Ideal for small screens (e.g. netbooks/smartbooks), all functionality is accessed via semantic search, rather than the usual assortment of menus or application icon panels. A rather intuitive UI. The user 'talks' to the computer. In essence this takes the idea of beagle/krunner/gnome-go like idea to the next level. Combined with the replacement of toolbar menus, it makes for an efficient use of screen space with an uncluttered UI, plus shifting the input method more to the keyboard side, which can be beneficial to netbooks/laptops on the move (when you don't want to rely on a mouse)

+

−

+

−

=== Link Pictures to Persons ===

+

−

+

−

Apple already did it the really fancy way: face recognition + linking of faces to people.

+

−

+

−

We do not have face recognition yet but we can link pictures to persons. Akonadi pushes the contacts in the address book to Nepomuk as nco:PersonContact instances. We can simply use those to allow linking to images.

+

−

+

−

In playground we already have peopletag which allows to define a region. It would make more sense to integrate it with Gwenview.

+

−

+

−

The ontology to use it still an issue. After all we want to easily handle

+

−

+

−

* The direct link between the image and the person

+

−

* The region in the image

+

−

+

−

Dolphin should be able to display the information, too, i.e. the name of the person, maybe even with a link to the address book.

+

−

+

−

+

−

=== Automatically annotate system files ===

+

−

+

−

The example is wallpapers. Installed wallpapers could automatically be marked as begin of type "Wallpaper". This would also require an ontology which includes the term Wallpaper based on PIMO.

Events

ToDo

Nepomuk is a rather young project with a notorious shortage in developers. There are many tasks and subprojects to get ones hands dirty on. Unlike other projects like Plasma, however, developing for Nepomuk is not easy. One has to read up on a lot of things and fight some day-to-day annoyances. But: helping with the development will improve the situation in any case.

If you are interested in working on a task in this list, please contact Sebastian Trueg.

Junior Jobs

If you want to get into Nepomuk development quickly by taking over a small task have a look at our Junior Job page.

Low level Nepomuk Development Tasks

The low-level development tasks are those that are not directly reflected in the GUI or even in the API used by most developers. However, they are important in terms of performance, scalability, and compatibility.

Add Inference Configuration to the Virtuoso Soprano Backend

Virtuoso 5 provides inference on rdfs:subClassOf and rdfs:subPropertyOf. These are the most important ones and for now all we need in Nepomuk.

The current implementation of the Virtuoso Soprano backend does not enable inference. We need a configuration option to do exactly that. It could happen along the lines of the existing config options or with the introduction of dedicated inference configuration options on the Soprano::Backend level.

Soprano Transaction Support

Soprano is the RDF database framework used in Nepomuk. Currently Soprano does not support transactions, i.e. sets of commands that can be rolled back. An experimental development branch exists which already contains new API for transaction support (while keeping BC).

It still misses an implementation of the transaction support in Soprano backends (Sesame2 and Virtuoso) and in the client/server architecture.

Another idea is to create a new API based on the design that Sesame2 follows: Repository and RepositoryConnection classes. The former creates instances of the latter which then has all the actual data handling methods and acts as one transaction object.

General Nepomuk

Handling of external storage

We already have the removablestorage service in kdebase which handles USB keys and such to a degree.

A typical problem with the way Nepomuk handles files and file metadata are removable storage devices. They can be mounted at different paths on different systems. But still one wants to keep the metadata stored in Nepomuk. If possible one would even want to be able to search for files saved on an USB stick even if it is not plugged in.

However, one actually needs more. The system would have to be embedded into KIO to make sure the metadata cache on the removable storage device is always up-to-date. Also it is directly related to the problem of relative vs. absolute file URLs.

Nepomuk Backup Service

We need a backup solution. The idea is the typical one: have a Nepomuk service that allows to specify update intervals and manual updates.

The service should ignore all data extracted by Strigi, i.e. data that can be recreated deterministically. This can easy be determined by checking the context/named graph the data statements are stored in. Strigi stores all extracted data in one context which is marked as the http://www.strigi.org/fields#indexGraphFor for the file in question. Thus, a query along the lines of the following would work: