** Attachment added: "Zeitgeist plugin for decibel v2"
http://launchpadlibrarian.net/48420809/Zeitgeist.py
--
Send events to zeitgeist
https://bugs.launchpad.net/bugs/579972
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgei
Thanks for the comment. I applied the changes. Some thoughts:
Is it better to use Interpretation.MUSIC or Iterpretation.AUDIO?
I found out that in python the batteries really are included ;) You can do:
import mimetypes
mimetype, encoding = mimetypes.guess_type(filename, strict=False)
Wouldn't i
We implemented this kind of differentiation with the ontology branch we
landed some time ago.
** Changed in: zeitgeist
Status: Confirmed => Fix Released
** Changed in: zeitgeist
Assignee: (unassigned) => Markus Korn (thekorn)
--
Separate Interpretation/Manifestation into different g
I think with our ontology stuff we can consider this bug as fixed.
** Changed in: zeitgeist
Status: In Progress => Fix Released
--
Event Interpretations Ontology
https://bugs.launchpad.net/bugs/489262
You received this bug notification because you are a member of Zeitgeist
Framework Team,
I think I got the negation part working in
lp:~thekorn/zeitgeist/negation_support
Before a merge, this branch needs a few more tests, I hope to work on it
tomorrow early morning.
After I got this branch landed I will work on the wildcard part.
** Branch unlinked: lp:~thekorn/zeitgeist/negation_s
Here's a quick review of the plugin. I can't comment on the Decibel
parts, just on the ZG integration parts:
* You can set the subject origin to the parent folder of the URI. You can just
use os.path.dirname(uri)
* It's a good idea to figure out the mimetype for the subject. You can fx. use
g
I added the zeitgeist data-sources project to the bugreport. Could you
guys please tell me if I have done everything correctly in the zeitgeist
plugin?
** Also affects: zeitgeist-dataproviders
Importance: Undecided
Status: New
--
Send events to zeitgeist
https://bugs.launchpad.net/bugs
The proposal to merge lp:~thekorn/zeitgeist/negation_switch into lp:zeitgeist
has been updated.
Status: Needs review => Rejected
--
https://code.launchpad.net/~thekorn/zeitgeist/negation_switch/+merge/16416
Your team Zeitgeist Framework Team is requested to review the proposed merge of
lp:~
I'll not support Subject.text for now, but make it easy to add this
field.
I mean when I look at my database for the values I've there it turns out
they are very random, like title of webpages, like "Television program
of 2010-05-12, 4 - 5 p.m", negation support make close to no sense for
this cas
I think it makes perfect sense what you laid out. The only thing I am
considering is subject.text. I am not sure whether or not to add
negation and/or prefix queries for that one...
--
Using filters (text match / exclusion / etc)
https://bugs.launchpad.net/bugs/485966
You received this bug notifi
I will start hacking on this again today, a plan to split it into two
parts.
1.) I will start with negation
2.) the next step is wildcards
There are still a few open question to me:
wrt 1.)
* for which fields do we allow negation?
- Subject.{Uri, Interpretation, Manifestation, Origin,
11 matches
Mail list logo
