MassBank / MassBank-web

The web server application and directly connected components for a MassBank web server
14 stars 22 forks source link

UX/UI: Implementation of a full featured search #289

Open tsufz opened 3 years ago

tsufz commented 3 years ago

Hi @meier-rene and all, I observe that the MassBank ID input field is often used for general search (e.g. for compounds or formulas). We should find a solution to handle this "misuse" of the field. The background is the typical quick search field on many sites. The people expect that they could run a general search using this field.

  1. Catch the false input and give advice that only the MassBank ID is accepted as input value and / or
  2. Redirect other requests to Search template
  3. Enhance the search field to a general search field.

Best, Tobias

tsufz commented 3 years ago

Just an example: image image

The response is misleading. It says two things to me:

  1. No MassBank record exists for Diclofenac (the people might not associate the Accession with the record ID).
  2. There is an error with the database.
tsufz commented 3 years ago

@sneumann @meier-rene @schymane @meowcat, What is your opinion to refine the "Search Field". I see more and more false searches in the field (MassBank ID is the wrong wording anyway as mentioned by @schymane). It is very confusing to the people as a smart search is implemented now on all websites. Therefore, I suggest to refine the search. The people could use general identifiers such as name, accession, inchikey etc and will be redirected to the search mask if their query is not successful for a more detailed search. The Accession search and the error page is not very comprehensive as many people might not know what accession is at all. They want to just lookup for a compound and don't want to get involved in Nerd issues.

tsufz commented 3 years ago

image

takaakin commented 3 years ago

Dear Tobias-san, An easy and quick way to solve the problem is to provide a "User's manual" for the NORMAN MassBank users. Takaaki


差出人: Tobias Schulze notifications@github.com 送信日時: 2021年2月3日 19:51 宛先: MassBank/MassBank-web MassBank-web@noreply.github.com CC: Subscribed subscribed@noreply.github.com 件名: Re: [MassBank/MassBank-web] UX/UI: Refinement of quick search field for MassBank ID (#289)

@sneumannhttps://github.com/sneumann @meier-renehttps://github.com/meier-rene @schymanehttps://github.com/schymane @meowcathttps://github.com/meowcat, What is your opinion to refine the "Search Field". I see more and more false searches in the field (MassBank ID is the wrong wording anyway as mentioned by @schymanehttps://github.com/schymane). It is very confusing to the people as a smart search is implemented now on all websites. Therefore, I suggest to refine the search. The people could use general identifiers such as name, accession, inchikey etc and will be redirected to the search mask if their query is not successful for a more detailed search. The Accession search and the error page is not very comprehensive as many people might not know what accession is at all. They want to just lookup for compound and don't want to get involved in Nerd issues.

- You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/MassBank/MassBank-web/issues/289#issuecomment-772417023, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AED2RH3I2WSF5JWGNBKJTUTS5ETELANCNFSM4WVVJHFQ.

meier-rene commented 3 years ago

For now I added a short explanation and a quick link to the actual search page.

tsufz commented 3 years ago

Dear Takaaki-san, Thanks a lot for your advice. We will think about a more detailed documentation. However, a website and service should be as much intuitive as possible. In general, all websites provide a search field in the position of the Accession search field and thus the users expect the same from MassBank. I guess, even with a manual, some people will hack anything into the Accession search field. Therefore, we think about the implementation of a full-featured text search to help the people to use the website intuitively. Apache already provides a search engine called Lucene and @meier-rene will put some efforts in a useful implementation of a full featured search.

Best wishes, Tobias

takaakin commented 3 years ago

Dear Tobias-san, Now I understand your project to implement a full-featured text search that help the people to use the website intuitively. No user manual might be neccesary. I appreciate very much for your many efforts to improve the MassBank server system. Mass Spectrometry Society of Japan (MSSJ) give us a small fund that is enough to prepare new MassBank records. Currently we have collected 418 new mass spectra for MassBank from MSSJ members. We will submit them to GitHub/MassBank in May 2021. Best regards Takaaki


差出人: Tobias Schulze notifications@github.com 送信日時: 2021年2月5日 0:00 宛先: MassBank/MassBank-web MassBank-web@noreply.github.com CC: takaaki.nishioka.23u@st.kyoto-u.ac.jp takaaki.nishioka.23u@st.kyoto-u.ac.jp; Comment comment@noreply.github.com 件名: Re: [MassBank/MassBank-web] UX/UI: Refinement of quick search field for MassBank ID (#289)

Dear Takaaki-san, Thanks a lot for your advice. We will think about a more detailed documentation. However, a website and service should be as much intuitive as possible. In general, all websites provide a search field in the position of the Accession search field and thus the users expect the same from MassBank. I guess, even with a manual, some people will hack anything into the Accession search field. Therefore, we think about the implementation of a full-featured text search to help the people to use the website intuitively. Apache already provides a search engine called Lucenehttps://lucene.apache.org/core/ and @meier-renehttps://github.com/meier-rene will put some efforts in a useful implementation of a full featured search.

Best wishes, Tobias

- You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/MassBank/MassBank-web/issues/289#issuecomment-773373114, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AED2RH25KOLFUOC43RQTZ4DS5KZBHANCNFSM4WVVJHFQ.