This is the main file that is used for the HMDC home page. This page includes all the standard header and footer.
This is the main style sheet for the page. Most all styles can be found in here.
This style sheet controls the styles in the popup windows from the hmdc. This is also included on the main page of the HMDC.
This controller handles the filtering for the disease table, as well as using the Search Service to do the data query for the table. This controller also handles the popup for the "Source" link on the smart table.
This controller handles the filtering for the gene table, as well as using the Search Service to do the data query for the table. This controller also handles the popup for the "Source" link on the smart table.
This controller handles the following:
- Popups
- Custom methods for the grid formating on the ng-cells directive
- Grid filtering
- Gird Search
- Updates the amount of rows and columns to show based on window size
- Builds out the filter lists for all the tabs
- Filters / Builds the grid.
- Changes the JSON String coming from Fewi into the format needed for the ng-cells grid
This controller handles the following:
- Setting up the filter settings options
- The cooridnation of events between the tabs for the filters
- The "You Searched For" text
- The click on the search buttton from the main query form
- Parses the gene upload file.
- Definition of the tabs
- Definition of the query form
This service provides a method for getting the REST endpoint for the autocomplete controller, for HMDC. This method takes the data in the query form in order to process the search to solr.
This service provides three methods used for doing Ajax calls to the server for each of the three tabs. All of them take the formData from the query form and pass that data to the server for processing.
This service provides a method that can be used to "natural sort" the list that is passed to it. This might be better known as Smart Alpha sorting.
This directive is used to add to the different tables in order to get the "reset" functionality for when the table data changes.
Filters are used to remove results from the query. Filters do not go back to the server with parameters. Filters filter out what is not selecte and keep what is selected. Also the filter list are not facet queries but rather lists from the original query.
This filter is used on different columns in the smart tables to order by that field of data by chaining it by a |
This filter is used to handle sub scripting on different fields, by adding to the field via a |
This filter is used to sort the columns of the smart tables by the header of the column. When clicking on the column heading the sort will reverse
This file is used to display the search query form, and all the tabs that are driven by the model in the search controller.
This file is used to display the disease table. It makes use of angular Smart Table
This file is used to display the gene table. It makes use of angular Smart Table
This file is used to display the HMDC grid. It makes use of angular ng-cells module.
- vm.onSubmit() on Search Controller is run
- Clears the loaded file data from the model before sending it on.
- Emits the CallSearchMethod Event which goes to all three controllers (Grid, Gene, Disease)
- Hides the query form
- Generates "You Searched for" string
- Sets the grid loading to true
- Runs the Ajax search method
- Builds Filter Lists in the root scope
- Filters the grid via the built lists
- Builds the grid
- Sets the grid loading to false
- Removes any previous filters
- Emit ClearFilterText (which clears the filter lists see picture below)
- Sets the gene loading to true
- Runs the Ajax search method
- Runs the filter method
- Removes any filters from the original filter set
- Sets the gene loading to false
- Sets the disease loading to true
- Runs the Ajax search method
- Sets the result count based on the data coming back from the server
- Runs the filter method
- Removed any filters from the original filter set
- Sets the disease loading to false
The image shows what happens with the Gene filter specifically but the same process happens for the disease filter also.
- vm.applyFilters on the Search Controller is run
- Emit FilterChanged Event to the Grid controllers
- Catch FilterChanged Event
- Sets grid loading to true
- Filters the grid based on the current filter set
- Emits GridFilterFinished event
- Builds the grid based the data that is left from the filter
- Sets grid loading to false
- Catch GridFilterFinished event
- Runs Filter Method with new filter values
- Catch GridFilterFinished event
- Runs Filter Method with new filter values
This surrounds the entire page on the html tag in the header.jsp page via the <html ng-app="HMDCApplication"> The app.module.js defines the application and the modules that its uses.
This is based on the Search Controller which surronds the searchTemplate.html. <div ng-controller="SearchController">
This is based on the gridTemplate.html which is included from inside the searchTemplate.html.
This is based on the geneTemplate.html which is included from inside the searchTemplate.html.
This is based on the diseaseTemplate.html which is included from inside the searchTemplate.html.
This is used in each of the controllers for their local model to interact with and have access to the data in the html templates and the javascript. Sometimes this can be shared, if a lower (down the tree) scope does not override it, see picture from above.