Skip to content

Commit a7b9db9

Browse files
author
Amrutha Elamparuthy
authored
Merge branch 'master' into v2.0.0
2 parents aee758f + e8cd25c commit a7b9db9

File tree

4 files changed

+23
-1
lines changed

4 files changed

+23
-1
lines changed

GCIS Conventions v1.0.pdf

512 KB
Binary file not shown.

GCIS.2.0.ERD.pdf

82 KB
Binary file not shown.
+20
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
2+
# Custom Query
3+
     The custom query tool is an intuitive search functionality that provides a GCIS user with the means to develop simple search queries with downloadable results in the form of a data table. It uses an SQL-type syntax with limited scope: the tool is built around the SQL SELECT, FROM, and WHERE statements, with allowance to specify a wide range of GCIS resource attributes. However, rather than type query statements, a user develops a query by selecting options from drop-down menus.
4+
5+
     The custom query tool advances search functionality that goes beyond the limitations of the “search bar” in the GCIS website. Importantly, it helps a user develop a query in a stepwise fashion. Also, given the several and sometimes unique attributes belonging to each GCIS publication, the custom query tool simplifies querying by displaying only those attributes relevant to the GCIS publication specified in the first drop down menu. These features are described below.
6+
7+
## Usage
8+
9+
**Step 1** : To develop a query, first start by specifying the initial publication (for example, “Reports”). Like all other input specifications, this can be done by selecting the relevant data table from the drop-down menu.
10+
11+
**Step 2** : Specify one or more attributes (for example, “identifier”) of the selected table to filter by. Only attributes relevant to the publication selected in Step 1 will be displayed.
12+
13+
**Step 3** : Select a relationship option for the selected publication (for example, “having”).
14+
15+
**Step 4** : Select a secondary publication to query against (for example, “images”).
16+
17+
**Step 5** : Specify attributes for the WHERE statement in similar fashion as described above.
18+
19+
20+
     The above query would read “SELECT Title FROM Report HAVING Image”.

gcis_resources/activity.md

+3-1
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,7 @@ Activities are created to connect components of USGCRP reports to the source pub
1010

1111
Activities are not created for non-USGCRP products.
1212

13+
1314
## Field Conventions:
1415

1516
| Field | Description |
@@ -34,7 +35,8 @@ Activities are not created for non-USGCRP products.
3435
|**spatial_extent** |Spatial bounds used to restrict the input object. GeoJSON. Optional, depending on applicability.|
3536
|**data_usage** |**DEPRECATED**. A description of the way in which input data were used for this activity.|
3637
|**notes** |**DEPRECATED**. Other information about this activity which might be useful for traceability or reproducability.|
37-
|**duration** |**DEPRECATED**. Use activity_duration to document the time taken to perform the activity.
38+
|**duration** |**DEPRECATED**. Use activity_duration to document the time taken to perform the activity. |
39+
3840

3941

4042
## Provenance Conventions:

0 commit comments

Comments
 (0)