[ldd-request] Create new LDD "neas"

[c-suh]

• Local Data Dictionary Name:
  Near Earth Asteroid Scout Mission LDD

• Namespace ID Requested:
  neas

• Discipline or Mission LDD?
  mission

• Steward Organization Name: examples: PDS PPI Node, PDS EN Node, PDS RMS Node, PSA, JAXA

• LDD Steward Name: Name of lead point of contact from steward organization

• LDD Steward Email: email address of LDD Steward

• LDD Stewardship Team Members: Github usernames for all members of the LDD Stewardship Team. For more information on the responsibilities of the LDD Stewardship Team, see https://pds-data-dictionaries.github.io/development/ldd-create.html#who-is-the-ldd-stewardship-team

• LDD Description:
  Mission dictionary for the Near Earth Asteroid Scout (NEAS) Mission

• Rationale for creation of new LDD:
  Provide mission-specific metadata for the Near Earth Asteroid Scout mission

---

Engineering Details

• Complete Initializing New LDD procedure
• If discipline LDD
  • update LDD script config
  • create directory and index files for Git
  • create symlink on all machines

[c-suh]

Hello @neese, please provide the information for the fields above. You likely cannot make edits there, so leave a new comment with the information. Thank you!

[neese]

Long Name: Near Earth Asteroid Scout Mission LDD
LDD description: Mission dictionary for the Near Earth Asteroid Scout (NEAS) Mission
Rationale for the creation of a new LDD: Provide mission-specific metadata for the Near Earth Asteroid Scout mission

For the questions about steward and stewardship team, it was my understanding that a mission dictionary doesn't have these.

[c-suh]

Hi @neese - thank you for the information! I've updated the descriptions for both issues and will prompt Steve about the namespace.

Regarding the stewardship team for mission dictionaries, I will verify and get back to you.

[c-suh]

@neese, we do require a steward or lead for any LDD, regardless of whether it is a discipline or mission dictionary, so please provide those details.

Regarding a stewardship team, if one exists, we encourage establishing it in GitHub as there are several benefits to this, e.g. admin access to the LDD repository, automatic notifications of pull requests (PRs) and assignments of issues. However, you are correct in that this is not required. Thank you for bringing this distinction to my attention!

[neese]

The people involved in the NEAS LDD are Ken Lawrence of the NEAScout mission who is preparing the dictionary, and myself the PDS POC for NEAScout who am advising him both for appropriate content and helping him learn how to do it. So I guess we would be the stewardship team, but which of us would be the steward?

[c-suh]

Hi @neese, apologies for the delay. (Please leave a comment with "@c-suh" so that I'm notified that you've left a comment.) The lead steward will be listed on the PDS Namespace Registry and is typically also the person to whom any LDD GitHub issues are assigned, but these can be differentiated if need be. The person (or persons) assigned to the issues can also be changed down the road, especially as the length and involvement of your advisory role might affect how you designate each of these contacts.

[c-suh]

Hello @neese, I hope all is well. I am designating you as the lead steward - the POC to be listed in the PDS Namespace Registry and the assignee for any GitHub issues. However, let me know if you would like the latter to be changed to Ken Lawrence; if so regardless, I will need Ken's GitHub username to add him to the LDD Stewardship Team. Thank you.

[c-suh]

@neese your LDD repo is now ready for use at https://github.com/pds-data-dictionaries/ldd-neas. Read through Getting to Know Your LDD Repo to get started.

[neese]

Thanks, @c-suh! I have a question: Ken Lawrence of the NEAScout mission downloaded LDDTool and has been developing the NEAS LDD locally. How do I make the new PDS NEAS repo available to him to continue development of the NEAS LDD? What does he need to do to get access?

…

On Feb 3, 2022, at 6:17 PM, Catherine Suh ***@***.***> wrote: @neese <https://www.google.com/url?q=https://github.com/neese&source=gmail-imap&ust=1644542228000000&usg=AOvVaw0o0SHNKKqYYzhDx1au2cEX> your LDD repo is now ready for use at https://github.com/pds-data-dictionaries/ldd-neas <https://www.google.com/url?q=https://github.com/pds-data-dictionaries/ldd-neas&source=gmail-imap&ust=1644542228000000&usg=AOvVaw2qaHafuCHb0hicdBbg3HWP>. Read through Getting to Know Your LDD Repo <https://www.google.com/url?q=https://pds-data-dictionaries.github.io/getting-started.html%23getting-to-know-your-ldd-repo&source=gmail-imap&ust=1644542228000000&usg=AOvVaw0v6gyC38Tijj8epJ1daShp> to get started. — Reply to this email directly, view it on GitHub <https://www.google.com/url?q=https://github.com/NASA-PDS/operations/issues/199%23issuecomment-1029551103&source=gmail-imap&ust=1644542228000000&usg=AOvVaw3d57LRxEpfz6GyU6Ugcxz7>, or unsubscribe <https://www.google.com/url?q=https://github.com/notifications/unsubscribe-auth/AGJQ4AD5NQIYJ35LDYUK223UZMSJFANCNFSM5JSOBTSA&source=gmail-imap&ust=1644542228000000&usg=AOvVaw1aoJggkwV_oJLFh9kGAPWQ>. Triage notifications on the go with GitHub Mobile for iOS <https://www.google.com/url?q=https://apps.apple.com/app/apple-store/id1477376905?ct%3Dnotification-email%26mt%3D8%26pt%3D524675&source=gmail-imap&ust=1644542228000000&usg=AOvVaw2B0218Osa1UUqtb-pN45A1> or Android <https://www.google.com/url?q=https://play.google.com/store/apps/details?id%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&source=gmail-imap&ust=1644542228000000&usg=AOvVaw2O33p0AgkLn1jIyTYKOltk>. You are receiving this because you were mentioned.

[c-suh]

Hi @neese, so sorry I missed this, especially as you used the @mention! In this case, I wasn't notified because, I think, the issue had been closed, so I will leave it open the next time for another day or two.

Regarding your question: I need the GitHub username for Ken Lawrence. I can then make him a member of the NEAS LDD Stewardship Team, which would grant him Admin access to the PDS NEAS repo. I have just sent you an invite for the team as well.

[neese]

@c-suh It's ok you didn't get back right away because Ken is very busy preparing for the NEAScout pre-launch peer review and will not be migrating the NEAS LDD to PDS GitHub until after that. I have asked him for his GitHub username so he can be added to the stewardship team and have access once he is ready to start work on it. Thanks for the invite for me, I just accepted it.

[neese]

@c-suh Ken Lawrence's GitHub username is klawrence4969.

[c-suh]

@neese and @klawrence4969 an invite has been sent!