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
Indigenous metadata considerations #35
Comments
@emiliom any experience with this from your NANOOS days? |
@MathewBiddle The only legacy connection I know of to the AFAIK, Since we're no longer requiring SOS/SWE, I think we could drop |
We did use the "tribal" sector value for a couple of assets in NANOOS. It didn't raise issues with our partners, BUT, they probably were not aware of the existence of this metadata. Still, this being a fully US context, that part would probably not have been an issue. Changing it to "indigenous" would make sense, though I suggest that would be an opportunity to engage tribal partners about this terminology and associated descriptions. I'd be happy to facilitate some connections if you'd like. You'd also have to think about what to do with existing uses of "tribal". I believe the motivation for having a The issue with "country" seems much trickier, and one I never dealt with. I imagine that not having US or Canada (as the case may be) in a machine actionable form under "country" could easily lead to unintended results when querying and inventorying assets. I wouldn't be surprised if there exists a clear (if not widely adopted) terminology that represents the relationship and distinction between a country and an indigenous nation. For example, in our usual contexts, country is an entity that has a ISO 3166-1 alpha-2 country code. Anyway, that's out of my depth. |
@emiliom and @mwengren thank you both for the context and discussion points. As I can't seem to find other examples of these changes I think it would be worthwhile for the IOOS community to discuss and explore the options. From what I can see now, here are the action items to be discussed:
|
@MathewBiddle Thinking of options to resolve the For the
Having said that though, we don't mention that vocabulary restriction anywhere in the attribute descriptions like you mentioned, so that was probably just assumed. Technically speaking, anything could be entered in those attributes and they would be 'compliant' with our profile. Not sure how to handle that one. Maybe we can leave it open ended as it is and as long as data providers understand the purpose of the attribute is to create a mailing address-like metadata collection, they can include any country identifier they prefer? Any other ideas out there? |
@mwengren I haven't used For reference, here are the unique @kbailey-noaa do you have any insights into how we use the |
@kbailey-noaa is okay with making these adjustments. |
@emiliom @fgayanilo I was going to update the terms in https://mmisw.org/ont/ioos/sector as described here, but I need permission to edit the vocabularies owned by 'ioos' in MMISW. How does one get access to this? My newly-created account ID on MMISW is: mwengren. @emiliom It appears you are the author of the sector vocabulary, that's why I included you in my request. TIA! |
Could you add me too? username: |
there is an account for user= ioos with admin access for the collection. You can reset the password -- I think the account is registered to Derrick (@carueda I lost my "Admin" tab) |
@fgayanilo – We (I and @graybeal) would be happy to assist with https://mmisw.org/ont stuff but I'm afraid I don't understand what the specific need is. |
@carueda NOAA IOOS wants to update the vocabulary they maintain (IOOS collections). Matt Biddle (username=mathewbiddle) and Micah Wengren (username=mwengren) want to update their collection. We created an account with username=ioos (if my memory serves me right) for this purpose, but I cannot remember the profile for that user. Perhaps, you can help reset the password for that account. |
Thanks @fgayanilo ... I just added those users as members to the ioos organization. |
That's amazing. I was just thinking during ESIP SemTech meeting yesterday about IOOS as an example of a group that published their vocabularies (some)!
Would be great to have that content updated.
John
On Nov 9, 2022, at 9:25 AM, Felimon Gayanilo ***@***.******@***.***>> wrote:
NOAA IOOS wants to update the vocabulary they maintain (IOOS collections). Matt Biddle (username=mathewbiddle) and Micah Wengren (username=mwengren) want to update their collection. We created an account with username=ioos (if my memory serves me right) for this purpose, but I cannot remember the profile for that user. Perhaps, you can help reset the password for that account.
—
Reply to this email directly, view it on GitHub<#35 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAJVJUASJQKZWOA343QDUETWHPNABANCNFSM5YOWQFIQ>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
========================
John Graybeal
Technical Program Manager
Center for Expanded Data Annotation and Retrieval /+/ NCBO BioPortal
Stanford Center for Biomedical Informatics Research
650-736-1632 | ORCID 0000-0001-6875-5360
|
Thanks, I see the 'Edit new version' button now. This should do the trick. I'm not sure how actively we plan to maintain all of these vocabularies, most aren't in active use at this point, but we do need to make a few changes to this particular one. |
I'm glad I saw this after it had already been resolved 😄 ! Brings back memories. |
Thanks all! The https://mmisw.org/ont/ioos/sector vocabulary has now been updated to include the terms Reading the vocabulary description more closely, I realized we're going against our own recommendations there (to use I will leave this open so we can remember (hopefully) to add a vocabulary reference for the |
This partner is closely engaged with First Nations and had some questions about the metadata. These are based on the metadata profile 1.2, mostly focused in the attribution section.
@mwengren any thoughts?
The text was updated successfully, but these errors were encountered: