Tracking metadata for Tetiaroa

[jdeck88]

There are a couple of needs for tracking metadata for Tetiaroa work:

1. Add "Auditor" to Expedition. It should be able to take multiple organizations, but for now we are using it to add Gump and Tetiaroa RORs to identify expeditions that were supported by either of these field stations.

Tetiaroa ROR: https://ror.org/04p8xrf95
Gump ROR: https://ror.org/04sk0et52

Here are some questions about this request:

• We need to insert this expedition level metadata field in the Master Configuration for an individual project or team level. so, What TEAM or PROJECT do we want this attached to?
• Is this OK to add as a free-text field or do we need a drop-down list of actual values?
• The term "Auditor" could be a little confusing to folks if we open this up. Can you come up with a short phrase that would clarify the intention here?
• do you want to be able to add multiple values for this field? How would this be entered? e.g. as a free text field using Pipe delimeter?

2. Institution as Project level metadata field. We had talked last month about adding Institution as a project level metadata field. Is this superseded by the request Put GeOMe logo in header #1 above?

[erinmr]

Hi John -

1. Answering the bullets here:

• I'd like this to be deployed across all expeditions and not specify specific projects or teams. All expeditions should be able to have an auditor
• For now it could be a free-text, but we'd like the field to be human readable org, linked to ROR (https://ror.org/): Tetiaroa ROR: https://ror.org/04p8xrf95 and Gump Station: https://ror.org/04sk0et52
• re: Auditor: It is meant for being able to identify all work that the field station has supported. I noted the field "institutionCode" that is already in samples, but let it be used at expeditions in addition? We went through rounds of what to call this, and this is where the group landed, so I hesitate to rename it right now.
• We would like potentially have multiple orgs in this field like Smithsonian (home institution) and Gump (field station institution). This would allow us to show all expeditions that were supported by Smithsonian or all expeditions that Gump supported.

2. This supersedes the idea on the institution metadata for the project.

[erinmr]

Re: ROR - i don't want ROR to be visible to humans, just linked in metadata and not a free text list, but org names are structured.

[jdeck88]

Erin--- should we ONLY allow RORs for this? I could have the field described like: "Auditor (insert ROR URL only)".
And then when we display auditor for expeditions that have been loaded, do a lookup on that ROR to find the fully qualified name dynamically.

[erinmr]

Hi John - Ideally, it will be something like what DMPTool has where it's a controlled list and it populates as you type like the screenshot below. The ROR isn't meaningful to humans, so while we need it in the metadata what we want to show is Tetiaroa Society or Gump Station. For now, let's go human readable free text.

[jdeck88]

Do you have a list of available funding organizations we want listed? Or to allow a list of ALL RORs?
I created a quick and dirty option with just the two options, see:
https://www.loom.com/share/7c79c4e8c71a47fda2c80820242b0c1e

I need to do some coding to enable a key/value list to enable text on the drop drown that is linked to a ROR id on the back-end when assigning expedition metadata properties.... Lets discuss this issue more in detail in Moorea and likely we want to spin-up a new issue with this more fully specified...

John

[erinmr]

This is super! These two for now are fine. Let’s also spin up an issue there on orcid working this way too. Thanks

…

On Friday, March 8, 2024, John Deck ***@***.***> wrote: Do you have a list of available funding organizations we want listed? Or to allow a list of ALL RORs? I created a quick and dirty option with just the two options, see: https://www.loom.com/share/7c79c4e8c71a47fda2c80820242b0c1e I need to do some coding to enable a key/value list to enable text on the drop drown that is linked to a ROR id on the back-end when assigning expedition metadata properties.... Lets discuss this issue more in detail in Moorea and likely we want to spin-up a new issue with this more fully specified... John — Reply to this email directly, view it on GitHub <#629 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAWHZY4PBIOINT5ZRRNRHZ3YXHWY3AVCNFSM6AAAAABEJSCP2GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBWGA4TANZVGU> . You are receiving this because you commented.Message ID: ***@***.***>