You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the "property" search in Vanilla APIS seems to use the display name of each propert: e.g. searching for the place of birth with "place" does not return anything, while search with "Ort" returns 19 hits. Should we make this more "intuitive" by having an autocomplete for this search option that selects one precise property by using several descriptive texts of the property?
The text was updated successfully, but these errors were encountered:
GVogeler
changed the title
support property search in Vanilla APIS by extende autocomplete
support property search in Vanilla APIS by extended autocomplete?
Nov 12, 2023
I have absolutely no idea how this is working (or why "search by property" is even a thing); I guess it does what it says, and is searching for properties that this "Birth Event" has — and one of the allowed properties of "Birth Event" is "Ort" (not "place").
I suppose on second thoughts that this makes sense with "normal" (non-factoid) APIS models: i.e. show me all the persons who have a property "has brother". But this makes no sense with statement-oriented models: "show me all the birth events that have a place of birth" doesn't seem like a useful question to ask. You'd want to ask "show me all birth events where place of birth is Wiener Neustadt" (or something); but we can't do this with current APIS, as it's two property traversals (i.e. a graph query, not a model query)
Currently the "property" search in Vanilla APIS seems to use the display name of each propert: e.g. searching for the place of birth with "place" does not return anything, while search with "Ort" returns 19 hits. Should we make this more "intuitive" by having an autocomplete for this search option that selects one precise property by using several descriptive texts of the property?
The text was updated successfully, but these errors were encountered: