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

Campaign Dashboard-DOIs: Display DOI recommendations #381

Closed
heidimok opened this issue Jul 27, 2022 · 1 comment
Closed

Campaign Dashboard-DOIs: Display DOI recommendations #381

heidimok opened this issue Jul 27, 2022 · 1 comment
Labels
design Feature Request See something that you think could be better? Describe the feature and your ideas and let's talk MI

Comments

@heidimok
Copy link
Contributor

heidimok commented Jul 27, 2022

Context

This is part of EPIC: MI Workflow Redesign #270

This issue covers changes to the DOI tab of a campaign. The main goal is to clean it up so that it's no longer a giant table that is difficult to view and work with.

  • A Digital Object Identifier (DOI) is a url, a unique identifier for data products.
  • Data products are a digital file, often a collection of files, in Earth Science Data System (ESDS) based on a logically meaningful group of similar and meaningful data packages for users.
  • Curators need to connect DOIs to the right deployment, instrument, platform to ensure the user gets the clearest data product. What you usually get in a campaign is one package with all the data for one field station or all the field stations from the whole deployment (for example all data from deployment 1 and 2).

Current

image
https://admgstaging.nasa-impact.net/campaigns/4a10b484-7581-42ab-88dc-602abd674dc9/doi-approval

  • At first, there are no DOIs listed
  • You click on the Generate DOIs button to recommend DOIs
  • Campaigns, instruments, and platforms are recommended for a DOI

image
https://admgstaging.nasa-impact.net/campaigns/01fa8481-8cb3-48bd-b596-900a8207ac86/doi-approval

  • Curator’s have to use the CMR link (NASA’s main repository) or DOI to determine what these pre-populated data products should be associated with in CASEI
  • Curator can pick any of the published campaigns, platforms, etc, and assign them right in this view. They have a few rules if it makes sense that something should be in a campaign or platform, but need to go and verify if it should be tied.
  • The identifier or URL is the only thing that shows on CASEI
  • The keep column is there because it can be a tedious process so you can know which row you were on. Trash bin is supposed to allow curator’s to say ‘this data product didn't have anything to do with the campaign so it doesn’t get associated.

image
https://admgstaging.nasa-impact.net/drafts/edit/facb72fe-e621-4a26-8442-be111194d135?back=/campaigns/01fa8481-8cb3-48bd-b596-900a8207ac86/doi-approval

  • DOIs also have forms like campaign edit details but curators interact with them in a different way than other forms.
  • You can access the published version of these and create edit drafts just like anything in CASEI.
  • Non-admins only work on the main table view.

New

Clear starting action

image
https://www.figma.com/file/zY7BS9fR1huZ0CieHf3Dm8/MI-Workflow-Change?node-id=175%3A27679

  • If there are no DOIs, users see information about DOIs and a button to Generate DOIs
  • A new View select is a way to separate lists:
    • Recommended DOIs (X) - The default because it is the main task to-do
    • Associated DOIs (x) - Upon clicking 'Done' DOIs automatically go here if 1 or more association has been made
    • Unassociated DOIs (x) - Upon clicking 'Done' DOIs automatically go here if 0 associations have been made
  • No DOIs exist. Clicking “Generate DOIs”, will generate a list of recommended DOIs for this campaign based on the campaign's short_name. Please refresh the page a few minutes after clicking "Generate DOIs". Digital Object Identifiers (DOIs) are unique identifiers of data products in ESDS that need to be associated with a campaign, platform, instrument, or CDPI. It is recommended to re-run the DOI matcher after creating instruments, platforms, or CDPIs for this campaign to update the proposed DOIs.
    • Note that this text was removed. Need to double check if it's important to include: If you have not made drafts of this campaign's instrument, platforms, or CDPIs, the DOI matcher won't be able to automatically relate proposed DOIs to this campaign.
  • Splitting the page into two columns with a line is there because once they generate DOIs, the list of recommendations will be on the left side of the page while the association details/actions is separated into the right.

Review DOI recommendations

image
https://www.figma.com/file/zY7BS9fR1huZ0CieHf3Dm8/MI-Workflow-Change?node-id=442%3A26047

  • All the DOI recommendations are listed on the left. They use the same pattern as Deployments where clicking on each recommendation will change the details on the right.
  • Users can Generate DOIs again which updates the list
  • Upon selecting a DOI, the right column now shows the information that was previously shown in the table columns:
    • Name (use CMR shown name. If blank, use UUID)
    • Edit - Only admins can edit this
    • Links - DOI (external link)
    • Links - CMR (external link)
    • Associated Campaigns (title change)
    • Associated Platforms (title change)
    • Associated Instruments (title change)
    • Associated CDPIs (title change)
    • DOI reviewed and associations updated as needed? Done (prompts model)

image
Are you sure? Marking done will remove this DOI from the recommended DOIs list. You can still reference this DOI later on by viewing Associated DOIs or Unassociated DOIs. Cancel or Done.

Published reviewed item

image
https://www.figma.com/file/zY7BS9fR1huZ0CieHf3Dm8/MI-Workflow-Change?node-id=442%3A26823
image
https://www.figma.com/file/zY7BS9fR1huZ0CieHf3Dm8/MI-Workflow-Change?node-id=514%3A45349

  • Once a DOI has been associated, it moves out of the Recommended DOIs view and can continue to be updated by an admin
  • The status changes from Created to Published
@heidimok heidimok added MI Feature Request See something that you think could be better? Describe the feature and your ideas and let's talk design labels Jul 27, 2022
@heidimok
Copy link
Contributor Author

heidimok commented Apr 8, 2024

Closing this issue as we have released the new MI workflow and do not plan to make these additional changes.

@heidimok heidimok closed this as completed Apr 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
design Feature Request See something that you think could be better? Describe the feature and your ideas and let's talk MI
Projects
None yet
Development

No branches or pull requests

1 participant