Outline, not a complete guide
This document was a list of empty headings. It now records what each topic covers and points at the authoritative source; the procedures themselves are still to be written. User-facing instructions live at learning.cyverse.org.
Access paths¶
| Path | What it is | Reference |
|---|---|---|
| iRODS protocol | Native access with iCommands or GoCommands |
Data Store |
| WebDAV / HTTPS | data.cyverse.org, via Apache and davrods |
Data Store |
| SFTP | SFTPGo with the iRODS backend | Data Store |
| CSI driver | Mounts collections into analysis pods | iRODS CSI driver |
| Terrain API | Programmatic filesystem operations | filesystem endpoints |
Third-party clients that speak WebDAV or SFTP work against the endpoints above — Cyberduck, FileZilla, and most desktop file managers among them. Nothing CyVerse-specific has to be installed for those.
Common administrative tasks¶
- Sharing. Permissions are set per collection or data object and can be granted to users or groups; see permissions and sharing for what the API exposes.
- Anonymous access. Public readability depends on the
anonymousaccount's permissions, established during zone initialization. - Community released folders. Publishing a folder to all CyVerse users; see Data Commons.
- Curated folders and DOIs. Staff-reviewed publication with a DataCite DOI, driven by permanent ID requests. The reviewer's checklist is in DE administration.
- Tickets. Time- or use-limited anonymous access to a specific path; see tickets.