Skip to content

Commit d92b568

Browse files
committed
Updated docs to make it clear uploader is now the preferred way
1 parent 9476f28 commit d92b568

File tree

1 file changed

+25
-23
lines changed

1 file changed

+25
-23
lines changed

USER-GUIDE.md

+25-23
Original file line numberDiff line numberDiff line change
@@ -412,38 +412,17 @@ Warning: aligner can take an even longer time, please be patient.
412412

413413
## 5. Upload to Fragalysis
414414

415-
To generate the gzipped tar file needed to manually upload the data move into your version dir and run this command
416-
(updating it for the specific upload version and target name):
417-
418-
```
419-
tar cvfz <target_name>.tgz upload_1
420-
```
421-
422-
Change `upload_1` to whatever your current upload is.
423-
424-
425-
### Uploading using the API endpoint
426-
427415
**Staging vs production: there are two live versions of Fragalysis. "Staging" is used for testing and is in constant development, therefore it may be buggier and/or have new features with respect to "production" which is the stable and public deployment. You should test if your upload works in staging, and verify that the data has been uploaded correctly before uploading to production. Data in staging is "at risk" as we may have to wipe the data occassionally for development reasons.**
428416

429417
### First to log in to Fragalysis and authenticate and log in with your FedID:
430418

431419
* Staging: https://fragalysis.xchem.diamond.ac.uk/viewer/react/landing
432420
* Production: https://fragalysis.diamond.ac.uk/viewer/react/landing
433421

434-
### The gzipped tar file can then be uploaded to Fragalysis via:
435-
436-
* Staging: https://fragalysis.xchem.diamond.ac.uk/api/upload_target_experiments/
437-
* Production: https://fragalysis.diamond.ac.uk/api/upload_target_experiments
438-
439-
The target access string will be the name of your proposal in UAS/ISpyB. Any Fed ID with access to your proposal will be able to see your data. If you have a private/closed data set, this means only logged in users with access configured via UAS will see your target dataset.
440-
441-
Fill in your email and attach the `.tgz` archive. After clicking 'POST' you will see a URL which you can append to https://fragalysis.xchem.diamond.ac.uk/ (or https://fragalysis.diamond.ac.uk/ for production) to track the progress of the upload.
442-
443422

444423
### Uploading with the XCA uploader tool
445424

446-
To use the XChemAlign uploader tool, first log in to Fragalysis and obtain the authentication token. Token can be obtained from:
425+
The preferred way to upload data to Fragalysis is using the uploader tool in XChemAlign. Once you've logged in, you can obtain the authentication token from:
447426

448427
* Staging: https://fragalysis.xchem.diamond.ac.uk/api/token/
449428
* Production: https://fragalysis.diamond.ac.uk/api/token/
@@ -454,14 +433,37 @@ Then run the upload command:
454433
python -m xchemalign.uploader -u <fragalysis url> -p <proposal number> -t <token>
455434
```
456435

457-
This will find the latest upload directory, compress it to a tarball, and then upload it to a given URL. If the tarball already exists, the compression step can be skipped by specifying either
436+
This will find the latest upload directory, compress it to a tarball, and then upload it to the given URL. If the tarball already exists, the compression step can be skipped by specifying either
458437
`-d` or `-c <path to custom tarball>` parameters. Instead of a full URL, a stack nickname can be used, if defined in the environment. To see the nicknames available, use the help command:
459438

460439
```commandline
461440
python -m xchemalign.uploader -h
462441
```
463442

464443

444+
### Uploading using the API endpoint
445+
446+
An alternative is to use the API endpoint directly. For this you need to generate the gzipped tar file and manually upload the data. Move into your version dir and run this command
447+
(updating it for the specific upload version and target name):
448+
449+
```
450+
tar cvfz <target_name>.tgz upload_1
451+
```
452+
453+
Change `upload_1` to whatever your current upload is.
454+
455+
456+
The gzipped tar file can then be uploaded to Fragalysis via:
457+
458+
* Staging: https://fragalysis.xchem.diamond.ac.uk/api/upload_target_experiments/
459+
* Production: https://fragalysis.diamond.ac.uk/api/upload_target_experiments
460+
461+
The target access string will be the name of your proposal in UAS/ISpyB. Any Fed ID with access to your proposal will be able to see your data. If you have a private/closed data set, this means only logged in users with access configured via UAS will see your target dataset.
462+
463+
Attach the `.tgz` archive by clicking the 'Choose file' button. The remaining fields, 'Data version' and 'Target name', are not necessary, these are used only by the uploader tool. After clicking 'POST' you will see a URL which you can append to https://fragalysis.xchem.diamond.ac.uk/ (or https://fragalysis.diamond.ac.uk/ for production) to track the progress of the upload.
464+
465+
466+
465467
## 6. Creating subsequent versions
466468

467469
When you have new or updated data you need to create a new version of the upload.

0 commit comments

Comments
 (0)