| 1 | = Aperture Configuration Service = |
| 2 | |
| 3 | Basically, we need a gui to add datasources, remove them and configure them. |
| 4 | |
| 5 | Also, the crawling behaviour is needed to be configured (crawl every X minutes, etc) |
| 6 | |
| 7 | * Edit datasource config |
| 8 | * add datasources |
| 9 | * remove datasources (including crawled resources from ResourceStorage) |
| 10 | * edit datasources config (including deleting crawled resources) |
| 11 | * Edit crawling behaviour - when, what to crawl |
| 12 | |
| 13 | = auto-configuration and datasource discovery = |
| 14 | |
| 15 | As detailed in UseCaseInstallationGnowsisFindsMyStuff We need a way for aperture to locate possible datasource. |
| 16 | ticket:147 is assigned to hack this. |
| 17 | |
| 18 | This is a bit tricky since it's: |
| 19 | |
| 20 | 1. Platform dependent |
| 21 | 2. Very different for different datasources |
| 22 | |
| 23 | In a way, each datasource implementation should have a method "find"/"location"/"isAvailable" or similar... |
| 24 | |
| 25 | * FileSystem? - this is easy - we just point it at "My Documents" or "/home/username/" |
| 26 | * Thunderbird - again, if the user has a $HOME/.mozilla-thunderbird directory. This changes in different versions of thunderbird... (what version do we rely on anyway?) |
| 27 | * Firefox - same |
| 28 | * Outlook - i know nothing. |
| 29 | * ? |
| 30 | |
| 31 | Maybe this could be a separate ticket for each one? |