Download results

[MelaniePhilofsky]

Expected behavior: Ability to download all the concepts from a domain, class, and/or other narrowing feature

Actual behavior: The "Download results" button is greyed out and won't allow download of the concepts

Steps to reproduce: From the drop down menu on the Athena home page, select domain = Type Concept and the Vocabulary = Procedure Type. The"Download results" button isn't active

[marpozh]

Thank you for your report! Will fix. As a workaround, I suggest to enter "Procedure" in the "search by keyword" field (or some word which is in all result concepts) and the button will become active. BR

[cgreich]

Aren't we merging Atlas with Athena at some point, and there you can select an entire vocab easily?

[gklebanov]

Christian - not sure if you meant "merging" the way I read it or "integration" - here are some thoughts:

1) It would not make sense to merge ATHENA and ATLAS since they are playing very different roles:

• ATHENA is a repository and distribution system of OMOP CDM vocabs (classic MDM). ATLAS is an analytical that consumes vocabs, it is one of the consumers. Actually, not even directly but rather can consume one of the vocabs from OMOP CDM data sets that is points to.
• The vocabs in ATHENA are always the greatest. ATLAS consumes whatever is in OMOP CDM

2) What we have been discussion, is to have a better "integration" between ATHENA and OHDSI "sites":

• be able to notify the sites about new vocabs available, and then download vocabularies into the local site with a button click. Have an ability then to automate the install and refresh process from the UI
• the challenges are: a) many site policies simply restrict external communication to the internet. So, we still need to cater for manual use case b) ATLAS is an analytical tool. Then there is ARACHNE - the research network tool. I think there should be an integration with the local "site data source manager" component that would be shared across ATLAS, ARACHNE and OMOP CDM instances allowing to configure and manage these instances, including the possibility to get and install new vocabs and automate "light" refreshes out of that. Actually, we already started working on creating a common data source manager component that will be shared between ATLAS and ARACHNE

[mik-ohdsi]

Bumping this one up:

Can we adjust the behavior of the download results button with a threshold taken from the number of total items currently in the search results instead of the number of characters in the search field? Thanks ~ Mik

[cgreich]

It would not make sense to merge ATHENA and ATLAS since they are playing very different roles:

I am not talking of merging the tools. One is for downloading, the other for exploiting. I am talking about the search function and UI. Atlas needs to be as fast as Athena. Of course on the basis of the local vocab, which may not be the latest.