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

:creator and :contributor global attributes #97

Open
mmckinzie opened this issue Jan 14, 2025 · 3 comments
Open

:creator and :contributor global attributes #97

mmckinzie opened this issue Jan 14, 2025 · 3 comments
Labels
bug Something isn't working enhancement New feature or request

Comments

@mmckinzie
Copy link

What should we add?

We still need to resolve the issue or devise a more appropriate approach for populating the suite of creator/contributor global attributes within the satellite trajectory NetCDF files; continuing to harvest these metadata attributes from the RW project level metadata → contacts → citation folks is problematic. The current approach conflicts with the DACs data management/submission guidelines allowing data contributors to have distinct 'project', 'deployment' and 'dataset' level metadata, as well as has implications for metadata presently contained in the portal project pages.

Additional discussion and notes regarding this topic can be found within our NCEI call notes, ATN test files issue notes, ATN DAC coordinator notes, and ML Axiom notes.

Reference

No response

@iwensu0313
Copy link

iwensu0313 commented Feb 7, 2025

@mmckinzie - I went through the past notes you pointed me to to better understand and summarize the issue.

I took a stab at answering the two Qs below based I what I gathered, but I don't think I have it all right. Can you help me fill in the gaps here? This might be helpful to include in description above.

Adding these two Qs to to the Issue description will help:

What is the current status quo (i.e., what happens if this does not get done)?

  • ATN Portal Project Overview page (ex)
    • Responsible Parties section populated w/ RW Project-level metadata Citation Folks
    • Points of Contacts section populated w/ RW Project-level metadata POC
  • ATN Portal Dataset Overview page (ex)
    • Responsible Parties section populated w/ RW Dataset/Folder-level metadata Citation Folks
    • Points of Contacts section populated w/ RW Dataset/Folder-level metadata POC
  • NCEI archive files Contributor/Creator attributes (contributor_email, contributor_institution, contributor_name, contributor_role and contributor_url) are harvested from RW project-level metadata > Citation Folks
    • Citation Folks > Principal Investigator is populated into the creator field in the NCEI archive files
    • Every other Citation Folks listed is populated into the contributor field in the NCEI archive files
  • Workaround for undesired behavior for NCEI contributor/creator attributes
    • Copy/paste each Citation Folk entry at the RW Folder level metadata record into the Citation Folk page at the RW Project level metadata record
    • Once NCEI scrapes and pulls the archive files, remove those changes and make sure the original Citation Folks at the Project level are back so that we have the correct Citation Folks on the ATN Portal Project page

What indicates this is done (i.e., how do we know this is complete)?

  • Keep the current status quo with regards to how Citation Folks/POCs show up on ATN Portal Project and Dataset Overview Pages
  • NCEI creator and contributor fields are populated as expected with the Folder/Dataset-level 'Citation Folks';
    • it's possible for future deployment groupings to have different set of 'Citation Folks'
    • so we may need to consider creating a new RW folder for each deployment grouping to have two distinct Folder/Dataset-level records
  • Megan no longer has to temporarily copy/paste each Citation Folk from Folder-level metadata in RW to Project-level metadata in RW and "revert" that after NCEI picks up the archive files
  • ATN Portal Project page won't temporarily have the incorrect set of Citation Folks between when we submit NCEI deployment archive files to NCEI to pick up and when they pick it up and archive it

@iwensu0313
Copy link

@mmckinzie okay I updated my summary above based on what you walked me through this aft. Hope that all looks right.

@mmckinzie
Copy link
Author

@iwensu0313 Yes that summary looks good and correctly captures the issue. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants