-
Notifications
You must be signed in to change notification settings - Fork 0
/
notes.rst
50 lines (37 loc) · 1.47 KB
/
notes.rst
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
# Architectural notes coming soon
## What do the page folders represent
## Architecture of templates
## What are the JS Scripts
=======
*******
Notes
*******
Architectural notes coming soon
===============================
Assets
------
assets/conf contains json configuration files specific for each environment the
labcas-ui 2.1 portal is deployed in. EDRN, MCL, and Labcas-dev are the three versions
currently deployed which displays each consortium's relevant data within the portal.
Configurations include base url links, sort/show/hide fields for each of the three
hierarchical detail pages (collection, dataset, file), search filter fields, and
collection specific filter fields.
assets/js/labcas contains labcas specific custom scripts that facilitates login,
search, dashboarding, utils, and page generations.
App Folders
-----------
m: main page (list of collections)
c: collection detail page
d: dataset detail page
f: file detail page
s: search page
a: dashboard page
x: favorites/starred page
p: public collections page
Template
--------
templates.html contains divs with different ids that are pulled separately into different
labcas pages. Pages use jquery load function to add div related content into functional
pages. Example is $('#{{id}}').load("{{file}} {{divid}}"); where id is div located where
content destination should go, file is the template html that contains template content,
and divid is subsection in template we want to pull content into destination.