Hey Thad,
thanks for the suggestions!

Concerning keywords in the description field of properties: i think
that is a shortcoming of the current autocomplete API that i'm using,
which is the same one Wikidata uses for the searchbox in the top-right
corner. Apparently they're not indexing those keywords, which makes it
difficult for me to also include them in my search.

I like the suggestion of using the 'that is' part of the rule as a way
to use filter operations, i'll take that into account when i'll be
adding that.

-- Hay

On Wed, Jun 21, 2017 at 2:13 AM, Thad Guidry <thadguidry@gmail.com> wrote:
> I like the idea of Layers of rules... like Photoshop in a way, and then you
> can probably surface quite a bit more.
>
> The one thing that is really lacking is finding properties that have a
> keyword in their description, and not just the label name.
> For instance, typing "person" in a property would give you all the
> properties that have a label containing "person", AND have a description
> containing the keyword "person".
>
> Also, the "that is" should be a drop down element to use other operations
> such as a "filter" or "containing" operation, etc.
>
> Imagine doing:
> "item" has a property equivalent class P1709  "containing"  "schema"
>
> instead of this:
>
> item
>
> has a property
>
> equivalent class P1709
>
> that is
>
> Schema.org Q3475322
>
>  Remove rule Add rule Remove all rules
> -Thad
> +ThadGuidry
>

> _______________________________________________
> Wikidata mailing list
> Wikidata@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikidata
>

_______________________________________________
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata