- Today we are starting the strategy subgroup. Our aim is to develop guidelines for assignment of these DOIs to multiple digital objects. Lalit Wanchoo had shared the document earlier with thought processes as to why we are doing that.
- In doing this it may be a good idea to have a template for people to fill in so we can see the use cases that people have; look at those use cases and develop commonalities among them to establish guidelines.
- Lalit will email template to everyone.
- What he’s looking for: you will define your collection of collections or documents that you think we should assign a group type of DOI, and why you want that; what advantages and benefits it will have. Also we want to see if there are any conditions before we assign. What metadata it might impact, any unique features, etc.
- More of what we’re looking for: once you have the data, how the DOI will play the role, and if we have to register, what things we need. It’s possible that the current registration model will need to be updated with additional fields. And who is responsible if we need to contact someone generally.
- How many of you can provide use cases? Is there anybody who doesn’t have a use case?
- Alicia Scott: Can’t think of any but might think otherwise upon seeing examples of others’ use cases.
- Lalit: It depends on how you assign your primary DOIs.
- Lena Iredell: Looking at use cases will be very useful. Can think of a few that we have: one is a particular new mission that we’re getting in; it’s a group of about six different PIs that each have related data; they want their data commingled and the documentation grouped together as a set. Another case is a collection of data with a producer combining content from different satellites and in about four different processing methods; each method has about 10-15 collections within it. This is a good way to separate out the methods and look at the content across the data and then we have several missions that have Level 1, Level 2, Level 3 data, so this might be a way for the PIs to group the data by level.
- Lalit: That’s exactly what I’m looking for, so we know how to establish the process and guidelines.
- Alicia: Had another comment: if we group these products based on how they might be used, doesn’t that introduce an infinite possibility in the future of how many additional DOIs we would have? Each user has a different way of grouping data based on what’s relevant to them at the moment.
- Lalit: That’s correct. These are unlimited conditions and combinations that can happen. That’s the discussion for our group to have, how to address these combinations.
- Alicia: I liked what Lena said about if it’s a PI or someone like that who has a recommendation about grouping products based on a project, but other than that I think we’d have to define which users are able to request and have us create these groups of DOIs.
- Lalit: The input has to come from the data producer so the PIs should consult with the DAAC and work together: how would this combination work? There should be discussion with the PI.
- Deborah Smith: I think the key is to determine what we will or won’t do, because if we leave it all to the PI we end up with a whole host of ways to do it that could be ever-expanding. So we may think of all these different use cases and group them into a few types and say these are what we will do, but extreme cases may fall out of scope….
- Lalit: Absolutely. That’s the whole purpose.
- Megan Buzanowicz: I have a potential use case: last week I met with Deborah about doing DAAC assignment and ingesting/archiving a surface network that could get interesting: it’s a different network of LIDARs and sometimes they’re moved around. Organizing that and potentially linking it all together could get interesting. That might be one of our bigger use cases. Another area is the facility instruments. One had a specific subset of data they wanted to group together so they could write a publication and disseminate that subgroup of data more easily. This DOI grouping could be helpful in that case.
- Michele Thornton from ORNL: Megan touched on a lot of the challenge that we’ll have with airborne especially with regard to facility instruments. Some are heavily used in other missions and campaigns. Each are using facility instruments. Those are perfect use cases. Another mission has two instruments that had a very specific mission. It sounds a lot like what Megan was saying; similar use cases in that regard.
- Lalit will send template again after the meeting. Will look at use cases at next meeting.
- Send email to Lalit if you have any questions or need help.
- What about everyone adding to a single Google document?
- Lalit: Sure, we can do that.
Overview
Content Tools