|
1 | | -Data & Observations Overview |
2 | | -=== |
| 1 | +# Arcsecond Cloud Storage vs External Storages |
3 | 2 |
|
4 | | -Arcsecond aims at providing a consistent platform for astronomical observers, being single or grouped into an |
5 | | -organisation (such as an astronomy club, or an observatory - see [Observatory Portals](/portals/) made for that). |
6 | | - |
7 | | -As such, Arcsecond offers solutions for astronomical data alone, for observations alone, and for the combination of |
8 | | -the two (where things become clearly more interesting). |
9 | | - |
10 | | -Arcsecond Cloud Storage vs External Storages |
11 | | ---- |
12 | | - |
13 | | -The principle is the following. With each personal account, and identically, with each Observatory Portal, comes the |
14 | | -[Arcsecond Cloud storage](./cloud-storage.md) by default. It is an unlimited read-write storage (you can upload, modify, |
15 | | -delete your files) based on secured Amazon AWS S3 buckets. |
16 | | - |
17 | | -In addition to that, multiple External Storages can be attached to the above account or portal. There is no restrictions |
18 | | -on the number of storages one can attach to an account or portal. These are read-only storages and Arcsecond will not |
19 | | -modify anything in them. Credentials will have to be provided, and will be stored encrypted and securely sealed in |
20 | | -Arcsecond ([read more](./credentials-security.md)). |
| 3 | +External Storages are existing data storages owned by an astronomer, or an Observatory Portal. Arcsecond allows to |
| 4 | +attach them to the account or portal. There is no restrictions on the number of storages one can attach to an account or |
| 5 | +portal. These are read-only storages and Arcsecond will not modify anything in them. Credentials will have to be |
| 6 | +provided, and will be stored encrypted and securely sealed in Arcsecond ([read more](./credentials-security.md)). |
21 | 7 |
|
22 | 8 | Find tutorials on how to provide credentials for your external storages in: |
23 | 9 |
|
24 | 10 | * [Amazon AWS S3 buckets](./external-storage-aws.md) |
25 | 11 | * [Dropbox](./external-storage-dropbox.md) |
26 | | -* FTP (coming soon) |
27 | | -* Local disk (coming with self-hosted Arcsecond, later in 2023) |
| 12 | +* [Azure](./external-storage-dropbox.md) (`in preparation`) |
| 13 | +* FTP |
| 14 | +* SFTP |
| 15 | +* Local disk (coming with self-hosted Arcsecond, `in preparation`) |
| 16 | +* Archives (ESO, CADC, HST, etc – `in preparation`) |
28 | 17 |
|
29 | 18 | For each account or portal, based on the accessible storages, Arcsecond will be able to extract and organise information |
30 | 19 | about your nights and observed targets. |
31 | 20 |
|
32 | 21 | {data-zoomable} |
33 | 22 |
|
34 | | -Arcsecond will parse content of external storages, identically to what it does on its |
| 23 | +Arcsecond will scan and parse content of external storages, identically to what it does on its |
35 | 24 | own [Cloud Storage](/observations/cloud-storage) when data is uploaded to it. This parsing allows to: |
36 | 25 |
|
37 | 26 | * Extract FITS- and XISF-files headers, for easy searching in a web interface, |
38 | 27 | * Create 2D-image and 1D-spectrum previews (stored in Arcsecond Cloud storage, within the 50GB limit, unless you unlock |
39 | 28 | more), |
40 | | -* **Create your personal list of all your observed targets, associated with its data** (this will combine all cloud and |
| 29 | +* **Create your personal list of all your follow-up targets, associated with its data** (this will combine all cloud and |
41 | 30 | external storages you have attached), |
42 | 31 | * Reconstruct your observing nights (when possible). |
43 | 32 |
|
|
0 commit comments