Blogs

Good Afternoon All!

Just wanted to update everyone on what we've been up to. Alan and I have collaborated together in revising the Draft Criteria questions. I wanted to post them up and let you all see and get some feedback before I proceed. Please feel free to contact me if you have any questions. Have a good weekend!

-Katherine
kyee@usgs.gov

DRAFT CRITERIA

1. Is this a single vocabulary or a collection of vocabularies?

(GOVERNANCE STRUCTURE)
2a. Does the vocabulary or collection of vocabularies have a governance structure?

To All,

Fran, Andy, and I have been brainstorming on my project that I will be working on this summer. Before I progress more into the CMSP Controlled Vocabulary criteria, I have a few questions that I hope can be answered.

Let's say I want to find the best vocabulary out there for describing things in the environment that can be observed—variables, parameters, phenomena, observable properties, whatever you might call them. If you are doing earth science on your laptop, these might be the labels you put in the top row of your spreadsheet.

How can I find that best vocabulary for a given domain and situation, like environment science (especially oceanography) observations in an infrastructure project? Shall we try?

OK, so it doesn't take long to make the point here: I think this OOI Cyberinfrastructure is a cool project, and if you're a sophisticated data management or cyberinfrastructure person, you probably will too. This is your classic 'rich metadata' environment. There are a significant number of new positions, and the hiring pace is picking up now. So if this might be the thing for you, get in gear and apply already. Help this leading-edge project be successful!

I can't believe I'm saying this, but I got a computer-generated phone call that I actually enjoyed. Well, in a wonky sort of way.

I was describing good future data practices to a panel considering ocean science needs for 2030, and was asked a good question after the talk: What are the qualities of a 'good' data system?

Hopefully our Guides on MMI give some ideas about that question, but the Guides are really focused on metadata. And they don't put it all in a neat summary.

So here are my proposals for what makes a good data system, with suitable weasel words for the wide array of projects that need data systems.

Introduction

Without having extensively surveyed the literature, these are some thoughts I've put together (as part of my OOI Cyberinfrastructure job) on what it means to talk about a data product version. Your comments are appreciated.

In this document, I call a Version a form of relationship in which one thing is the same as another in some conceptual sense, but has differences as the result of other attributes not being the same. To be specific:

DataONE invites applications for summer research internships for undergraduates, graduate students and postgraduate (MS, PhD) students. As part of a larger virtual organization, interns will work in virtual groups of 2-3 with multiple mentors from DataONE, and are not expected to be at the same location or institution as the mentors and other team members.  Regular communication (including videoconference) with mentors and other team members will

For those of you seeing this on the front page of MMI: I'm using this post to call attention to MMI blogs. If you're a member you can blog about metadata things on MMI. Ask us if you need help!

This Periodic Table of Visualization Methods is either not at all about metadata, or all about it. It sure is all about interoperability! The table has a remarkable amount of depth, even after you have discovered that mousing over an entry brings up an example of the corresponding visualization.

 

Ever wonder where we're headed, with all this new technology, and ever-more-complex development?  Check out "From linking to thinking: How we'll live when information surrounds us"