Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Preparing file migration #31

Open
3 tasks
philippconzett opened this issue Oct 6, 2021 · 3 comments
Open
3 tasks

Preparing file migration #31

philippconzett opened this issue Oct 6, 2021 · 3 comments
Assignees
Labels
Azure Related to the MS Azure cloud computing service Dataverse Related to the Dataverse software

Comments

@philippconzett
Copy link

We need to plan how to migrate files to Azure, including figuring out

  • why we have different data folders in production and test:
    10.18710 (production DOI of DataverseNO)
    10.5072/FK2/ (general test DOI provided by DataCite)
    10.10037.1 (? former test DOI of DataverseNO)
    10.21337 (current test DOI of DataverseNO)
  • how to speed up transfer, e.g. by creating tar and do gzip
  • ...
@philippconzett philippconzett added Azure Related to the MS Azure cloud computing service Dataverse Related to the Dataverse software labels Oct 6, 2021
@philippconzett
Copy link
Author

Two cases that need special handling:

  • 10.5072/FK2/VA3BVU/ needs to be re-created and published as an entirely new dataset.
  • 4 datasets in the DocEnhance collection on test.dataverse.no; see https://test.dataverse.no/dataverse/DocEnhance, need to be saved and recreated once we have migrated to Azure.

@philippconzett
Copy link
Author

I just had a look at how this looks in the DataverseNO user for DataCite.

In the user account for our production base (dataverse.no), there is only one DOI prefix displaying, 10.18710:
image

In the user account for our test base (test.dataverse.no), in addition to our test DOI prefix (10.21337), there are also 2 datasets with the production DOI prefix (10.18710):
image

I don't know why.

@Louis-wr
Copy link

Test compress with rsinc

Louis-wr pushed a commit that referenced this issue Feb 21, 2023
feat: make API signing secret a JvmSetting IQSS#7715
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Azure Related to the MS Azure cloud computing service Dataverse Related to the Dataverse software
Projects
None yet
Development

No branches or pull requests

5 participants