When I select a concept like "antibodies" to build my corpus query within the navigator, is there a way I can see which specific search terms are included?
Is there a way to edit the specific terms associated with a given concept?
Concept search is great, but I need a way to validate the terms employed and possibly tailor them if necessary to find the right content.
In the Navigator tool, the concepts available in the Concepts tab are based on the UMLS dictionary/ontology from the National Center for Biotechnology Information (NCBI). In the UMLS dictionary, the concept “antibodies” includes 26 terms (or surface forms) including “antibodies, antibody, anti-body, unidentified antibody, unidentified ab, etc.”. Each UMLS concept on average contains about 5 terms.
In addition, many UMLS concepts have parent/child/sibling relationships with other UMLS concepts allowing you to expand your search to those concepts and all of their terms. If you click on the white search card for the “antibodies” concept, you will see a set of checkboxes allowing you to include those related terms in your search. By default, the “Include children” checkbox is checked meaning all the concepts with a “child” relationship to the selected concept are included. For “antibodies” there are over 1000 child concepts which translates to over 5000 search terms including specific antibodies like “omalizumab, avelumab, antivenin, Immunoglobulin G, aspergillus Igm, etc.”.
You’ll also notice a checkbox for “Include MeSH concepts”. This is another way to expand your search. MeSH stands for Medical Subject Headings from the National Center for Biotechnology Information (NCBI). MeSH is another dictionary/ontology that applies to the Medline and PubMed documents in the COVID-19 corpus. Checking this box for “antibodies” will include those terms and their children along with the UMLS-based terms.
Related
I am currently trying to implement a web tool with a capable web developer, but we are stuck on one functionality.
It's about draggable nested lists, which should be grouped and sorted automatically according to different attributes.
The "draggable" is not the problem but the automatic creation of parent & child nested lists and the automatic distribution of the products into the corresponding lists.
For a better understanding I have made a
Figma-Prototype, maybe you will understand what I mean.
I have a database of products with attributes like "producer", "product category", "sub-category", "country" and "region". (However the example is just a table, in reality we made the DB in MongoDB)
I want the user to be able to change the order (drag&drop) and also create new lists(Nested-List Parents & Childrens). However, I would like to spare the Users from having to start at 0 and create and fill all lists manually, for example, when it its just about grouping and sorting "only" by product category.
Is this even Possible? We are working with React (MERT-stack).
Thank you!!
We havent an idea where to start, tbh.
I'm new to JSON-LD. I find the syntax fairly straightforward but my query lies more with deciding which pages it is best to add the JSON-LD to. I've spent a bit of time looking for an answer online but so far nothing has been clear.
My example:
The site is for a business that has roughly 20 branch locations across the country. Each office has a dedicated contact details page, and there is also a "contact us" page for the site as a whole.
Should I
A: Add 'Organisation' JSON-LD snippet for the organisation as a whole to the homepage of the site, and then add individual 'LocalBusiness' JSON-LD snippets to each office details page?
B: Consolidate all this into one snippet of JSON-LD that has 'Organisation' with nested 'LocalBusiness'es and place it on ALL office pages, with a separate 'Organisation' snippet for the homepage?
C: Consolidate all this into one snippet of JSON-LD that has 'Organisation' with nested 'LocalBusiness'es and place it on ALL pages sitewide?
D: None of the above... Instead you should ____________________.
I realise there may not be one correct answer for this, but any help at all in achieving what would be considered best practice, would be greatly appreciated!
Cheers
Per the JSON-LD specification, it’s totally up to the authors. Consumers of your JSON-LD might of course have their own expectations.
You seem to use the vocabulary Schema.org, which is sponsored by the big Web search engine services. They are of course typically interested in your page content. The general idea of Schema.org is to mark up your existing content (+ closely related metadata).
This becomes clear when looking at the other syntaxes supported by Schema.org (Microdata and RDFa), as they define attributes that get added to existing HTML elements used for your content. So JSON-LD is the exception here, as it doesn’t get coupled with the HTML/content.
tl;dr: On a page about a branch location, provide structured data about this branch location.
It typically makes sense to provide structured data about related entities (e.g., the parent organization) in addition. This can be done by including the data and/or by referencing it via its URI (see an example). Make use of the properties the type offers (e.g., parentOrganization).
If this question is still relevant to someone, here is my recommendation:
on the homepage, create a "LocalBusiness" markup and use the "department" attribute for each branch.
So in your case, there should be one main office and 19 departments.
For the main office, indicate all attributes (opening hours, logo, image, etc.) For branches, mark up only distinct properties, such as address or telephone (they are apparently different for each branch).
For example, if all branches have the same working hours, no need to repeat them again and again - indicate working hours only for the main office.
Then on each dedicated contact details page add "LocalBusiness" markup only for that specific branch - without departments. You can indicate all attributes in detail.
Do not add "LocalBusieness" sitewide - Schema markup must be relevant to a specific page.
Also, here is an article that can help to understand it better:
https://postelniak.com/blog/local-business-schema-for-multiple-locations/
There you can also find JSON-LD code snippets.
I have website with 2 languages and 2 different categories. I would like to use taxonomy menu on both languages, but I want just to translate these terms to my language and use taxonomy as menu.
When editing taxonomy I have 3 options to pick:
Localize.
Terms are common for all languages, but their name and description may be localized.
It seems that this is solution I'm looking for: I want to have translated terms ad just add nodes and pick category. But this is not working.
Translate.
Different terms will be allowed for each language and they can be translated.
This does not work too.
Fixed Language.
Terms will have a global language and they will only show up for pages in that language.
I don't want to have 2 different terms, I want to have one term translated, so this solution is not for me.
When I say that it's not working I mean, that on when other language is selected, whole page is translated into this language, but not taxonomy menu. I remember that I wrote my own block for displaying it, but then I had to add translated path to each term.
Is there a possibility in drupal to have:
Menu based on taxonomy (for example: taxonomy has terms: Bikes and Cars)?
Translated terms and displayed in menu depend on current site language (for en: Bikes/Cars, for french: Vélo/Auto)?
Translated paths for taxonomy terms (Bikes => bikes, Cars => cars, Vélo => velo, Auto => auto)?
How to manage this?
If I understand your question, localize term is the choice you shoud use but remember to refresh your translation interface on admin/build/translate/refresh after changing taxonomy translation setting.
For menu based on taxonomy, you could use TaxonomyMenu and for localized menu address, i18nmenu is a good choice.
It will work only in 7.x-2.x version with re-introduction of the Add item for Vocabulary option.
https://drupal.org/node/1034310
But check this one also:
https://drupal.org/node/1665308
This is quite an old question, but for people with the same problem as in question (2):
Taxonomies linked to a content type won't show the translation by default (even if you have translated the taxonomy) To show the localized version, you have to change the display options.
Go to structure > content types > (content type)
Click on 'manage display'. There, you have the option to change the format, eg. link -> link (localized)
So I'm not a programmer, but my friend is. He's trying to help me develop a web/phone app but we are stuck because I'm having trouble communicating to him an idea and he is having trouble understanding. One or both of us is a moron ;) Part of the problem is that I don't even know where to search for the answer cuz I don't know the specific search terms...believe me I've tried...and I've searched stack overflow as well. Here is the problem:
Short Question:
Websites (like hotel search) allow you to search for rooms by selecting checkboxes in certain categories (i.e. smoking/nonsmoking, stars, size of bed, near downtown, etc.). Certainly these sites are referencing a large database of hotels in a city.
How can you create a site so that as you check boxes (narrow your search), other options which are no longer available are dynamically "grayed out" or disabled on the fly so you cannot check those boxes. So if I were to check 4 stars and that excluded all smoking rooms based on the database, then the option to check "smoking" would be disabled.
The key to this is that the site is querying a database as you click boxes, then based on the results of that query (which is presumably many rows of data (a subset)), it is analysing that subset of data to determine whether checkbox options should be on/off, then dynamically "graying out" specific options that are no longer available. Once you got to only a single possible result, then the site would pop up the website for that hotel (or some other action).
What is this called? Where can I get more information on this. Any pointing toward the right direction would be tremendously appreciated.
Thanks so much in advance!
Roy
HERE IS AN EDIT TO ORIGINAL QUESTION...HERE IS AN EXAMPLE:
So here is my sample database. Each Column (i.e. AA, AB, AC) represents a checkbox. '1'= True, '0'= False, and '2'= Either. Therefore, if you click checkbox AA, then only the top three rows would meet the criteria of AA=True. So query would return the top three rows. The '2's could be either True/False so since they don't affect outcome, those checkboxes should be disabled and only the checkboxes CA,CB, & CC should remain choosable. If you then click checkbox CB, then result ZYX would be output.
Conceptually, How do you go from the initial click to the point where the database is queried and the results are used to dynamically change the menu. People have suggested javascript but i am not looking for a language. I am more looking for the concept. I was thinking that the query would return a new "temp" array with just the top three rows. Then each column of this "temp" array would be queried to see if it contained a '1' in any of the rows. If it did, then that button would be turned "ON". If it didn't then that button would be turned "OFF". Is this confusing? Am I asking for too much ;)
This sounds like javascript could help. For example, using jQuery, you can dynamically send queries to databases based on whatever you click on checkboxes, and then reload a particular section of the webpage. Javascript can also dynamically disable checkboxes.
I have a similar question to my previous one (Drupal 7 views filter by dynamic taxonomy term), it's only the other way round.
I have a "partner" content type, each with it's own taxonomy term. The other content type is a regular page with multiple terms from the "partner" vocabulary. In my regular nodes, I want to include a few of the "partners" in a view block.
The view should filter only those relevant partner nodes (those tagged with one of the regular node's tags).
Could it be done this way? The problem is that I can't get the term names from URL via contextual filters...
After googling the whole afternoon (and posting it there), I eventually found the answer.
It's based on a tutorial on scito.ch (thanks), with only a few modifications. On the Content: Has taxonomy term ID (with depth) filter, be sure to check the Allow multiple values checkbox. Also (there's a lot of wrong tuts for that), don't specify anything in the WHEN THE FILTER VALUE IS AVAILABLE OR A DEFAULT IS PROVIDED. It's important you specify all those 3 contextual filters.
Hope this helps someone and saves him a sunny afternoon :)