Page History
Section | ||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
We advertise our Searches as being 'extensions', but in reality it is very difficult (or impossible) for a use to create a plug-in type Search.
Info | | |||||||||||||||||||||||||||||||||||||||||||
|
Design ScopeGForge itemsPlease visit the LexEVS 5.1 Scope document found at: https://wiki.nci.nih.gov/display/EVS/LexEVS+5.1+Scope+document Solution ArchitectureProposed technical solution to satisfy the requirements. Performance Enhancements
Lucene is very fast as a search engine. Given a text string, Consider this scenario: A user searches for 'heart' in the NCI The solution is to is lazy load the documents as needed. After the
As we move forward, it is important to keep current with the latest
We advertise our Searches as being 'extensions', but in reality it is very The Interface
As with Searching, Sort algorithms are not currently easily extended. A well defined The existing Interface org.LexGrid.LexBIG.Extensions.Query.Search will be
Join EntityDescription when building AssociatedConcepts Furthermore, this will allow the 'EntityDescription' to be available without Join EntryState when building CodedEntry |
- and there is potential RRF DataValue Set/Domain SupportLoading FrameworkCross product dependenciesInclude a link to the Core Product Dependency Matrix. Changes in technologyInclude any new dependencies in the Core Product Dependency Matrix and summarize them here. AssumptionsList any assumptions. RisksList any risks. Detailed DesignSpecify how the solution architecture will satisfy the requirements. This should include high level descriptions of program logic (for example in structured English), identifying container services to be used, and so on. Performance EnhancementsRRF DataValue Set/Domain SupportLoading FrameworkImplementation PlanThis will include the technical environment (HW,OS, Middleware), external dependencies, teams/locations performing development and procedures for development (e.g. lifecycle model,CM), and a detailed schedule. Technical environmentExternal dependenciesTeam/Location performing developmentProcedures for DevelopmentDetailed scheduleThe LexEVS 5.1 project plan is located in Gforge at: Training and documentation requirementsOne heading for each item. Download center changesList the needed changes. |