Bug 207273 - sysadmin documentation for nepomuk
Summary: sysadmin documentation for nepomuk
Status: RESOLVED UNMAINTAINED
Alias: None
Product: docs.kde.org
Classification: Websites
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Unspecified
: NOR wishlist
Target Milestone: ---
Assignee: Documentation Editorial Team
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-13 19:06 UTC by Michal Svoboda
Modified: 2017-04-02 15:29 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michal Svoboda 2009-09-13 19:06:02 UTC
Version:            (using KDE 4.3.1)
Installed from:    Unspecified

I am unable to find any documentation of the semantic desktop/nepomuk/strigi machinery from the sysadmin's point of view. For a few basic examples, I was not able to find answers to these questions:

1) Where are tags/ratings stored? Where is the indexer's database stored?

2) How do these two relate?

3) Can the locations and/or methods of storage be configured?

4) How does one do backups of these storages?

5) What are the tools to manipulate/examine/repair those storages?

6) Can these storages be shared between users on the same machine? How?

7) Between users on the network?

8) Are there any access controls for those storages? How granular?
Comment 1 Anne-Marie Mahfouf 2009-09-14 13:00:24 UTC
Where do you want that doc please?
Comment 2 Michal Svoboda 2009-09-14 16:22:08 UTC
(In reply to comment #1)
> Where do you want that doc please?

I'd prefer a googlable location, plus a link at http://nepomuk.kde.org/node/2 (ie. nepomuk->documentation)
Comment 3 Michal Svoboda 2009-12-14 20:00:34 UTC
Are we moving somewhere with this report?

C'mon. You introduce a new load of functionality, with tons of propaganda, but not a word of documentation?
Comment 4 Michal Svoboda 2010-04-12 20:21:58 UTC
Bump. Kick.
Comment 5 Brad Hards 2010-04-13 09:34:40 UTC
Please be patient and considerate of the lack of documentation writer and developer time. 

There is some documentation at http://nepomuk.kde.org/discover/developer which does not fully address your specific questions, but provides pointers that will help you infer the answers, or where you would need to look to find the answers.

Also, you might be able to infer the answers to your questions given the files stored by nepomuk-kde are in .kde/share/apps/nepomuk/repository

[This isn't to suggest that more documentation wouldn't be useful, but instead to help you in the interim. Perhaps you could even write the documentation?]
Comment 6 Michal Svoboda 2010-04-13 18:39:15 UTC
(In reply to comment #5)
> Please be patient and considerate of the lack of documentation writer and
> developer time. 

Time we have all equally - 24 hours per day, it's up to us what we do. The point being, you can devote time to writing the doc instead of whatever else you guys are doing on the project. Needless to say that writing a documentation usually has a purifying effect on the other parts (development, testing).

> There is some documentation at http://nepomuk.kde.org/discover/developer which
> does not fully address your specific questions, but provides pointers that will
> help you infer the answers, or where you would need to look to find the
> answers.

I read that page even before posting this ticket, obviously I was unable to make sense of it.

> Also, you might be able to infer the answers to your questions given the files
> stored by nepomuk-kde are in .kde/share/apps/nepomuk/repository

OK, at least something, that answers some of my questions, but I'm afraid in not a very useful way,

$ less triples-cspo.dat                                   
"triples-cspo.dat" may be a binary file.  See it anyway?                      
^@^@^@^A^@^@^H^@^@^@^@^Q^@^@^X^D^@^@^@^@^@^@^@^@^@...

It means that the answers could be about the following,

1) all the meta data (incl. tags, stars...) are in the .kde dir, which is usually the first one to go ("problems? delete .kde")

2) seems they live together

3) probably not - backend dependent

4) only God knows - is the database open at all times? supports online backup? recovery?

5) probably none

6) probably not

7) oh please :)

8) no

Correct?
 
> [This isn't to suggest that more documentation wouldn't be useful, but instead
> to help you in the interim. Perhaps you could even write the documentation?]

I have no incentive to do so. I hoped to wet my taste by reading the doc. But right now for me Nepomuk & co is totally alien, messy and possibly broken technology, probably not the outcome you'd want to hear.
Comment 7 Luigi Toscano 2017-04-02 15:29:06 UTC
Unfortunately (and sorry for the lack of answers) time passed, and Nepomuk was replaced.