Unable to un-assign primary or secondary wrangler

[ipediez]

Description of the task:

The project Multiomics single-cell analysis of human pancreatic islets reveals novel cellular states in health and type 1 diabetes is not wrangleable right now, as it is a pre-print with no data or metadata available at the moment. To avoid this affecting our way of filtering and triaging datasets in Ingest, it would be great to set back the value of the "Primary Wrangler" field to its default. This cannot be done from the UI, where the last value of the field gets automatically assigned when left blank, so a dev action is needed.

Acceptance criteria for the task:

• The "Primary Wrangler" field can be set to its "default value"
  • Better put as "Assigned wranglers can be unassigned"?
• The "Secondary Wrangler" field can be set to its "default value"

Other fields that can't currently be un-set, should be resolved by current intended solution:

• Project Information Fields:
  • releaseDate
  • accessionDate
  • dataAccess
  • technology
  • identifyingOrganisms
• Wrangler Admin Fields:
  • primaryWrangler
  • secondaryWrangler
  • wranglingState
  • wranglingNotes
  • dcpReleaseNumber

[MightyAx]

Reviewer's: @aaclan-ebi & @yusra-haider

[MightyAx]

This issue is 2 fold:

1. there is no interface (clickable) to allow "clearing a wrangler assignment" or "setting the default value" for primary or secondary wranglers.
2. The underlying data for an unassigned project is primaryWrangler: null, ingest-ui strips out all null values before sending the data to ingest core.
   • This affects more fields than primary / secondary wrangler and will have to be fixed for those fields too.

[MightyAx]

Work in progress solution for problem 1: "there is no interface (clickable) to allow clearing a wrangler assignment":

[MightyAx]

Current Sequence Diagram: https://miro.com/app/board/uXjVOSWgtMw=/

[ipediez]

@gabsie @ipediez and @ofanobilbao to take a look at the design and the functionality

[gabsie]

Hi, @MightyAx - I am good with the designs shown above !

[MightyAx]

@ofanobilbao you wanted to know the other fields that can't currently be un-set, that should be resolved by current intended solution:

• Project Information Fields:
  • releaseDate
  • accessionDate
  • dataAccess
  • technology
  • identifyingOrganisms
• Wrangler Admin Fields:
  • primaryWrangler
  • secondaryWrangler
  • wranglingState
  • wranglingNotes
  • dcpReleaseNumber

[MightyAx]

Awaiting PR Reviews

[idazucchi]

Jacob is reviewing

[MightyAx]

Review comments resolved, merged and deployed to dev. merged to master and deployed to staging. Will sit with @Wkt8 this afternoon to verify.

[Wkt8]

Have sat with @MightyAx and tested it - looks great. Clear, and fulfils what we are trying to do. I think we can put this into production.

[MightyAx]

Deployed to Production. Verified functionality is on production