-
Notifications
You must be signed in to change notification settings - Fork 3
app structure
Beta Masaheft app works like this
the parts of the app using this technology use functions in modules which need to be imported by view.xql, the xquery which calls the templates module and matches the data-template attributes in the html with the xquery functions.
templates
- templates/search.html is used by the advanced search, as.html
- templates/searchR.html is used by search.html
the initial form in as.html uses the controller template model with the template search.html, which calls a javascirpt filters.js which on click loads with AJAX the selected form*.html file. Each of these contains a call to a function app:NAMEofTHEform which will call app:formcontrol which will call app:selectors This allows the form to be flexibly adjusted and load only what is needed. The number of parameters needed does not allow to do this (to my current knowledge) with RESTXQ unfortunately
Search results API Documentation Team
The indexes under Resources use the controller/model/view system to load from the called html a single function producing the result. these functions are in resources.xqm
post.xsl transformation is called directly by the controller for any request with the pattern /tei/resource.xml. this is different from calling simply resource.xml which will return the source file
jquery bootstrap
is used for the date and other sliders in search filters
is used for the comparison of manuscripts for the carousel
is used to view images from the iiif manifests
is used to view images in the catalogue entry view
this does the small popups on links to perseus, geonames, wikipedia