Upload v2.3.6 or previous ‐ migration and publication tasks

Execution of migration and publication tasks

1. Go to Tasks > Periodic Tasks
2. Perform the tasks in the sequence indicated in this document:

migrate_title_databases task

• Dependency: access to classic website database folders
• Objective: to obtain the journal records from the classic website database and insert them into the new system
• Follow-up: Consult the logs of the celeryworker container

Result

• Consult the Migration > Migrated Journals menu
• Consult the Processing menu > Journal Proc
• Check the columns and status filters
• Check the 'Events newest to oldest' tab (since v2.3.0) | 'Result' tab (previous releases)
• Check that all the migration steps have been recorded.
• Consult the Unexpected E... menu to identify unexpected problems. In this case, send an e-mail reporting the problem.

Note: in all listings, the column headings can be clicked to reorder the list by column.

migrate_issue_databases task

• Dependency: access to the classic website's base folders
• Objective: to obtain the issue records from the classic website database and insert them into the new system
• Follow-up: Consult the logs of the celeryworker container

Result

• Consult the Migration > Migrated Issues menu
• Go to Processing menu > Issue Proc
• Check the columns and status filters
• Check the 'Events newest to oldest' tab (since v2.3.0) | 'Result' tab (previous releases)
• Check that all the migration steps have been recorded.
• Consult the Unexpected E... menu to identify unexpected problems. In this case, send an e-mail reporting the problem.

Note: in all listings, the column headings can be clicked to reorder the list by column.

create_or_update_journals task

• Dependency: migrate_title_databases task successfully completed
• Objective: to create the records with journal data from the migrated data Follow-up: Consult the logs of the celeryworker container

Result

• Consult the Journals > Journals menu

• Consult the Processing menu > Journal Proc
• Check the columns and status filters
• Check the 'Events newest to oldest' tab (since v2.3.0) | 'Result' tab (previous releases)
• Check that all the migration steps have been recorded.
• Consult the Unexpected E... menu to identify unexpected problems. In this case, send an e-mail reporting the problem.

Note: in all listings, the column headings can be clicked to reorder the list by column.

create_or_update_issues task

• Dependency: migrate_issue_databases task successfully completed
• Objective: to create the records with issue data from the migrated data Follow-up: Consult the logs of the celeryworker container

Result

• Go to the Issues > Issues menu

• Go to the Processing menu > Issue Proc
• Check the columns and status filters
• Check the 'Events newest to oldest' tab (since v2.3.0) | 'Result' tab (previous releases)
• Check that all the migration steps have been recorded.
• Consult the Unexpected E... menu to identify unexpected problems. In this case, send an e-mail reporting the problem.

Note: in all listings, the column headings can be clicked to reorder the list by column.

publish_journals task

• Dependency: create_or_update_journals task successfully completed
• Objective: Publish journal data on the quality assurance (QA) website Interaction: new website
• Follow-up: Consult the logs of the celeryworker container

Result

• Consult the quality assurance (QA) website
• Go to Processing menu > Journal Proc
• Check the columns and status filters
• Check the 'Events newest to oldest' tab (since v2.3.0) | 'Result' tab (previous releases)
• Check that all the migration steps have been recorded.
• Consult the Unexpected E... menu to identify unexpected problems. In this case, send an e-mail reporting the problem.

Note: in all listings, the column headings can be clicked to reorder the list by column.

publish_issues task

• Dependency: create_or_update_issues task successfully completed
• Goal: Publish issue data on the quality assurance (QA) website Interaction: new website
• Follow-up: Consult the logs of celeryworker container

Result

• Consult the quality assurance (QA) website
• Go to the Processing menu > Issue Proc
• Check the columns and status filters
• See the Result tab
• Check that all the migration steps have been recorded.
• Consult the Unexpected E... menu to identify unexpected problems. In this case, send an e-mail reporting the problem.

Note: in all listings, the column headings can be clicked to reorder the list by column.

task_migrate_document_records task

• Dependency: create_or_update_issues task successfully completed and access to the folders on the classic website
• Objective: Obtain the article records from the classic website and store them in the new system. Consider adding journal_acron and/or publication_year parameters to execute it for a smaller amount. E.g.: {"journal_acron": "xyz", "publication_year": "2013"}, {"journal_acron": "xyz"}, {"publication_year": "2013"}
• Follow-up: Consult the logs of the celeryworker container

Result

• Consult the Migration > Migrated Article menu
• Although the migrated content of this task belongs to the articles, the status record is made in Issue Processing because the content is located in the issue folders.
• Go to the Processing menu > Issue Proc
• Check the columns and status filters
• Go to the Result tab
• Check that all the migration steps have been recorded.
• Consult the Unexpected E... menu to identify unexpected problems. In this case, send an e-mail reporting the problem.

Note: in all listings, the column headings can be clicked to reorder the list by column.

task_migrate_document_files task

• Dependency: create_or_update_issues task successfully completed and access to the folders of the - classic website
• Objective: Obtain the article files (pdf, xml, translation, img/reviews) from the classic website and store them in the new system. Consider adding journal_acron and/or publication_year parameters to execute it for a smaller amount. E.g.: {"journal_acron": "xyz", "publication_year": "2013"}, {"journal_acron": "xyz"}, {"publication_year": "2013"}
• Follow-up: Consult the logs of the celeryworker container

Result

• Consult the Migration > Migrated Files menu
• Although the migrated content of this task belongs to the articles, the status record is made in Issue Processing because the content is located in the issue folders.
• Go to the Processing menu > Issue Proc
• Check the columns and status filters
• Check the 'Events newest to oldest' tab (since v2.3.0) | 'Result' tab (previous releases)
• Check that all the migration steps have been recorded.
• Consult the Unexpected E... menu to identify unexpected problems. In this case, send an e-mail reporting the problem.

Note: in all listings, the column headings can be clicked to reorder the list by column.

get_xmls task

• Dependency: task_migrate_document_files task successfully completed
• Objective: Obtain the native XML or generate the XML from the article data and the files migrated from the translations folders.
• Follow-up: Consult the logs of the celeryworker container

Result

• Consult the Processing menu > XML from HTML
• Consult the Processing menu > Article Proc
• Check the columns and status filters
• Check the 'Events newest to oldest' tab (since v2.3.0) | 'Result' tab (previous releases)
• Check that all the migration steps have been recorded.
• Consult the Unexpected E... menu to identify unexpected problems. In this case, send an e-mail reporting the problem.

Note: in all listings, the column headings can be clicked to reorder the list by column.

generate_sps_packages task

• Dependency: get_xmls task successfully completed
• Objective: Get the XML and other migrated files and create an SPS package for each article. Interaction: core.scielo.org and minio.scielo.xxx (minio of the collection's domain)
• Follow-up: Consult the celeryworker container logs

Result

• Consult the Processing menu > SPS Packages
• Go to Processing menu > Article Proc
• Check the columns and status filters
• Consult the Result tab
• Check that all the migration steps have been recorded.
• Consult the Unexpected E... menu to identify unexpected problems. In this case, send an e-mail reporting the problem.

Note: in all listings, the column headings can be clicked to reorder the list by column.

create_or_update_articles task

• Dependency: generate_sps_packages task successfully completed
• Objective: to create the records with article data from the XMLs Follow-up: Consult the logs of the celeryworker container

Result

• Consult the Articles menu > Articles

• Go to Processing menu > Article Proc
• Check the columns and status filters
• Check the 'Events newest to oldest' tab (since v2.3.0) | 'Result' tab (previous releases)
• Check that all the migration steps have been recorded.
• Consult the Unexpected E... menu to identify unexpected problems. In this case, send an e-mail reporting the problem.

Note: in all listings, the column headings can be clicked to reorder the list by column.

publish_articles task

• Dependency: create_or_update_articles task successfully completed
• Goal: Publish the articles on the new website Follow-up: Consult the logs of the celeryworker container

Result

• Consult the new website

• Go to Processing menu > Article Proc
• Check the columns and status filters
• Check the 'Events newest to oldest' tab (since v2.3.0) | 'Result' tab (previous releases)
• Check that all the migration steps have been recorded.
• Consult the Unexpected E... menu to identify unexpected problems. In this case, send an e-mail reporting the problem.

Note: in all listings, the column headings can be clicked to reorder the list by column.