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.

Sign up for GitHub

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

Jump to bottom

Data portal - decide how manifest_set records should look in the UI #1463

Open
aclum opened this issue Nov 15, 2024 · 1 comment
Open

Data portal - decide how manifest_set records should look in the UI #1463

aclum opened this issue Nov 15, 2024 · 1 comment
Assignees
@aclum @kheal

Comments

@aclum
Copy link
Contributor

aclum commented Nov 15, 2024

This ticket replaces #1365
@aclum aclum assigned aclum and kheal Nov 15, 2024
@kheal
Copy link

kheal commented Nov 22, 2024 •
edited
Loading

For the MS-related use case:
When the associated Manifest record that is referenced to a DataObject has the field value manifest_type of instrument_run, no special or alternate handling is needed on the upset plots or changes to the existing UI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@aclum aclum

@kheal kheal

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@aclum @kheal