-
Notifications
You must be signed in to change notification settings - Fork 7
Description
Description
Q: What is the name of the feature?
A: Search
Q: What does this feature enable the user to do?
A: Search available pathways (from Biofactoid)
Q: What information must the user provide to use the feature?
A: Query term
Q: What are the applicable constraints, e.g. compatibility or performance?
A: Provide access to pathways submitted to Biofactoid (public). The downside of redirecting to another search service is that the information will not be as up-to-date as would be the case with biofactoid.org, although, this too has changed (#1304 - updates nightly).
Specification
This was never meant to be a long-term solution, but rather provide some access to the valid user-submitted Documents beyond the limited number in the carousel. The intent was to offer some feedback to an author that their data didn't just end up "nowhere" but rather some tangible, publically accessible location.
The current search engine uses an in-browser implementation. This means the browser loads the entire public data (>5MB) every time someone visits the site. Given the growth, albeit modest, of the resource (~500 Documents) this puts tremendous load on the server and has necessitated a bunch of hacks to ensure the app is responsive and available (e.g. caching see #1304).
Mockup
Details
