GES - Lena - UC#1-2

  • Document -
    • More of a descriptive DOI for a group of products related to a mission - a standing page for information about this DOI
    • Versions of data underneath can vary but the location is permanent with the latest description of the latest  version of the product (each product will have their own landing page that will give version history with links to accompanying DOIs)
    • Update:  DOI stays the same but the information underneath changes - see MERRA example on last bullet - Info is for the user to quickly learn more about the product pointing them in the right direction
    • User Community that would use this in publications - PIs (quick way to lead their audience to the data via poster or journal intro paragraph)
    • Deb Q: Good idea. Is this an HTML web page or would this be stored with the data on their computer?
      • DOI would point to a Word Document not an HTML page
    • Deb Q: What does fully-descriptive mean - eg. MERRA
    • Not for a PI needing to point to a collection of 40 products for one short citation for that group of data products
    • Beth Q:  Would this document be captured in CMR or linked to the dataset for that mission (maybe from a DOI landing page for a broader background of information).  Could it be under a section that says "Related Documents"
    •  
  • Mission Page
    • Data Group DOI - Lena
      • May have several groups of related products in a mission - all collections would be related to a single version of a product.  These would only change as a new version of the product came in.
      • Static document for a particular data collection

Megan - UC#3

  • Group DOI for Facility Project (eg. AJAX)
    • Facility and major air borne instruments have unique needs.
    • 4 groups (available in ED Search)
    • They want to highlight a group of flight samples during a particular event - reference this in a publication.
    • AJAX PI created a document posted on ASDC website with links to the flights for downloading data from the flight catalog (stores a flights-worth of data)
    • Assign DOI to a compendium of links which was used in a wild-fire publication
    • More like a Document DOI - links to a PDF which contains a flight and data table with flight links to associated folder
    • Only updated when the science team updates the product then the appropriate links would need to be updated. 
    • Deb Q: Looking for a single solution that can do several things or meets multiple needs.

BethH - UC #4-5

  • Easy access to lower-level data products
  • Grouping of PM products so users interested in PM can find those products easily
  • Create a DOI that points to entire group of products
  • Putting the suggestion out as a Q not a demand
  • Should we just use relationships to make the connection clear in CMR - maybe DOIs may not do what they want here.
  • Metadata solution - Metadata Input - products that went into that product may be a better way to move around within the group and know what the #s are.  We dont want an explosion of DOIs with too many to manage - open to feedback - an input to products tracked in DOI combined with a document DOI would probably solve this use case

Jeff  - UC#6

  • Citing the entire field campaign - use DOI link to capture methodologies that other campaigns could also use
    • Campaign landing page can be a central clearing house
  • More of a Document DOI or a Group of Group (collection) DOI?
    • More of a Group DOI for related DOIs with supporting information from magazines and other resources
    • Like a Document DOI Pointing to Data Product DOIs underneath
  • Deb Q - seems most of these Use Cases are document DOIs except when there is a new data product consisting of other data products with DOIs (capture that final summary from Deb)
  • No labels