aude added a comment. I think the next steps are:
- more detailed implementation (perhaps still exploratory) of field mapping builder objects, for exposing the fields to the mapping - more detailed implementation of field indexer objects for populating the fields during indexing TBD: to use them more directly with the available hooks or add some indirect methods/interface in the Content objects. I think it would be quite some more time to get the search code in core and Cirrus to injest these fields in a nice way other than the hooks that exist now. I think the most important next step is to spec out an EntitySearch (or TermSearch) interface, as this is what SearchEntities uses (but the code now is in TermSqlIndex). In exploring this already, it becomes more obvious that we may also want to index meta info like entity type. (although we also know the namespace of the page) TASK DETAIL https://phabricator.wikimedia.org/T117548 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: aude Cc: aude, Aklapper, Wikidata-bugs, Mbch331 _______________________________________________ Wikidata-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
