Closed mpoelchau closed 3 years ago
Hello @mpoelchau
The first thing that comes to mind is to create a Tripal Field. By creating a field and attaching it to the entities that should be linked to in the results, you'll be able to tell the entities indexer to consider it and at the same time tell Tripal to not display it.
Please let me know if this helps
To clarify, Tripal Elasticsearch allows you to choose which fields to index by visiting the Tuning Form
at /admin/tripal/extension/tripal_elasticsearch/tuning
or from the admin menu -> Tripal -> Extensions -> Tripal Elasticsearch -> Tuning.
The fields are already associated with this content type, and they display on the page as currently configured. Here's a screenshot of the fields that are displayed for the gene bundle:
And here are some of those properties on a gene page:
Can you try visiting the tuning form and make sure the field is set to High Priority?
Thanks @almasaeed2010 we totally missed the tuning page. I believe that should do what we want! We still need to test but I'll close the issue for now.
This is not really an issue but a question about custom indices. We'd like to index additional fields for bundles beyond the default provided by the entities indexer. For example, there is a lot of information in the featureprop table associated with our genes and mRNAs that users will likely search for that need to be included in the index. We've looked at the interface to build custom indices, but when we select the chado_bio_data_x table associated with the bundle type (e.g. gene), only the fields from that table are shown as options for indexing (mapping_id, entity_id, record_id, nid - whereas we'd want to index particular cvterms, not to mention many fields from the feature table).
How would you recommend indexing additional fields for different chado bundle types? Will this require a code change?
Thanks for your help with this!