|
1 | | -# ⚠ Under construction ⚠ |
| 1 | +# Getting Started |
| 2 | + |
| 3 | +This section is for end users interested in using Clowder as a data repository, data sharing |
| 4 | +platform, or to develop data pipelines. |
| 5 | + |
| 6 | +There are two main ways to interact with Clowder |
| 7 | + |
| 8 | +- web interface |
| 9 | +- web API |
| 10 | + |
| 11 | +Most users will use the web interface to upload, download, and manage data, metadata, analytics and data visualizations. |
| 12 | +Advanced users can use the web API to interact with Clowder programmatically through scripts, Jupyter notebooks, or |
| 13 | +other services. |
| 14 | + |
| 15 | +## Data Model |
| 16 | + |
| 17 | +The main resources in Clowder is the **dataset**. |
| 18 | +A Clowder dataset is a collection of files, folders, metadata and visualizations. |
| 19 | +Datasets can be shared and downloaded. |
| 20 | +When uploading new data, users can create a new dataset or add files to existing datasets. |
| 21 | + |
| 22 | +One unique aspect of Clowder is the ability to attach **metadata** to files and datasets. |
| 23 | +Metadata can be used to store any kind of information about the underlying data, such as provenance, data quality, or |
| 24 | +data processing steps. |
| 25 | +A dataset or a file can have multiple metadata documents attached to it. |
| 26 | +These metadata documents can be manually added by the owner of the file or dataset, or automatically generated by |
| 27 | +information extractors. |
| 28 | +If the dataset is shared with other users, they can also add metadata to the dataset. |
| 29 | + |
| 30 | +Unlike most other systems which store metadata as key value pairs, Clowder represents metadata as JSON for Linking |
| 31 | +Data, [JSON-LD](https://json-ld.org/). |
| 32 | +The advantage of using JSON-LD is that it affords the simplicity of JSON, but enforces semantic information about each |
| 33 | +field in the JSON document. |
| 34 | +JSON-LD can also be serialized to [RDF](https://en.wikipedia.org/wiki/Resource_Description_Framework), make metadata |
| 35 | +interoperable with other systems, including [knowledge graphs](https://en.wikipedia.org/wiki/Knowledge_graph). |
| 36 | + |
| 37 | +When a user manually adds metadata to a file or dataset, they will pick from a list of metadata fields defined by the |
| 38 | +system. |
| 39 | +The administrators of the Clowder instance can define the metadata fields that are available to users. |
| 40 | +These metadata fields can be simple text fields, dropdowns, or more complex fields like date pickers. |
| 41 | +Clowder, via information extractors, can also add metadata automatically to files and datasets. |
| 42 | +These metadata documents can be the results a ofa manual submission to an information extractor or the result of an |
| 43 | +automatic extraction triggered by the system. |
| 44 | + |
| 45 | +## Signing Up |
| 46 | + |
| 47 | +Each user must sign up for an account to use Clowder. By default, users can sign up for a local account on the specific |
| 48 | +Clowder instance. Some instances may also allow users to sign in using single sign-on, through OAuth provider like |
| 49 | +Google, GitHub, [CILogon](https://cilogon.org/), [Globus](https://www.globus.org/). |
| 50 | + |
| 51 | +Depending on the configuration of the instance, users might not be automatically enabled once they have created an |
| 52 | +account. |
| 53 | +In this case, the administrator of the instance will need to enable the account. |
| 54 | + |
| 55 | +## Browsing and Searching |
| 56 | + |
| 57 | +## Uploading Data |
| 58 | + |
| 59 | +## Sharing Data |
| 60 | + |
0 commit comments