|
7 | 7 | <p> |
8 | 8 | The EMBER Archive supports free storage and sharing of public data, prioritizing data |
9 | 9 | generated as a part of the |
10 | | - <LinkText :link="links.bbqs_full" />. Users can create an account to begin instantiating a project and uploading data. Users can also request access to data. As the program progresses, project data will be released freely and publicly following appropriate protocols. |
| 10 | + <LinkText :link="links.bbqs_full" />. Users can create an account to begin instantiating |
| 11 | + a project and uploading data. Users can also request access to data. As the program |
| 12 | + progresses, project data will be released freely and publicly following appropriate |
| 13 | + protocols. |
11 | 14 | </p> |
12 | 15 | <p> |
13 | 16 | <span class="text-bold"> |
14 | 17 | Currently, PHI/PII data cannot be submitted to the EMBER Archive. |
15 | 18 | </span> |
16 | | - As the BBQS program progresses, EMBER will be adding functionality to support PHI/PII data storage. |
| 19 | + As the BBQS program progresses, EMBER will be adding functionality to support PHI/PII |
| 20 | + data storage. |
17 | 21 | </p> |
18 | 22 | </q-card-section> |
19 | 23 | </q-card> |
|
27 | 31 | <q-item-section> |
28 | 32 | <q-item-label overline>Phase I</q-item-label> |
29 | 33 | <q-item-label> |
30 | | - Users will be required to verify human data have been de-identified and are approved for release and reuse. PHI/PII data will not be accepted. |
| 34 | + Users will be required to verify human data have been de-identified and are |
| 35 | + approved for release and reuse. PHI/PII data will not be accepted. |
31 | 36 | </q-item-label> |
32 | 37 | </q-item-section> |
33 | 38 | </q-item> |
|
36 | 41 | <q-item-section> |
37 | 42 | <q-item-label overline>Phase II</q-item-label> |
38 | 43 | <q-item-label> |
39 | | - Data access controls and data use agreements will be implemented, as needed, in accordance with IRB requirements. |
| 44 | + Data access controls and data use agreements will be implemented, as needed, in |
| 45 | + accordance with IRB requirements. |
40 | 46 | </q-item-label> |
41 | 47 | </q-item-section> |
42 | 48 | </q-item> |
|
45 | 51 | <q-item-section> |
46 | 52 | <q-item-label overline>Phase III</q-item-label> |
47 | 53 | <q-item-label> |
48 | | - Additional support for the storage and access control for PHI and PII data will be added. |
| 54 | + Additional support for the storage and access control for PHI and PII data will be |
| 55 | + added. |
49 | 56 | </q-item-label> |
50 | 57 | </q-item-section> |
51 | 58 | </q-item> |
|
62 | 69 | <q-item-section> |
63 | 70 | <q-item-label overline>Metadata</q-item-label> |
64 | 71 | <q-item-label> |
65 | | - Users can create an EMBER Project, specifying required and optional data for EMBERsets. |
| 72 | + Users can create an EMBER Project, specifying required and optional data for |
| 73 | + EMBERsets. |
66 | 74 | </q-item-label> |
67 | 75 | </q-item-section> |
68 | 76 | </q-item> |
|
71 | 79 | <q-item-section> |
72 | 80 | <q-item-label overline>Animal Electrophysiology and Behavioral Data</q-item-label> |
73 | 81 | <q-item-label> |
74 | | - Users can upload animal electrophysiology and behavioral data, specified in NWB and BIDS formats, along with supporting data files. This leverages our EMBER-DANDI instance. |
| 82 | + Users can upload animal electrophysiology and behavioral data, specified in NWB |
| 83 | + and BIDS formats, along with supporting data files. This leverages our EMBER-DANDI |
| 84 | + instance. |
75 | 85 | </q-item-label> |
76 | 86 | </q-item-section> |
77 | 87 | </q-item> |
|
80 | 90 | <q-item-section> |
81 | 91 | <q-item-label overline>De-identified Human Data</q-item-label> |
82 | 92 | <q-item-label> |
83 | | - Appropriately de-identified human data, such as electrophysiology, can be uploaded by users once assuring the appropriate IRB processes are followed and consent documented. Please contact us for more information! |
| 93 | + Appropriately de-identified human data, such as electrophysiology, can be uploaded |
| 94 | + by users once assuring the appropriate IRB processes are followed and consent |
| 95 | + documented. Please contact us for more information! |
84 | 96 | </q-item-label> |
85 | 97 | </q-item-section> |
86 | 98 | </q-item> |
|
89 | 101 | <q-item-section> |
90 | 102 | <q-item-label overline>Future Phases</q-item-label> |
91 | 103 | <q-item-label> |
92 | | - Future phases will allow upload of human data requiring access controls or data use agreements, as well as secure upload of PHI/PII information. |
| 104 | + Future phases will allow upload of human data requiring access controls or data |
| 105 | + use agreements, as well as secure upload of PHI/PII information. |
93 | 106 | </q-item-label> |
94 | 107 | </q-item-section> |
95 | 108 | </q-item> |
96 | | - |
97 | 109 | </q-list> |
98 | 110 | </q-card-section> |
99 | 111 |
|
|
125 | 137 | <div class="text-h2 scrollable" ref="dataAccessSection">Data Access & Requests</div> |
126 | 138 |
|
127 | 139 | <p class="q-px-md q-py-sm"> |
128 | | - Users can create an account to request data access. As data are released publicly in support of the BBQS program, they will be listed on the |
| 140 | + Users can create an account to request data access. As data are released publicly in |
| 141 | + support of the BBQS program, they will be listed on the |
129 | 142 | <RouterLink to="/projects" class="link">Projects</RouterLink> |
130 | 143 | page. |
131 | 144 | </p> |
|
0 commit comments