Skip to content

Upload application configuration

Jump to bottom
Roberta Takenaka edited this page Sep 20, 2024 · 6 revisions

Update: Development team, 20-Sep-2024

Back to Home - SciELO Publishing Platform Guide

Access the upload.scielo.xxx

Access the address configured on the web server: https://upload.scielo.xxx/admin (address configured in Nginx).

image

Figure 1. Menu

Collections

  1. Create a collection by going to Collections > Collections in the menu:

  2. Fill in the collection ISO 3166-1 Alpha-3 Country Code, e.g., scl, mex, chl, cri, cub etc. Consult https://articlemeta.scielo.org/api/v1/collection/identifiers/ (acron value)

Websites

  1. Go to the New Websites Configurations menu.

  2. Fill in the SciELO website configuration data

- Collection: (select the collection registered previously)
- Website URL: "https://qa.scielo.xxx"
- Purpose: "QA"
- Article API URL: "https://qa.scielo.xxx/api/v1/article"
- Issue API URL: "https://qa.scielo.xxx/api/v1/issue"
- Journal API URL: "https://qa.scielo.xxx/api/v1/journal"
- Get token API URL: "https://qa.scielo.xxx/api/v1/auth"
- Api username: "upload.xxx"
- Api password: "******"
- enabled: false

To check if the configuration is correct, in the server in which Upload is installed, in the terminal, run:

curl --request POST https://qa.scielo.xxx/api/v1/auth -u "useremail:password"

The result must be similar to

{
  "exp": "Sat, 21 Sep 2024 08:31:15 GMT",
  "message": "Validated successfully",
  "token": "eyJhbG..."
}

Files Storage (MinIO)

  1. Go to the Files Storage (MinIO) settings menu

  2. Fill in the Files Storage configuration data

- Name: minio.scielo.xxx (any name to identify this instance)
- Host: minio.scielo.xxx (domain without http or https, and no subdir)
- Bucket root: upload
- Access key: Access key for File Storage  (created according to Minio’s procedure)
- Secret key: Secret key for File Storage (created according to Minio’s procedure)
- Secure: checked (with SSL configuration is already done) and unchecked otherwise

Classic website configuration

  1. Go to the Classic website configurations menu
  2. Map each of the classic website folders mentioned below. Read 'Creating access to classic website folders'
  3. Fill in the Website configuration data. Note /scielo_www corresponds to scielo/www (path to classic website folders).
- Collection: select the collection
- Title path: Website path to Title (/scielo_www/new_platform/bases_for_upload/title.id)
- Issue path: Website path to Issue (/scielo_www/new_platform/bases_for_upload/issue.id)
- Serial path: (ignore)
- Cisis path: (ignore)
- Bases work path: Website path to the Bases folder (/scielo_www/new_platform/bases_for_upload/bases-work)
- Bases pdf path: Website path to the PDF folder (/scielo_www/bases/pdf)
- Bases translation path: Website path to the translation folder (/scielo_www/bases/translation)
- Bases XML path: Website path to the XML folder (/scielo_www/bases/xml)
- Htdocs img revistas path: Website path to images (/scielo_www/htdocs/img/revistas)

Note: The *.id files are text files converted from *.mst and *.xrf binary files which are classic website databases.

Pid Provider configuration

  1. Access the Pid Provider config menu
  2. Fill in the configuration data for the Pid Provider to be supplied for each collection and the specific user
- XML Post URI: URL for sending XML. `https://core.scielo.org/api/v2/pid/pid_provider/`
- Get Token URI: URL to obtain the token. `https://core.scielo.org/api/v2/auth/token/`
- API Username: API user. We will provide an username and password, by providing an impersonal e-mail
- API Password: API password

To check if the configuration is correct, in the server in which Upload is installed, in the terminal:

Change USERNAME and PASSWORD by the username and password registered on core.scielo.org.

curl -X POST https://core.scielo.org/api/v2/auth/token/ --data 'username=USERNAME&password=PASSWORD'

The result must be similar to

{"refresh":"eyJhbG...","access":"eyJhbG..."}%
Clone this wiki locally