Feature client transfer

[kjgarza]

Purpose

Allows staff admin to transfer repositories

resolves: #404

Approach

Adds a component to transfer repository.
It also renames the repository-transfer component as repository-dois-transfer to better fit its Purpose.

Learning

Fabrica stays in cache for a long time sometimes.

Status

• Ready for Review

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

[mfenner]

Can you explain why we have both repository-transfer and repository-dois-transfer components? I am also not convinced that we have a repository-dois transfer, at least for the user it is a transfer of the repository, the reindexing of DOIs is needed but for me not essential for what we are doing in the DOI.

Looks good otherwise.

[kjgarza]

as mentioned in the purpose, it just a refactor of the component to transfer dois:

It also renames the repository-transfer component as repository-dois-transfer to better fit its purpose.

One component its for the transfer doi functionality (the old/refactored one) and the new one is for transferring repositories.

[mfenner]

Why not repository-transfer and doi-transfer. That is what the user sees in the UI. As repository-transfer does not transfer any DOIs.

[kjgarza]

doi-transfer already exists, remember? https://github.com/datacite/bracco/blob/master/app/components/doi-transfer.js that's for the transfer of a DOI. it's for a single doi.

repository-dois-transfer is the old component that transfers all the dois of a single repository.

repository-dois-transfer shows:
https://doi.datacite.org/repositories/rads.sch/transfer

while repository-transfer shows:
https://codepen.io/kjgarza/full/YzyNxLg

[mfenner]

@kjgarza thanks for clarifying that, this makes sense.

[mfenner]

LGTM